create-skill
siviter-xyz/dot-agent
Guide for creating modular skills that extend agent capabilities with specialized knowledge and workflows.
What is create-skill?
This skill provides best practices for building effective SKILL.md packages that extend agent capabilities. Use it when creating or updating skills to ensure they follow the progressive disclosure principle, maintain optimal performance, and remain maintainable across different models.
- Structure skills as modular packages with metadata, instructions, and bundled resources
- Apply the 200-line rule to keep SKILL.md concise and context-efficient
- Implement three-level progressive disclosure: metadata, body, and bundled resources
- Set appropriate degrees of freedom for different types of instructions
- Bundle specialized workflows, tool integrations, and domain expertise
- Test skills across multiple models for consistent effectiveness
How to install create-skill
npx skills add https://github.com/siviter-xyz/dot-agent --skill create-skillHow to use create-skill
- 1.Review the three-level loading system to understand progressive disclosure
- 2.Structure your skill with SKILL.md (under 200 lines) and optional bundled resources in scripts/, references/, and assets/
- 3.Write concise metadata in YAML frontmatter with name and description
- 4.Keep the SKILL.md body focused on essential instructions, moving detailed content to references/
- 5.Apply appropriate degrees of freedom based on whether the task allows multiple approaches or requires specific steps
- 6.Test your skill with all target models before publishing
Use cases
- Creating a new skill to extend agent capabilities in a specific domain
- Refactoring an existing skill to improve performance and maintainability
- Building company-specific knowledge skills with custom schemas and business logic
- Packaging multi-step workflows as reusable skill modules
- Integrating tool-specific instructions for APIs or file formats
- Skill developers building extensions for coding agents
- Teams creating domain-specific agent capabilities
- Engineers packaging workflows and tool integrations
- Anyone maintaining or updating existing skills
create-skill FAQ
SKILL.md must stay under 200 lines to reduce initial context load and improve activation times. If you need more content, move it to bundled reference files that load only when needed.
Use inline content for essential instructions that always apply. Move detailed documentation, examples, and reference material to references/ files that load progressively as the agent needs them.
Use high freedom for text-based instructions with multiple valid approaches, medium freedom for pseudocode with parameters, and low freedom for specific scripts handling fragile operations.
Skills act as additions to the underlying model, so effectiveness varies by model capability. Testing ensures your skill works reliably across Claude, GPT, and other supported models.
Include name and description in YAML frontmatter. The description should clearly state what the skill does and when to use it, helping agents decide whether to activate it.
Full instructions (SKILL.md)
Source of truth, from siviter-xyz/dot-agent.
name: create-skill description: Guide for creating effective skills following best practices. Use when creating or updating skills that extend agent capabilities.
Create Skill
Guide for creating effective skills that extend agent capabilities with specialized knowledge, workflows, and tool integrations.
About Skills
Skills are modular, self-contained packages that extend agent capabilities by providing specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific domains or tasks.
What Skills Provide
- Specialized workflows - Multi-step procedures for specific domains
- Tool integrations - Instructions for working with specific file formats or APIs
- Domain expertise - Company-specific knowledge, schemas, business logic
- Bundled resources - Scripts, references, and assets for complex and repetitive tasks
Progressive Disclosure Principle
The 200-line rule is critical. SKILL.md must be under 200 lines. If you need more, split content into references/ files.
Three-Level Loading System
- Metadata (name + description) - Always in context (~100 words)
- SKILL.md body - When skill triggers (<200 lines, ideally <500 lines for optimal performance)
- Bundled resources - As needed by agent (unlimited)
Why Progressive Disclosure Matters
- 85% reduction in initial context load
- Activation times drop from 500ms+ to under 100ms
- Agent loads only what's needed, when it's needed
- Skills remain maintainable and focused
Skill Structure
skill-name/
├── SKILL.md (required, <200 lines)
│ ├── YAML frontmatter metadata (required)
│ │ ├── name: (required)
│ │ └── description: (required)
│ └── Markdown instructions (required)
└── Bundled Resources (optional)
├── scripts/ - Executable code
├── references/ - Documentation loaded as needed
└── assets/ - Files used in output
Core Principles
Concise is Key
The context window is a shared resource. Your skill shares it with everything else the agent needs. Be concise and challenge each piece of information:
- Does the agent really need this explanation?
- Can I assume the agent knows this?
- Does this paragraph justify its token cost?
Set Appropriate Degrees of Freedom
- High freedom: Text-based instructions for multiple valid approaches
- Medium freedom: Pseudocode or scripts with parameters
- Low freedom: Specific scripts with few/no parameters for fragile operations
Test with All Models
Skills act as additions to models, so effectiveness depends on the underlying model. Test your skill with all models you plan to use it with.
References
For detailed guidance, see:
references/progressive-disclosure.md- 200-line rule and references patternreferences/skill-structure.md- SKILL.md format and frontmatter detailsreferences/examples.md- Good skill examplesreferences/best-practices.md- Comprehensive best practices guide
Related skills
More from siviter-xyz/dot-agent and the wider catalog.

backend-development
Backend API design, database architecture, microservices patterns, and test-driven development. Use for designing APIs, database schemas, or backend system architecture.

code-review
Automated code review for pull requests using specialized review patterns. Analyzes code for quality, security, performance, and best practices. Use when reviewing code changes, PRs, or doing code audits.

google-flights
Search Google Flights for flight prices, schedules, and availability via browser automation.
agent-browser
Browser automation CLI for AI agents to navigate, interact with, and extract data from websites.
byted-ark-seedance-skill
Volcano Ark Seedance AI video generation for Agent Plan with intelligent model routing and multimodal support.
byted-ark-seedream-skill
AI image generation for Agent Plan with coherent series, streaming output, and prompt optimization.