rolemodel/skill-creation
skills/skill-creation/SKILL.md
Create and update SKILL.md files following the Agent Skills format specification. Use when building new skills or improving existing skill documentation for AI agents.
$ install --global
skillsauthnpx skillsauth add rolemodel/rolemodel-skills skill-creationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 10:12 AM226.4s1 file scanned
SKILL.md
- name:
- skill-creation
- description:
- Create and update SKILL.md files following the Agent Skills format specification. Use when building new skills or improving existing skill documentation for AI agents.
Skill Creation Guide
Generate properly formatted SKILL.md files that help AI agents perform domain-specific tasks effectively.
File Structure
Every skill must have:
- YAML frontmatter with required fields
- Markdown body with clear instructions
- Progressive disclosure (concise main file, detailed references separate)
Optional directories:
scripts/: Executable code agents can run. Keep scripts self-contained or document dependencies, and include clear error handling.references/: On-demand documentation (for example,REFERENCE.md, templates, domain notes). Keep files focused and small for efficient context usage.assets/: Static resources such as templates, diagrams, and data files.
Recommended layout:
skill-name/
├── SKILL.md
├── scripts/ # Optional
├── references/ # Optional
├── assets/ # Optional
└── ...
Frontmatter Requirements
SKILL.md must start with YAML frontmatter, followed by Markdown instructions.
Required Fields
---
name: skill-name
description: What this skill does and when to use it.
---
name field rules:
- 1-64 characters
- Lowercase alphanumeric characters and hyphens only
- No leading/trailing hyphens
- No consecutive hyphens (
--) - Must match parent directory name
description field rules:
- 1-1024 characters
- Include WHAT the skill does
- Include WHEN to use it (trigger keywords)
- Be specific about use cases
Optional Fields
Optional frontmatter fields and constraints:
license: License name or reference to a bundled license filecompatibility: 1-500 characters when present; describe environment requirements only when neededmetadata: Key-value mapping for additional metadataallowed-tools: Space-delimited list of pre-approved tools (experimental; support varies by agent)
license: Apache-2.0
compatibility: Requires git, docker, and internet access
metadata:
author: org-name
version: "1.0"
allowed-tools: Bash(git:*) Bash(jq:*) Read
Body Content Guidelines
Structure:
- Clear overview of capability
- Step-by-step instructions
- Examples with inputs/outputs
- Edge cases and considerations
Best Practices:
- Keep main SKILL.md under 500 lines (~5000 tokens)
- Use bullet points for scanability
- Include code examples where helpful
- Reference external files for detailed content
- Write for progressive disclosure
Progressive Disclosure Pattern
Optimize for efficient context usage:
- Metadata (~100 tokens): name + description loaded at startup
- Instructions (<5000 tokens): Full SKILL.md loaded when activated
- Resources (as needed): Reference files loaded on demand
Move detailed content to separate files:
references/REFERENCE.md- Technical detailsscripts/- Executable codeassets/- Templates, data files
Common Patterns
Good Description Examples
description: Extract text and tables from PDF files, fill forms, merge documents. Use when working with PDFs, document extraction, or form filling.
description: Write automated tests using RSpec, Capybara, and FactoryBot for Rails applications. Use when implementing features, fixing bugs, or when testing is mentioned.
Poor Description Examples
description: Helps with PDFs. # Too vague, no trigger keywords
description: A comprehensive system... # Doesn't say what it does
File References
Use relative paths from skill root:
See [detailed reference](references/REFERENCE.md) for more.
Run the script: scripts/process.py
Keep references one level deep - avoid nested chains.
Validation Checklist
Before finalizing a SKILL.md:
- [ ] Frontmatter has valid
nameanddescription - [ ] Name matches directory name
- [ ] Name follows character rules (lowercase alphanumeric + hyphens, no
--) - [ ] Description includes both what and when
- [ ] Description has relevant trigger keywords
- [ ] Optional fields follow spec limits (
compatibility<= 500 chars,allowed-toolsis space-delimited) - [ ] Main body is under 500 lines
- [ ] Instructions are actionable and clear
- [ ] Examples included where helpful
- [ ] Detailed content moved to reference files
- [ ] File references use relative paths
Validate with skills-ref validate ./my-skill when available.
Related Skills
rolemodel/ruby-version
testing
VerifiedTrustedCommunity
Verify what Ruby versions actually exist and install a specific Ruby via rbenv. Use BEFORE asserting that any Ruby version does or doesn't exist (e.g., "Ruby 4.0 isn't out yet", "the latest Ruby is 3.x", "Ruby X.Y.Z doesn't exist"). Also use when the user asks "what's the latest Ruby", "is Ruby X out", "does Ruby X.Y exist", "install Ruby", "switch to Ruby X", "what Ruby is installed", or mentions a specific Ruby version you're unsure about. Claude's training data may be out of date — run `check.sh` first.
6SKILL.mdUpdated May 28, 2026
rolemodel/trace
development
VerifiedTrustedCommunity
Trace code through the stack — upward to entry points, downward to data, or laterally across boundaries. Use when the user asks "where does this get called from", "what calls this method", "trace this through the stack", "how does this request flow", "where does this data come from", "follow this through the code", or pastes/selects a piece of code and wants to understand where it fits in the larger system.
5SKILL.mdUpdated Apr 25, 2026
rolemodel/sentry-top-issue
tools
VerifiedTrustedCommunity
Pick the single highest-priority unresolved Sentry issue and hand it off to a fixer skill. Use when triaging Sentry errors, running automated issue triage, or when asked to fix the top Sentry issue in a project.
5SKILL.mdUpdated Apr 25, 2026
rolemodel/rm-sentry-issue-fixer
tools
VerifiedTrustedCommunity
Find and fix issues from Sentry using MCP. Use when asked to fix Sentry errors, debug production issues, investigate exceptions, or resolve bugs reported in Sentry. Methodically analyzes stack traces, breadcrumbs, traces, and context to identify root causes.
5SKILL.mdUpdated Apr 25, 2026