skill-building

Create, validate, package, and evaluate Claude skills with scripts and reference guides.

1|Updated Nov 11, 2012
One-click install
npx skills add https://github.com/fairchild/dotfiles --skill skill-building-fairchild
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-building
Source: https://github.com/fairchild/dotfiles/tree/main/agents/shared/first-party-skills/skill-building
Command: npx skills add https://github.com/fairchild/dotfiles --skill skill-building-fairchild

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve? Writing effective agent skills requires knowing frontmatter conventions, progressive disclosure patterns, and defensive writing techniques, and evaluating third-party skills for security and quality is time-consuming without a structured process. ## Core Features & Use Cases - Skill Creation Workflow: Scaffold new skills with init_skill.py, write SKILL.md following proven patterns, validate with quick_validate.py, and package into distributable .skill files. - Third-Party Skill Evaluation: Run a 7-step evaluation covering source resolution, structural checks, security scanning, quality rubric scoring, context budget analysis, and report generation. - Defensive Writing Guidance: References cover testing methodology, rationalization tables, workflow patterns, and description refinement to make skills resilient against agent shortcut-taking. - Use Case: Before installing a skill found on GitHub, run the evaluation workflow to fetch the repo, scan it for security patterns like credential access or obfuscation, estimate its token cost, and produce an ADOPT/SKIP recommendation report. ## Quick Start Ask the agent to create a new skill called my-skill using the skill-building workflow, then validate it with the quick_validate script.

Frequently Asked Questions about skill-building

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new Claude skill from scratch?▼

Run init_skill.py with a hyphen-case name and output path to scaffold the directory, then edit the generated SKILL.md frontmatter and body. Validate with quick_validate.py and package with package_skill.py when finished.

How do I evaluate a third-party skill before installing it?▼

Follow the 7-step workflow: fetch the source, check structure, run security_scan.py for pattern analysis, assess quality against the rubric, measure context budget, evaluate value overlap, and generate a report with an ADOPT or SKIP recommendation.

What makes a good skill description field?▼

The description is the primary triggering mechanism, so it must state what the skill does plus specific trigger conditions and phrases users would type. Keep it between 50 and 1024 characters, avoid internal mechanics, and front-load the domain noun.

What security risks should I check in a skill?▼

Scan for credential access like os.environ and .ssh paths, network exfiltration via requests.post, code execution through eval or subprocess, persistence hooks in frontmatter, and obfuscation such as long base64 strings. Any CRITICAL finding without justification means FAIL.

How long should a SKILL.md file be?▼

Keep the body under 500 lines and around 500 words, with metadata near 100 words. Move detailed content into references/ files loaded on demand, keeping references one level deep from SKILL.md.

Why does my skill not trigger when expected?▼

The description field controls invocation matching, so vague or workflow-summary descriptions fail to trigger. Rewrite it with concrete trigger phrases and verbs users actually type, then verify with the refining-skill-descriptions checklist.