sft-skill-anatomy

Analyze Claude Code skill structure and section rationale for audits.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/steltz/skill-factory --skill sft-skill-anatomy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sft-skill-anatomy
Source: https://github.com/steltz/skill-factory/tree/main/plugins/skill-factory-toolkit/skills/sft-skill-anatomy
Command: npx skills add https://github.com/steltz/skill-factory --skill sft-skill-anatomy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps learners study how Claude Code skills are structured and why each section exists, enabling consistent skill design and faster audits.

Core Features & Use Cases

  • Structural mapping: links every section to the CSO framework and explains design rationale for re-use across skills.
  • Cross-skill references: provides overview and comparison to highlight patterns and common pitfalls.
  • Practical guidance: demonstrates how to apply the anatomy principles to new skills and audits.

Quick Start

Refer to SKILL.md in this skill's folder to study the anatomy and consult skill-analyses.md for deeper maps.

Frequently Asked Questions about sft-skill-anatomy

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

FAQPage Schema
How do I structure a Claude Code skill to meet authoring guidelines?

Structure Claude Code skills using a frontmatter-based name and description, cross-skill mappings, and documented section principles. This enforces consistent architecture and clear design rationale aligned with the CSO framework.

Why does each section exist in a skill anatomy reference guide?

Each section in a skill anatomy reference guide exists to map structural components to the CSO framework, explaining design rationale for re-use and highlighting common pitfalls across skills.

What is the best way to audit skill structures for consistent architecture?

Audit skill structures by applying anatomy principles that check for frontmatter-based descriptions, cross-skill references, and documented section principles to ensure reliable mapping to authoring guidelines.

How do cross-skill references improve skill design and documentation?

Cross-skill references improve design by providing structural overviews and comparisons that highlight patterns across skills, enabling faster audits and consistent architecture.

Can I use skill anatomy principles to design new skills from scratch?

Yes, skill anatomy principles demonstrate how to apply structural mapping and documented section rationale to new skills, ensuring they meet authoring guidelines and maintain consistent architecture.

When should I not use a reference-driven skill structure?

Avoid reference-driven skill structures when your project lacks cross-skill dependencies or when frontmatter-based mapping and CSO framework alignment are unnecessary for the skill's intended scope.