Agent skill

Auto Skill Builder

by tradecatlabs in tradecatlabs/vibe-coding-cn

Meta-skill that turns docs, APIs, code or specs into a reusable skill with references and a quality gate, and refactors skills that are unclear or misfire.

MITAuto-check passedAgent Workflows

Install Auto Skill Builder

skills CLI
$ npx skills add tradecatlabs/vibe-coding-cn --skill auto-skill -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tradecatlabs/vibe-coding-cn auto-skill --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tradecatlabs/vibe-coding-cn.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/auto-skill .claude/skills/auto-skill && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
auto-skill
GitHub stars
17k
Used in
1 other repo
Token cost
~2.4k tokens
SKILL.md length
567 words
Files
25 (incl. scripts, references, assets)
Skills in repo
17
Repo updated
First seen
Licence
MIT

At a glance

Meta-skill that turns docs, APIs, code or specs into a reusable skill with references and a quality gate, and refactors skills that are unclear or misfire.

  • Works in 4 steps: A concrete directory layout (typically… → An actionable SKILL.md with decidable… → Long-form docs moved to references/ with… → …
  • Creating a skill from documentation, specs or a repository
  • SKILL.md covers When to Use This Skill, Not For / Boundaries, Quick Reference and Examples, plus 5 more sections
  • Runs Shell scripts from its folder

What it does

A meta-skill that turns scattered domain material such as docs, APIs, code and specs into a reusable skill, with `SKILL.md` as the entry point, `references/` for long-form evidence and optional `scripts/` and `assets/` for scaffolding and templates. It also refactors existing skills that are too long, unclear or inconsistent, or that misfire, and helps design reliable activation through frontmatter, triggers and boundaries.

Deliverables are fixed: a concrete directory layout, an actionable `SKILL.md` with decidable triggers, boundaries and reproducible examples, long-form material moved into `references/` with an index, and a pre-delivery quality gate checklist. It does not invent external facts and asks one to three questions when inputs are missing. A linked Skill Seekers tool can draft a first skill from a documentation site, a GitHub repository or a PDF, with bootstrap, run and import scripts, and the package ships complete and minimal templates, an anti-pattern list and a spec reference.

When your agent uses it

  • Creating a skill from documentation, specs or a repository
  • Refactoring a skill that is too long or fires at the wrong times
  • Splitting a large skill into a quick reference plus a references folder
  • Adding a quality gate checklist and validator to a skill

Example prompts

  • “Turn the Stripe webhooks docs into a skill with a quick reference and a references folder.”
  • “Refactor my deploy skill. It is too long and triggers on unrelated requests.”
  • “Generate a first-draft skill from this GitHub repository with Skill Seekers and import it.”

Requirements

  • Skill Seekers, linked as a submodule and bootstrapped with the bundled script
  • A shell to run the helper scripts

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. A concrete directory layout (typically skills//)
  2. An actionable SKILL.md with decidable triggers, boundaries, and reproducible examples
  3. Long-form docs moved to references/ with a references/index.md
  4. A pre-delivery checklist (Quality Gate)

What it can do on your machine

Read from SKILL.md and the folder at commit 0a7fdf4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 4 files in scripts/ (Shell, from the files we listed), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • support.claude.com
    • docs.claude.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Auto Skill Builder loads about 2.4k tokens when it runs, and up to ~7.3k if it reads all its reference files. Until then it costs about 58 tokens; SKILL.md has 567 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~2.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from tradecatlabs/vibe-coding-cn at commit 0a7fdf4, republished under its MIT licence (© tradecatlabs). 567 words, ~2,368 tokens.

Download SKILL.mdSave it as .claude/skills/auto-skill/SKILL.md (or your agent's skills folder). This skill also uses 24 other files; get the full folder from GitHub.
name
auto-skill
description
Claude Skills meta-skill: extract domain material (docs/APIs/code/specs) into a reusable Skill (SKILL.md + references/scripts/assets), and refactor existing Skills for clarity, activation reliability, and quality gates.

Auto Skill

Turn scattered domain material into a Skill that is reusable, maintainable, and reliably activatable:

  • SKILL.md as the entrypoint (triggers, constraints, patterns, examples)
  • references/ for long-form evidence and navigation
  • optional scripts/ and assets/ for scaffolding and templates

When to Use This Skill

Trigger this meta-skill when you need to:

  • Create a new Skill from scratch from docs/specs/repos
  • Refactor an existing Skill (too long, unclear, inconsistent, misfires)
  • Design reliable activation (frontmatter + triggers + boundaries)
  • Extract a clean Quick Reference from large material
  • Split long content into navigable references/
  • Add a quality gate and a validator

Not For / Boundaries

This meta-skill is NOT:

  • A domain Skill by itself (it builds domain Skills)
  • A license to invent external facts (if the material does not prove it, say so and add a verification path)
  • A substitute for required inputs (if inputs are missing, ask 1-3 questions before proceeding)

Quick Reference

Deliverables (What You Must Produce)

Your output MUST include:

  1. A concrete directory layout (typically skills/<skill-name>/)
  2. An actionable SKILL.md with decidable triggers, boundaries, and reproducible examples
  3. Long-form docs moved to references/ with a references/index.md
  4. A pre-delivery checklist (Quality Gate)
Built-in Tool (Mandatory): Skill Seekers (Linked)

This meta-skill exposes the tools/external/Skill_Seekers-development submodule through a relative symlink so you can generate a first-draft Skill from:

  • Documentation websites
  • GitHub repositories
  • PDFs

Bootstrap dependencies (once):

bash
./skills/auto-skill/scripts/skill-seekers-bootstrap.sh

Run Skill Seekers (from linked source):

bash
./skills/auto-skill/scripts/skill-seekers.sh -- --version
./skills/auto-skill/scripts/skill-seekers.sh -- scrape --config ./skills/auto-skill/scripts/Skill_Seekers-development/configs/react.json
./skills/auto-skill/scripts/skill-seekers.sh -- github --repo facebook/react --name react

Import the generated skill into this repo's canonical skills/ tree:

bash
./skills/auto-skill/scripts/skill-seekers-import.sh react
./skills/auto-skill/scripts/skill-seekers-import.sh react --force

Update the linked source by moving the tools/external/Skill_Seekers-development submodule pointer directly. The update helper is guarded to avoid overwriting the linked repository.

bash
./skills/auto-skill/scripts/skill-seekers-update.sh --dry-run
skill-name/
|-- SKILL.md              # Required: entrypoint with YAML frontmatter
|-- references/           # Optional: long-form docs/evidence/index
|   `-- index.md          # Recommended: navigation index
|-- scripts/              # Optional: helpers/automation
`-- assets/               # Optional: templates/configs/static assets

The truly minimal version is just SKILL.md (you can add references/ later).

YAML Frontmatter (Required)
yaml
---
name: skill-name
description: "What it does + when to use (activation triggers)."
---

Frontmatter rules:

  • name MUST match ^[a-z][a-z0-9-]*$ and SHOULD match the directory name
  • description MUST be decidable (not "helps with X") and include concrete trigger keywords
Minimal SKILL.md Skeleton (Copy/Paste)
markdown
---
name: my-skill
description: "[Domain] capability: includes [capability 1], [capability 2]. Use when [decidable triggers]."
---

# my-skill Skill

One sentence that states the boundary and the deliverable.

## When to Use This Skill

Trigger when any of these applies:
- [Trigger 1: concrete task/keyword]
- [Trigger 2]
- [Trigger 3]

## Not For / Boundaries

- What this skill will not do (prevents misfires and over-promising)
- Required inputs; ask 1-3 questions if missing

## Quick Reference

### Common Patterns

**Pattern 1:** one-line explanation
```text
[command/snippet you can paste and run]

Examples

Example 1
  • Input:
  • Steps:
  • Expected output / acceptance:
Example 2
Example 3

References

  • references/index.md: navigation
  • references/...: long-form docs split by topic

Maintenance

  • Sources: docs/repos/specs (do not invent)
  • Last updated: YYYY-MM-DD
  • Known limits: what is explicitly out of scope

### Authoring Rules (Non-negotiable)

1. Quick Reference is for short, directly usable patterns
   - Keep it <= 20 patterns when possible.
   - Anything that needs paragraphs of explanation goes to `references/`.
2. Activation must be decidable
   - Frontmatter `description` should say "what + when" with concrete keywords.
   - "When to Use" must list specific tasks/inputs/goals, not vague help text.
   - "Not For / Boundaries" is mandatory for reliability.
3. No bluffing on external details
   - If the material does not prove it, say so and include a verification path.

### Workflow (Material -> Skill)

Do not skip steps:
0. If your source material is a docs site / GitHub repo / PDF: generate a first draft with the linked Skill Seekers tool, then import into `skills/<skill-name>/`
1. Scope: write MUST/SHOULD/NEVER (three sentences total is fine)
2. Extract patterns: pick 10-20 high-frequency patterns (commands/snippets/flows)
3. Add examples: >= 3 end-to-end examples (input -> steps -> acceptance)
4. Define boundaries: what is out-of-scope + required inputs
5. Split references: move long text into `references/` + write `references/index.md`
6. Apply the gate: run the checklist and the validator

### Quality Gate (Pre-delivery Checklist)

Minimum checks (see `references/quality-checklist.md` for the full version):
1. `name` matches `^[a-z][a-z0-9-]*$` and matches the directory name
2. `description` states "what + when" with concrete trigger keywords
3. Has "When to Use This Skill" with decidable triggers
4. Has "Not For / Boundaries" to reduce misfires
5. Quick Reference is <= 20 patterns and each is directly usable
6. Has >= 3 reproducible examples
7. Long content is in `references/` and `references/index.md` is navigable
8. Uncertain claims include a verification path (no bluffing)
9. Reads like an operator's manual, not a documentation dump

Validate locally:

```bash
# From repo root (basic validation)
./skills/auto-skill/scripts/validate-skill.sh skills/<skill-name>

# From repo root (strict validation)
./skills/auto-skill/scripts/validate-skill.sh skills/<skill-name> --strict

# From skills/auto-skill/ (basic validation)
./scripts/validate-skill.sh ../<skill-name>

# From skills/auto-skill/ (strict validation)
./scripts/validate-skill.sh ../<skill-name> --strict
Show full SKILL.md (223 more words)Show less
Tools & Templates

Generate a new Skill skeleton:

bash
# From repo root (generate into ./skills/)
./skills/auto-skill/scripts/create-skill.sh my-skill --full --output skills

# From auto-skill/ (generate into ../ i.e. ./skills/)
./scripts/create-skill.sh my-skill --full --output ..

# Minimal skeleton
./skills/auto-skill/scripts/create-skill.sh my-skill --minimal --output skills

Templates:

  • assets/template-minimal.md
  • assets/template-complete.md

Examples

Example 1: Create a Skill from Docs
  • Input: an official doc/spec + 2-3 real code samples + common failure modes
  • Steps:
    1. Run create-skill.sh to scaffold skills/<skill-name>/
    2. Write frontmatter description as "what + when"
    3. Extract 10-20 high-frequency patterns into Quick Reference
    4. Add >= 3 end-to-end examples with acceptance criteria
    5. Put long content into references/ and wire references/index.md
    6. Run validate-skill.sh --strict and iterate
Example 2: Refactor a "Doc Dump" Skill
  • Input: an existing SKILL.md with long pasted documentation
  • Steps:
    1. Identify which parts are patterns vs. long-form explanation
    2. Move long-form text into references/ (split by topic)
    3. Rewrite Quick Reference as short copy/paste patterns
    4. Add or fix Examples until they are reproducible
    5. Add "Not For / Boundaries" to reduce misfires
Example 3: Validate and Gate a Skill
  • Input: skills/<skill-name>/
  • Steps:
    1. Run validate-skill.sh (non-strict) to get warnings
    2. Fix frontmatter/name mismatches and missing sections
    3. Run validate-skill.sh --strict to enforce the spec
    4. Run the scoring rubric in references/quality-checklist.md before shipping

References

Local docs:

  • references/index.md
  • references/skill-spec.md
  • references/quality-checklist.md
  • references/anti-patterns.md
  • references/README.md (upstream official reference)
  • references/skill-seekers.md (linked tool integration + workflow)

External (official):

Maintenance

  • Sources: local spec files in skills/auto-skill/references/ + upstream official docs in references/README.md
  • Last updated: 2025-12-14
  • Known limits: validate-skill.sh is heuristic; strict mode assumes the recommended section headings

© tradecatlabs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 24 other files (scripts, references, assets) in skills/auto-skill of tradecatlabs/vibe-coding-cn.

  • SKILL.md
  • AGENTS.md
  • README.md
  • assets/AGENTS.md
  • assets/README.md
  • assets/template-complete.md
  • assets/template-minimal.md
  • references/AGENTS.md
  • references/README.md
  • references/anti-patterns.md
  • references/index.md
  • references/quality-checklist.md
  • references/skill-seekers.md
  • references/skill-spec.md
  • scripts/AGENTS.md
  • scripts/README.md
  • scripts/Skill_Seekers-development
  • scripts/create-skill.sh
  • … and 7 more

Open the folder on GitHubat commit 0a7fdf4

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in tradecatlabs/vibe-coding-cn, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Auto Skill Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Auto Skill Builder compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Auto Skill Builder this skilltradecatlabs/vibe-coding-cn17k1 repos~2.4kAutomated safety check: PassMIT
Skill Release Gaterohitg00/ai-engineering-from-scratch66k—~1kAutomated safety check: PassMIT
Skill Authoring and Refactoring2025Emma/vibe-coding-cn23k2 repos~2kAutomated safety check: PassMIT
Skill Seekers Builderyusufkaraaslan/Skill_Seekers15k—~760Automated safety check: PassMIT
DBS Skill Makerdontbesilent2025/dbskill11k—~1.2kAutomated safety check: PassCustom licence
LubanLearnPrompt/luban-skill958—~3.1kAutomated safety check: PassMIT

Similar skills

  • Skill Release Gate

    rohitg00/ai-engineering-from-scratch

    Evaluates an Agent Skill bundle before release for structure, trigger quality, artifact improvement, script correctness, safety, installed-tree integrity and host portability.

    66k GitHub stars~1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Skill Authoring and Refactoring

    2025Emma/vibe-coding-cn

    Builds new skills from scattered docs, specs or code, and refactors existing skills for clear triggers, reliable activation and a quality checklist.

    23k GitHub starsUsed in 2 repos~2k tokens
    Agent WorkflowsAuto-check passed
  • Skill Seekers Builder

    yusufkaraaslan/Skill_Seekers

    Detects the type of a knowledge source and uses the Skill Seekers MCP tools to turn docs, repos, PDFs or videos into packaged AI skills.

    15k GitHub stars~760 tokensUpdated 8 days ago
    Agent WorkflowsAuto-check passed
  • DBS Skill Maker

    dontbesilent2025/dbskill

    Turns a problem you keep running into into a single installable, tested skill, and prepares a GitHub repository only when you ask to share it.

    11k GitHub stars~1.2k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Luban

    LearnPrompt/luban-skill

    鲁班(Luban)——Skill打磨工坊。把一个"能用的Skill"打磨成"能被理解、能被安装、能被传播、能被验证、能持续进化"的公共Skill资产。

    958 GitHub stars~3.1k tokensUpdated 3 mo ago
    Agent WorkflowsAuto-check passed
  • Build Cs Skill

    codestable/CodeStable

    CodeStable skill authoring and evolution protocol. An agent skill from codestable/CodeStable.

    1.1k GitHub stars~3k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

More from tradecatlabs/vibe-coding-cn

All 17 skills in this repo
  • Web3 Smart Contract Grep Arsenal

    tradecatlabs/vibe-coding-cn

    A master set of ten grep command blocks that surface likely vulnerability classes in Solidity source within the first 30 minutes of auditing a new protocol.

    17k GitHub starsUsed in 2 repos~3.3k tokens
    Auto-check passed
  • Auto tmux Operator

    tradecatlabs/vibe-coding-cn

    Operates tmux sessions like an administrator: reads pane output, sends keys, inspects many panes at once, and coordinates multiple AI terminals through a swarm state script, built on oh-my-tmux.

    17k GitHub stars~4.7k tokensUpdated today
    Auto-check passed
  • Web3 Bug Bounty AI Tools

    tradecatlabs/vibe-coding-cn

    A selection guide to AI-driven tools for Web3 bug bounty work, from autonomous web pentesters to smart contract bug finders, with notes on authorization.

    17k GitHub starsUsed in 2 repos~3.9k tokens
    Auto-check: warnings
  • Runs Slither and Mythril against Solidity contracts to find reentrancy, overflow and access-control bugs before mainnet deployment, then triages and reports findings.

    17k GitHub starsUsed in 1 repo~738 tokens
    Auto-check passed
  • Math Computation

    tradecatlabs/vibe-coding-cn

    Runs reproducible math computations and counterexample searches with SymPy, NumPy and mpmath, logging evidence without presenting results as proofs.

    17k GitHub stars~881 tokensUpdated today
    Auto-check passed
  • DeFi Smart Contract Bug Classes

    tradecatlabs/vibe-coding-cn

    Reference for ten classes of DeFi smart contract bugs, each with root cause, vulnerable code, fix, grep patterns and paid examples, for audits and bug bounty reviews.

    17k GitHub starsUsed in 2 repos~10k tokens
    Auto-check passed

Works with

Categories

Questions about Auto Skill Builder

What does Auto Skill Builder do?

Meta-skill that turns docs, APIs, code or specs into a reusable skill with references and a quality gate, and refactors skills that are unclear or misfire. md` as the entry point, `references/` for long-form evidence and optional `scripts/` and `assets/` for scaffolding and templates. It also refactors existing skills that are too long, unclear or inconsistent, or that misfire, and helps design reliable activation through frontmatter, triggers and boundaries.

When should I use Auto Skill Builder?

Auto Skill Builder fits situations like: creating a skill from documentation, specs or a repository; refactoring a skill that is too long or fires at the wrong times; splitting a large skill into a quick reference plus a references folder; adding a quality gate checklist and validator to a skill.

How do I install Auto Skill Builder in Claude Code?

Run `npx skills add tradecatlabs/vibe-coding-cn --skill auto-skill -a claude-code`. Or copy the skill folder (skills/auto-skill in tradecatlabs/vibe-coding-cn) into .claude/skills/auto-skill in your project. Claude Code loads it when a task matches its description.

How do I install Auto Skill Builder in Codex?

Run `npx skills add tradecatlabs/vibe-coding-cn --skill auto-skill -a codex`. Or copy the skill folder (skills/auto-skill in tradecatlabs/vibe-coding-cn) into .agents/skills/auto-skill in your project. Codex loads it when a task matches its description.

Can I use Auto Skill Builder in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tradecatlabs/vibe-coding-cn --skill auto-skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/auto-skill, .gemini/skills/auto-skill, .github/skills/auto-skill and .opencode/skills/auto-skill in your project.

What does Auto Skill Builder need to run?

Going by SKILL.md and its folder, Auto Skill Builder needs a shell for the scripts in its folder. Our summary lists: Skill Seekers, linked as a submodule and bootstrapped with the bundled script; A shell to run the helper scripts.

Does Auto Skill Builder access the network?

SKILL.md names 2 domains. As links in the text: support.claude.com and docs.claude.com. This is read from the text; nothing was executed.

Is Auto Skill Builder safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Auto Skill Builder use?

Auto Skill Builder is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Auto Skill Builder use?

About 2.4k tokens (SKILL.md is roughly 9.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.9k tokens, read only when the agent opens those files.

What are the alternatives to Auto Skill Builder?

Skills that share tags, products or a category with Auto Skill Builder: Skill Release Gate (rohitg00/ai-engineering-from-scratch, 66k stars), Skill Authoring and Refactoring (2025Emma/vibe-coding-cn, 23k stars), Skill Seekers Builder (yusufkaraaslan/Skill_Seekers, 15k stars) and DBS Skill Maker (dontbesilent2025/dbskill, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Auto Skill Builder?

tradecatlabs (a GitHub user) maintains it in tradecatlabs/vibe-coding-cn, which has 17,300 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 9, 2026.

Source: tradecatlabs/vibe-coding-cn on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.