create-skill

siviter-xyz/dot-agent · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/siviter-xyz/dot-agent --skill create-skill
0 commentsdiscussion
summary

Comprehensive guide for building modular skills that extend agent capabilities with specialized knowledge and workflows.

  • Skills are self-contained packages providing specialized workflows, tool integrations, domain expertise, and bundled resources for agents
  • SKILL.md must stay under 200 lines; use progressive disclosure by splitting detailed content into references/ files to reduce context load and activation time
  • Structure includes required YAML frontmatter (name, description) and m
skill.md

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

  1. Specialized workflows - Multi-step procedures for specific domains
  2. Tool integrations - Instructions for working with specific file formats or APIs
  3. Domain expertise - Company-specific knowledge, schemas, business logic
  4. 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

  1. Metadata (name + description) - Always in context (~100 words)
  2. SKILL.md body - When skill triggers (<200 lines, ideally <500 lines for optimal performance)
  3. 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 pattern
  • references/skill-structure.md - SKILL.md format and frontmatter details
  • references/examples.md - Good skill examples
  • references/best-practices.md - Comprehensive best practices guide
how to use create-skill

How to use create-skill on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add create-skill
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/siviter-xyz/dot-agent --skill create-skill

The skills CLI fetches create-skill from GitHub repository siviter-xyz/dot-agent and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/create-skill

Reload or restart Cursor to activate create-skill. Access the skill through slash commands (e.g., /create-skill) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.841 reviews
  • Shikha Mishra· Dec 8, 2024

    I recommend create-skill for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Isabella Menon· Dec 8, 2024

    Useful defaults in create-skill — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Daniel Park· Dec 4, 2024

    Keeps context tight: create-skill is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Rahul Santra· Nov 27, 2024

    Solid pick for teams standardizing on skills: create-skill is focused, and the summary matches what you get after install.

  • Benjamin White· Nov 27, 2024

    We added create-skill from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Sofia Martin· Nov 23, 2024

    create-skill is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Pratham Ware· Oct 18, 2024

    create-skill is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Anaya Martinez· Oct 18, 2024

    create-skill reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Daniel Thompson· Oct 14, 2024

    Solid pick for teams standardizing on skills: create-skill is focused, and the summary matches what you get after install.

  • Kaira Patel· Sep 25, 2024

    create-skill is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 41

1 / 5