Tools· AI Assistance & Agent Building

    skillsmith

    skillsmith is a meta-suite for building, auditing and distilling consistent Claude Code skills across four steps: Discover, Scaffold, Distill and Audit.

    structuringreviewingexecutableOpen Source
    Source code
    Available locally as a plugin suite; public source still being clarified, several projects of the same name found.
    skillsmith

    Description

    Strengths

    Full skill lifecycle
    Discover, Scaffold, Distill and Audit cover building a skill from the first idea through to quality checking.
    Seven defined file types
    entry points, tasks, templates, frameworks, context, checklists and rules each follow their own syntax specification defining structure and anti-patterns.
    Two-layer architecture
    the operational skill suite stays lean, the syntax specifications in the specs folder are loaded only on demand, not upfront.
    No runtime overhead
    Skillsmith consists entirely of markdown files, with no hooks, MCP servers or workspace data.
    Scalable builds
    for skill specifications with ten or more files, Scaffold offers a phased build through PAUL instead of generating everything in one step.

    Assessment

    AI features

    • Guided interview (Discover) works through question groups from identity to persona, scope and content, validating as it goes and deriving a structured skill specification from the answers.
    • Automatic generation (Scaffold) creates complete files with meaningfully pre-filled content from the specification, such as YAML frontmatter and the five XML sections of an entry point, or a task with user story, steps and acceptance criteria.
    • Concept-based chunking (Distill) breaks down raw material by concept rather than by chapter, producing for each chunk a core-concept synthesis, frameworks with usage triggers, fillable templates and if/then decision tools.
    • Compliance scoring (Audit) checks every file of a skill against its corresponding syntax spec and returns a compliance percentage with prioritized remediation suggestions, either individually or in batch across a whole directory.

    Suitable for

    • Teams that want to develop their own Claude Code skills following a consistent structure, from ideation through to the finished SKILL.md
    • Skill authors who want to audit existing skills against a syntax and quality standard
    • Projects that want to turn raw material such as books, courses or transcripts into reusable skill building blocks in a structured way
    • As a reference pattern for your own skill-creation process, independent of the specific public source

    Limitations and notes

    • Requires Claude Code Skillsmith is built for Claude Code's slash command system and assumes an existing .claude/commands/ structure.
    • Node.js only for installation Node.js 16 or higher is required solely for the install script, Skillsmith itself has no runtime dependencies.
    • Ecosystem features are optional registration in the BASE v2 knowledge graph and phased builds through PAUL require those companion tools, without them the four core workflows still work.
    • Generated files carry provenance data every generated file includes version, source and a Chris AI Systems footer note in its frontmatter.

    Quick start

    1. Install globally with npx @chrisai/skillsmith, which places the suite under ~/.claude/commands/skillsmith/ and makes it available in every workspace.
    2. For a project-only install use npx @chrisai/skillsmith --local instead, or set --config-dir to point at a custom Claude config path.
    3. In Claude Code, type /skillsmith to open the suite.
    4. For a new skill, run /skillsmith discover and work through the guided interview.
    5. Generate the complete skill directory from the resulting specification with /skillsmith scaffold.
    6. Turn raw material such as books, courses or transcripts into structured framework chunks with /skillsmith distill.
    7. Check existing skills against the syntax specs, individually or in batch, with /skillsmith audit [path].

    Tips

    • Audit relies on the compact rules for fast checking, while Scaffold uses the full specs in the specs folder for correct generation, which explains the difference between the two workflows.
    • For extensive skill specifications, the PAUL-backed phased build is worth using instead of generating everything in a single Scaffold run.
    • The seven syntax specifications in the specs folder can also be read independently of the workflows as a reference for your own skill conventions.
    • All tools in the ecosystem work standalone, Skillsmith does not require SEED or PAUL.

    Last reviewed: · Pricing, plans and features are a snapshot in time. Check the provider's own page before deciding.

    In the workshop this becomes your method.

    Whoever sees this process run once wants the agent behind it next. We build that in the workshop From Process to Agent.

    View workshops

    Related resources

    Browse all resources

    Conversation, not pitch

    Understand first, then decide. We take time for an initial conversation, without sales pressure, without obligation.

    Schedule a call