Craft Skill logo

Craft Skill

Community
danielvm-git
craft-skill

Create new bigpowers skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill for the bigpowers lifecycle.

Overview

Publisherdanielvm-git
Repositorybigpowers
Skill namecraft-skill
Stars
206
Forks
18
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by danielvm-git on GitHub. Read the source before you install it.

Installation

Install the Craft Skill AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/danielvm-git/bigpowers.git /tmp/bigpowers
mkdir -p .claude/skills
cp -r /tmp/bigpowers/skills/craft-skill .claude/skills/craft-skill
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Craft Skill in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Craft Skill on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Craft Skill is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Craft Skill

HARD GATE — Do NOT name a skill without a two-word verb-noun pair. Do NOT merge a new skill without running sync-skills.sh. Generated .cursor/rules/ and .gemini/ artifacts MUST match the source SKILL.md.

CSO Description Discipline (e45s02)

The YAML description is the Catalog Selection Object — the only field agents see when picking a skill.

RuleLimit
Max length1024 characters
VoiceThird person
ContentCapability + Use when … triggers only
ForbiddenWorkflow steps, phase chains, numbered lists, → verify:, HARD GATE prose

Move process detail into the SKILL.md body or REFERENCE.md — never into description.

Agentic STE body discipline (e79s02)

Skill-body instructional prose MUST follow AGENTIC-STE.md.

RuleLimit
Sentence length≤20 words per instruction sentence
VoiceImperative, active
Directive termsMUST, MUST NOT, NEVER, ALWAYS, DO, DO NOT
Banned modalsshould, might, could, may, consider, try, generally, typically
ScopeSKILL.md body only — not YAML description, not terse-mode output

HARD GATE — Do NOT merge a new or edited skill until bash scripts/validate-agentic-ste.sh --strict skills/<name>/SKILL.md exits 0. Fix violations before sync-skills.sh.

Process

  1. Gather requirements — ask user about:

    • What task/domain does the skill cover?
    • Which use cases must the skill handle?
    • Does it need executable scripts or just instructions?
    • Any reference materials to include?
    • What specs/ output does it produce (if any)?
  2. Verify Principles — Ensure the skill aligns with PRINCIPLES.md:

    • Is it atomic (verb-noun)?
    • Is it "deep" (simple interface, complex internal logic)?
    • Does it include Hard Gates?
    • Is it verifiable with a .feature file?
  3. Draft the skill — create:

    • SKILL.md with concise instructions (see REFERENCE.md for template)
    • Additional reference files if content exceeds 100 lines
    • Utility scripts if deterministic operations needed

    Auto-skill from library README: When user provides a library README or API docs URL, extract triggers and HARD GATEs. Draft verify commands and specs/ output into SKILL.md. Do NOT invent APIs not in the source.

  4. Add model: frontmatter (haiku | sonnet | opus) per model-profiles.md.

STREAM CONTINUITY — When writing file content, output in continuous chunks of ~200 lines. Do not pause. Continue immediately until complete. If you need time, emit a placeholder comment rather than going silent.

  1. Review with user — present draft and ask:

    • Does this cover your use cases?
    • Anything missing or unclear?
    • Does any section need more or less detail?
  2. Completion-honesty gate (HARD GATE — e45s02) — Before declaring done:

    • Run bash scripts/validate-skill-description.sh skills/<name>/SKILL.md — must exit 0
    • Run bash scripts/validate-agentic-ste.sh --strict skills/<name>/SKILL.md — must exit 0 (e79s02)
    • Run bash scripts/sync-skills.sh — must complete without error
    • Run bash scripts/run-skill-verify.sh <name> if the skill defines a verify command
    • Show terminal output for each — narration without evidence is rejected

Naming Rules

Every skill name must be a two-word verb-noun pair. See REFERENCE.md for full rules, examples, and documented exceptions.

specs/ Output

If the skill produces written output, it goes in specs/ at the project root. Document the output file path in the skill body and in CONVENTIONS.md's output files table.

Review Checklist

After drafting, verify:

  • Name is a two-word verb-noun pair (or follows grill-me exception)
  • Description < 1024 chars, triggers only, no workflow-summary leakage
  • Description includes triggers ("Use when...")
  • SKILL.md under 100 lines
  • No time-sensitive info
  • Consistent terminology with CONVENTIONS.md
  • specs/ output documented if applicable
  • validate-skill-description.sh exits 0
  • validate-agentic-ste.sh --strict exits 0 (e79s02)
  • sync-skills.sh run to propagate to Cursor/Gemini
  • bash scripts/validate-skill-catalog.sh passes for the new skill (HARD GATE — completion honesty)

HARD GATE — Do NOT declare the skill done until bash scripts/validate-skill-catalog.sh --strict --skill <name> exits 0. Validator enforces verb-noun name, HARD GATE block, description ≤1024 chars, and → verify: command.

Verify

→ verify: bash scripts/validate-skill-catalog.sh --strict --skill craft-skill && bash scripts/validate-skill-description.sh skills/craft-skill/SKILL.md

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Craft Skill AI skill do?

Create new bigpowers skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill for the bigpowers lifecycle.

Why use Craft Skill on TypingMind?

Because you install it once and use it with any model. Craft Skill is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Craft Skill in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/danielvm-git/bigpowers/tree/main/skills/craft-skill. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Craft Skill?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Craft Skill?

As many as you like. As long as a model supports skills, you can use Craft Skill with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Craft Skill AI skill free?

Yes. It is published on GitHub by danielvm-git under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇