{"id":24841,"date":"2025-11-23T07:15:37","date_gmt":"2025-11-23T07:15:37","guid":{"rendered":"https:\/\/pokecon.jp\/job\/?p=24841"},"modified":"2025-11-23T07:15:37","modified_gmt":"2025-11-23T07:15:37","slug":"how-to-create-skills-for-claude-steps-and-examples","status":"publish","type":"post","link":"https:\/\/pokecon.jp\/job\/24841\/","title":{"rendered":"How to create Skills for Claude: steps and examples"},"content":{"rendered":"\n<\/p>\n
\n

Skills<\/a> are custom instructions that extend Claude’s capabilities for specific tasks or domains.\u00a0<\/p>\n

When you create a skill via a SKILL.md<\/a> file, you’re teaching Claude how to handle specific scenarios more effectively. The power of skills lies in their ability to encode institutional knowledge, standardize outputs, and handle complex multi-step workflows that would otherwise require repeated explanation or investment in building a custom agent.<\/p>\n

Learn how to create skills that transform Claude from general-purpose assistant into specialized expert for your specific workflows either with our skill creator<\/a> template or manually. (Pro-tip: to make it easy, we recommend building your SKILL.md<\/a> file with this template and tailoring from there).<\/p>\n

Creating a skill in 5 steps<\/strong><\/h2>\n

Follow this structured approach to build skills that trigger more reliably.<\/p>\n

1. Understand the core requirements<\/strong><\/h3>\n

Before writing anything, clarify what problem your skill solves. Strong skills address concrete needs with measurable outcomes. “Extract financial data from PDFs and format as CSV” beats “Help with my finance stuff” because it specifies the input format, the operation, and the expected output.<\/p>\n

Start by asking yourself: What specific task does this skill accomplish? What triggers should activate it? What does success look like? What are the edge cases or limitations?<\/p>\n

2. Write the name<\/strong><\/h3>\n

Your skill needs three core components: name<\/strong> (clear identifier), description<\/strong> (when to activate), and instructions<\/strong> (how to execute). In fact, the name and description are the only parts of the SKILL.md<\/a> file that influence triggering, in other words, the ability for Claude\u00a0 to call a skill for specialized knowledge or workflows.\u00a0<\/p>\n

The name should be straightforward and descriptive. Use lowercase with hyphens (e.g., pdf-editor, brand-guidelines). Keep it short and clear.<\/p>\n

3. Write the description field<\/strong><\/h3>\n

The description determines when your skill activates, making it the most critical component. Write it from Claude’s perspective, focusing on triggers, capabilities, and use cases.<\/p>\n

A strong description balances several elements: specific capabilities, clear triggers, relevant context, and boundaries.<\/p>\n

Weak description<\/strong>:<\/p>\n

This skill helps with PDFs and documents.<\/span><\/code><\/pre>\n
Strong description<\/strong>:<\/p>\n
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging\/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale. Use for document workflows and batch operations. Not for simple PDF viewing or basic conversions.<\/span><\/code><\/pre>\n
The stronger version gives Claude multiple data points: specific verbs (extract, create, merge), concrete use cases (form filling, batch operations), and clear boundaries (not for simple viewing).<\/p>\n
4. Write the main instructions<\/strong><\/h3>\n
Your instructions should be structured, scannable, and actionable. Use markdown headers, bullet points for options, and code blocks for examples.<\/p>\n
Structure with clear hierarchy: overview, prerequisites, execution steps, examples, error handling, and limitations. Break complex workflows into discrete phases with clear inputs and outputs.<\/p>\n
Include concrete examples showing correct usage. Specify what the skill cannot do to prevent misuse and manage expectations. Your SKILL.md<\/a> file can also include additional reference files and assets to provide even more clarity and guidance around what you\u2019re asking the agent to do when the skill is triggered.\u00a0<\/p>\n
5. Upload your skill\u00a0<\/strong><\/h3>\n
Depending on what Claude surface you\u2019re building on, here\u2019s how to upload your skill for use:\u00a0<\/p>\n