S Claude Has Skills Tools

Pattern catalog

Claude Skill Examples and Patterns

A pattern catalog for reading official Claude Skill examples and designing your own without copying blindly.

Updated 2026-07-06 9 min T4 source-backed

Primary source takeaway: the official examples show multiple shapes of skills, from lightweight guidance to script-heavy document workflows.

Document and file-format skills

The docx, pdf, pptx, and xlsx examples are the right place to study complex skills. They show how a skill can combine prose instructions with helper scripts and format-specific knowledge. The lesson is not that every skill needs a script; the lesson is that scripts are useful when file formats need deterministic handling.

If your workflow manipulates structured files, start by deciding which operations must be exact. Put exact operations into scripts or templates, and let the model handle judgment, prioritization, and narrative output.

Design and creative skills

Skills such as frontend-design, brand-guidelines, canvas-design, theme-factory, and algorithmic-art demonstrate taste-setting. They work by naming the aesthetic standard, describing anti-patterns, and giving the agent a vocabulary for decisions.

The risk with creative skills is generic taste language. Replace vague words like "polished" with concrete rules: typography constraints, layout expectations, unacceptable visual tropes, or domain-specific examples.

Developer workflow skills

Developer skills such as webapp-testing, mcp-builder, and claude-api show how a skill can guide an agent through technical work without becoming a full tutorial. The best versions define when to inspect docs, when to run tools, and what output evidence counts as done.

Keep developer skills close to verifiable commands. A skill that says "test carefully" is weak. A skill that names the exact browser checks, command sequence, expected artifact, and failure-report format is much stronger.

Enterprise workflow skills

Skills for internal communications, coauthoring, or brand guidelines are useful because they package institutional preferences. The skill can tell the agent how the organization writes, which templates to use, what approvals matter, and how to avoid claims that the organization would not make.

These are also the skills most likely to contain sensitive information. Separate public examples from private policies, and run a security review before sharing a skill outside the team.

Creator-helper skills

skill-creator is a meta-skill: it helps create skills. Study it to see how an agent can interview a user, translate workflow details into frontmatter, and produce a starter folder. Meta-skills are powerful, but their output still needs review by someone who understands the target task.

A creator-helper skill should produce small, inspectable artifacts. Avoid generators that create huge skill bundles before the workflow has been tested on real prompts.

FAQ

Is this site affiliated with Anthropic?

No. Claude Has Skills is an independent editorial guide. It links to Anthropic and Agent Skills primary sources so readers can verify product details directly.

Does a skill replace normal prompting?

No. A skill packages repeatable instructions and resources so the agent can load them when a task matches. The user still asks for a task, and the agent still decides what to read and run.

Which example should I study first?

Start with skill-creator for structure, then inspect the official example closest to your task family.

Can an example skill be production-ready?

Sometimes, but do not assume it. Review behavior, dependencies, permissions, and output quality in your own environment.

Primary Sources