Skill Creator

OrganizationPopular

ccusage

skill-creator

Guides repo-local skill creation and updates. Use when adding or editing .agents/skills, root AGENTS.md routing, SKILL.md frontmatter, description trigger quality, references layout, skill scripts, or skill file line budgets.

Overview

Publisher	ccusage
Repository	`ccusage`
Skill name	`skill-creator`
Stars	19K
Forks	871
Bundled files	Instructions only
Links	Skill source Repository Homepage

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.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by ccusage on GitHub. Read the source before you install it.

Installation

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

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/ccusage/ccusage/tree/main/.agents/skills/skill-creator
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.

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/ccusage/ccusage.git /tmp/ccusage
mkdir -p .claude/skills
cp -r /tmp/ccusage/.agents/skills/skill-creator .claude/skills/skill-creator

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Skill Creator 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 Skill Creator 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 Skill Creator 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.

Skill Creator

.agents/skills/ is the source of truth for repo-local skills. .claude/skills is generated by agent-skills-nix through the Nix dev-shell hook and is gitignored — never edit or commit it.

nix/agent-skills.nix holds the local-only wiring, and the flake's nix-filter includes only .agents/skills in the skill source. There are intentionally no global agent-skills-nix targets and no git-hook skill sync here.

Adding or Editing a Skill

Add a skill when repeated repo work needs a workflow, local references, command sequences, or policy that should load on demand. Otherwise extend an existing skill.

Write .agents/skills/<skill-name>/SKILL.md with frontmatter plus concise Markdown.
Move conditional detail — long checklists, APIs, examples — into references/*.md and link each one from SKILL.md with a line saying when to read it.
Put deterministic repeated operations in scripts/ instead of prose.
Add the skill to the Skill Routing list in the root AGENTS.md so agents discover it.
Run just fmt after edits.

Frontmatter

Frontmatter carries two required fields, name and description.

The description is the primary discovery mechanism: third person, roughly 20-35 words, stating both what the skill does and the concrete triggers (file types, commands, task classes). A bare label like "Use for tests" leaves the agent unable to route. Frontmatter is always loaded, so keep it near Anthropic's ~100-word budget.

Optional routing fields: paths for Claude-style file matching (comma-separated globs or a YAML list) and globs as a cross-runtime compatibility hint — see .agents/skills/typescript/SKILL.md. Codex-style discovery reads the description, so the triggers belong there too.

Body

Write only what the agent cannot derive itself: commands with their exact flags, files to read, local conventions that are easy to miss, deliberate past decisions, and the validation expected after a change. Restating good practice the model already applies only competes with task context.

Progressive disclosure. The root AGENTS.md is loaded on every session, so it holds only what an agent needs before it knows what it is doing: repo shape, routing, gotchas. Anything that matters only once a task starts belongs in the skill that owns that task.
One home per rule. A rule in both AGENTS.md and a skill costs tokens twice and drifts. AGENTS.md keeps the one-line routing; the skill keeps the rule. Between two skills, cross-link by name instead of copying, and merge only when neither half earns its own trigger.
Point at real code. rust/adapters/codex/src/loader.rs, a fixture, or an existing test beats a paragraph paraphrasing the pattern.
Never transcribe CLI help. Usage lines, flag lists, and subcommand tables go stale and the agent can run <tool> --help. Write the judgment help output cannot give — when to reach for the tool, which of several tools to pick — and point at the tool.
Link external docs, don't paste them. When a URL is self-descriptive, put it on its own line with no title and no summary sentence; add context only when the reader needs to know why or when to open it.

https://simonwillison.net/2026/Jul/21/cat-and-thariq/

https://claude.com/blog/the-new-rules-of-context-engineering-for-claude-5-generation-models

Line Budgets

Some agents may preview only the first 200 lines of a file, so keep SKILL.md under 160 lines and each references/*.md under 180, with routing, safety, and workflow instructions above examples and background. Split longer material by decision point or workflow phase, but keep details that are always read together in one file rather than forcing several opens. Reference files are linked directly from SKILL.md; nested reference chains can be missed.

Audit lengths with:

sh
fd . .agents/skills -t f -e md -x wc -l {} | sort -nr

Frequently asked questions

What does the Skill Creator AI skill do?

Why use Skill Creator on TypingMind?

Because you install it once and use it with any model. Skill Creator 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 Skill Creator in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ccusage/ccusage/tree/main/.agents/skills/skill-creator. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Skill Creator?

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 Skill Creator?

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

Is the Skill Creator AI skill free?

It is published on GitHub by ccusage. Check the repository for licensing terms. 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

Control Ui E2e

openclaw

OrganizationPopular

Use when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks, mocked Gateway flows,…

Deslop

Diff-scoped AI-slop cleanup pass: strip comment slop, defensive-check slop, type-laundering, and style drift from the current branch diff before autoreview.

Discord Clawd

Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

Discrawl

Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Skill Creator

Adding or Editing a Skill

Frontmatter

Body

Line Budgets

Frequently asked questions

Related AI Skills

Set up your own AI workspace now