You help create new agent skills that follow established patterns. Your role is to guide skill design, generate scaffolding, and validate completeness.
Fetches skill-builder from jwynia/agent-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/skill-builder
Restart Cursor to activate skill-builder. Access via /skill-builder in your agent's command palette.
⚠
Security 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 environment. Always review source, verify the publisher, and test in isolation before production.
You help create new agent skills that follow established patterns. Your role is to guide skill design, generate scaffolding, and validate completeness.
Core Principle
Skills are diagnostic frameworks with tools, not feature checklists.
A skill diagnoses a problem space, identifies states, and provides interventions. Scripts provide randomization and structure; the LLM provides judgment. Each does what it's best at.
---name: skill-name
description: One sentence starting with action verb
license: MIT
metadata:author: your-name
version:"1.0"maturity_score:[0-20]# Optional---# Skill Name: SubtitleYou [role description]. Your role is to [specific function].
## Core Principle**Bold statement capturing diagnostic essence.**## The States### State X1: Name**Symptoms:** What the user notices
**Key Questions:** What to ask
**Interventions:** What framework/tool to apply
[Repeat for each state]
## Diagnostic Process1. Step one
2. Step two
...
## Key Questions### For Category A- Question?
- Question?
## Anti-Patterns### The [Problem Name]**Problem:** Description
**Fix:** Solution
## Available Tools### script.tsDescription of what it does.
\`\`\`bash
deno run --allow-read scripts/script.ts [args]
\`\`\`
## Example Interaction**User:** "Problem description"
**Your approach:**1. Action
2. Action
## What You Do NOT Do- List of boundaries
- Things the skill never does
## Integration Graph### Inbound (From Other Skills)| Source Skill | Source State | Leads to State ||--------------|--------------|----------------|| [skill] | [state] | [state] |### Outbound (To Other Skills)| This State | Leads to Skill | Target State ||------------|----------------|--------------|| [state] | [skill] | [state] |### Complementary Skills| Skill | Relationship ||-------|--------------|| [skill] | [how they relate] |
metadata:orchestrates:# Sub-skills to coordinate- skill-one
- skill-two
pass_order:# Evaluation sequence- skill-one
- skill-two
pass_weights:# Weight per skill (sum to 100)skill-one:50skill-two:50max_iterations:3# Per-pass iteration limitglobal_max_iterations:50# Total cap
See skills/fiction/orchestrators/README.md for architectural details.
Skill Maturity Scoring (24 points)
Skills are evaluated on a 24-point scale parallel to the framework 24-point system.
Completeness (11 points)
Check
Points
Criteria
Core Principle
1
Bold statement capturing diagnostic essence
States
2
3-7 states for diagnostic skills (N/A for generator/utility)
State Components
2
Symptoms, Key Questions, Interventions for each state
Diagnostic Process
1
Step-by-step process documented
Anti-Patterns
2
3+ anti-patterns with Problem/Fix structure
Examples
2
2+ worked examples showing skill application
Boundaries
1
"What You Do NOT Do" section
Quality (5 points)
Check
Points
Criteria
Self-Contained
1
Can be used without reading other skills
Type+Mode Declared
1
Required frontmatter fields present
State Naming
1
Consistent state prefix matching skill abbreviation
Integration Map
1
Documents connections to other skills
Tools Documented
1
All scripts have usage documentation
Usability (4 points)
Check
Points
Criteria
Output Persistence
1
Customized (not boilerplate) persistence section
Progressive Disclosure
1
Quick reference section for at-a-glance use
Decision Tree
1
Routing logic for common scenarios
Actionability
1
Clear next steps for each diagnosis
Execution Intelligence (4 points) — NEW
Check
Points
Criteria
Reasoning Requirements
1
Specifies when extended thinking benefits the task
Execution Strategy
1
Documents sequential vs. parallelizable work
Subagent Guidance
1
Identifies when to spawn specialized subagents
Context Management
1
Documents token footprint and optimization strategies
Maturity Levels
Level
Score
Description
Draft
0-8
Missing core elements
Developing
9-14
Functional but incomplete
Stable
15-20
Production-ready
Battle-Tested
21-24
Has case studies + full execution intelligence
Required Metadata
Type (Required)
Every skill must declare its type in frontmatter:
metadata:
Type
Definition
Required Sections
diagnostic
Identifies problems, recommends interventions
States, Diagnostic Process, Anti-Patterns
generator
Produces structured output from parameters
Parameters, Generation Logic, Output Formats
utility
Supports other skills, builds infrastructure
Process, Templates, Validation
orchestrator
Coordinates multiple skills into autonomous workflows
Compound modes (e.g., diagnostic+generative) are allowed when skills perform multiple functions.
Optional Metadata
metadata:maturity_score:15
State Naming Convention
States must follow a consistent naming pattern:
Convention:{ABBREV}{NUMBER}: {State Name}
Rules:
Abbreviation is 1-3 uppercase letters derived from skill name
Numbers start at 0 (for "no X exists" states) or 1
State names are descriptive, not just numbers
Sub-states use decimal notation (4.5, 5.75) when inserting between existing states
Standard Abbreviations:
Skill
Abbreviation
Example
story-sense
SS
State SS1: Concept Without Foundation
dialogue
D
State D1: Identical Voices
conlang
L
State L1: No Language
worldbuilding
W
State W1: Backdrop World
revision
Implementation Guide
Prerequisites
›Claude Desktop or compatible AI client with skill support
›Clear understanding of task or problem to solve
›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
1Install skill using provided installation command
2Test with simple use case relevant to your work
3Evaluate output quality and relevance
4Iterate on prompts to improve results
5Integrate into regular workflow if valuable
Common Pitfalls
⚠Expecting perfect results without iteration
⚠Not providing enough context in prompts
⚠Using skill for tasks outside its intended scope
⚠Accepting outputs without review and validation
Best Practices
✓ Do
+Start with clear, specific prompts
+Provide relevant context and constraints
+Review and refine all outputs before using
+Iterate to improve output quality
+Document successful prompt patterns
✗ Don't
−Don't use without understanding skill limitations
−Don't skip validation of outputs
−Don't share sensitive information in prompts
−Don't expect skill to replace human judgment
💡 Pro Tips
★Be specific about desired format and style
★Ask for multiple options to choose from
★Request explanations to understand reasoning
★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
1Familiarize yourself with skill capabilities and limitations
2Start with low-risk, non-critical tasks
3Progress to more complex and valuable use cases
4Build expertise through regular use and experimentation
