randyhaylor/fine-grained-skill-builder
ai-tools/fine-grained-skill-builder/SKILL.md
Guide for building fine-grained skills where content is split into many small files to minimize tokens loaded per invocation. Use when creating or restructuring a skill to be token-efficient with section-based progressive disclosure.
development
Updated Apr 20, 2026
$ install --global
skillsauthnpx skillsauth add randyhaylor/enhanceclaude fine-grained-skill-builderInstall 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 20, 2026, 5:16 AM8.2s3 files scanned
SKILL.md
- name:
- fine-grained-skill-builder
- description:
- Guide for building fine-grained skills where content is split into many small files to minimize tokens loaded per invocation. Use when creating or restructuring a skill to be token-efficient with section-based progressive disclosure.
Fine-Grained Skill Building Approach
Goal
Minimize tokens loaded per invocation by breaking content into small, purpose-specific files loaded only when needed.
Structure
skill-name/
├── SKILL.md ← frontmatter + TOC only (links to section indexes)
├── section-a/
│ ├── index.md ← section TOC (links to content files)
│ ├── topic-1.md ← 1 table, 1 snippet, or ≤4 bullets
│ └── topic-2.md
├── section-b/
│ ├── index.md
│ └── ...
└── templates/
└── example.xml ← raw assets, no markdown wrapper
Rules
SKILL.mdbody: section list only — no content- Section
index.md: file list with one-line descriptions — no content - Content files: one concept each, as small as possible
- Assets (XML, scripts): raw files, not wrapped in markdown code blocks
Building with an Agent Team
- Identify sections (non-overlapping, independently writable)
- Create empty folder +
index.mdstub per section upfront - Write
SKILL.mdpointing to stubs - Spawn one agent per section in a single parallel call — each agent gets: its folder path, file list to create, and source material to extract from
- Agents complete concurrently; shut each down as it reports done
- Delete old source files
Key constraint for agent prompts: give each agent an explicit file list and source files. Vague scope causes overlap or gaps.
Related Skills
randyhaylor/ai-tools/xstate
tools
VerifiedTrustedCommunity
# XState v5 Quick Reference ## How to Look Up API Details For complete function signatures, types, and interfaces, **grep `api-reference.md`** — do NOT read it in full (12k+ lines). Example: ``` Grep pattern="createActor" path="~/.claude/skills/xstate/api-reference.md" output_mode="content" -C 5 ``` Then use `Read` with `offset`/`limit` to get the full section. This is the primary way to get precise technical info when the quick reference below isn't enough. ## Design Workflow Recommended
SKILL.mdUpdated Apr 20, 2026
randyhaylor/vscode-agent-teams
tools
VerifiedTrustedCommunity
Workaround for agent teams in VS Code extension where TeamCreate teammates cannot execute tools. Uses an echo-back-and-resume pattern where agents return tool requests instead of executing them directly.
SKILL.mdUpdated Apr 20, 2026
randyhaylor/typographic-hierarchy
development
VerifiedTrustedCommunity
Format documentation, READMEs, and structured text using header hierarchy where each level stands alone. Use when creating docs, research notes, summaries, or when user requests 'scannable,' 'well-structured,' 'skimmable,' or 'readable at multiple depths' output. Applies to markdown, technical specs, and any hierarchical text formatting.
SKILL.mdUpdated Apr 20, 2026
randyhaylor/test-driven-development
development
VerifiedTrustedCommunity
Enforce strict Test-Driven Development workflow: write one test, make it pass, verify, then proceed. Prevents over-implementation and ensures code matches requirements exactly. Use when implementing new features, adding settings, or building functionality incrementally.
SKILL.mdUpdated Apr 20, 2026