AGENT SKILL

skills

Quick reference for every available skill in this repo — name, one-line purpose, triggers, usage examples — without having to open each individual SKILL.md document. Triggers on: "/skills", "list skills", "what skills do you have", "show all skills", "skill cheatsheet", "skills help", "show me the skills", "what can you do". Usage: /skills — Compact reference table for all skills /skills <name> — Full detail for one skill (e.g. /skills explain) /skills --search "<term>" — Filter by name/description match

License 许可
MIT
最近更新
2026-11-10
Stars
★ 0
Forks
0

01 前言 Front Matter

name
skills
description
Quick reference for every available skill in this repo — name, one-line purpose, triggers, usage examples — without having to open each individual SKILL.md document. Triggers on: "/skills", "list skills", "what skills do you have", "show all skills", "skill cheatsheet", "skills help", "show me the skills", "what can you do". Usage: /skills — Compact reference table for all skills /skills <name> — Full detail for one skill (e.g. /skills explain) /skills --search "<term>" — Filter by name/description match
disable-model-invocation
true

02 资源文件 1

03 SKILL.md 正文

Skill Quick Reference

Explicit invocation only — host-neutral. disable-model-invocation: true enforces this in Claude Code and in VS Code Copilot, which reads .claude/skills/ and honours that key (verified against VS Code Agent Skills docs 2026-09-02). Hosts beyond those two are unverified, and a key cannot carry the reasoning anyway, so the rule is stated here as well.

Nothing here is destructive — this is a roster, not a gate — but a full skill listing is a poor answer to a question about the work, so render it when the user asked for it.

A discoverable, always-current reference for every skill in this bundle. Reads directly from skills/*​/SKILL.md frontmatter so the listing can never drift from reality — the same file Claude Code parses to register each skill.

This skill itself does NOT modify code. Pure read-and-render.

Worktree preflight — in a linked git worktree the synced tooling tree scripts/.claude-skills/ is absent — it is gitignored, so git worktree add does not populate it, and every command below that uses it dies on a bare MODULE_NOT_FOUND. Run npm run skills:hydrate first. If this repo defines no such script, references/worktree-preflight.md holds the entry to add — ask the user first, since it edits their package.json.


Step 0 — Pick the mode

Input Mode
/skills (no argument) List all — compact table of every skill
/skills <skill-name> Detail — full description, triggers, usage for one skill
/skills --search "<term>" Filter — show only skills whose name/description/triggers/usage contain the term (case-insensitive)

If <skill-name> doesn't match an existing skill, the helper suggests near-matches. Skill names are the directory names under skills/ (e.g. audit-code, explain, persona-test).


Step 1 — Invoke the helper

# List all skills
node scripts/skills-help.mjs

# Detail for one skill (SKILL_NAME = a directory name under skills/, e.g. audit-code)
node scripts/skills-help.mjs SKILL_NAME

# Filter by search term
node scripts/skills-help.mjs --search "<term>"

The helper auto-detects whether to render a compact table, a per-skill detail block, or a filtered list, and emits Markdown by default. Output is read-only — no files written unless --out <path> is passed.


Step 2 — Render the result

The helper output is already Markdown. Pass it through verbatim — do NOT re-summarise (the user asked for the reference; don't paraphrase).

If the helper exits non-zero with "skill not found", surface the suggestion line as-is and stop.


Output format reference

Compact list

# Available skills (N total)

| Skill | One-liner |
|---|---|
| `/audit-code` | Iteratively audit code against a plan with GPT + Gemini final gate. |
| `/brainstorm` ? | Multi-LLM concept-level brainstorming. |
| ... |

? = `disable-model-invocation: true` — Claude Code and VS Code Copilot will not
auto-trigger it; invoke explicitly via `/<name>`. Each locked skill also states
the rule in its body, for hosts that ignore the key.

Detail (e.g. /skills explain)

# /explain

Explain WHY a piece of code is structured the way it is.

**Triggers on:**
- why is this
- explain this code
- ...

**Usage:**
\`\`\`
/explain <file>                Explain the file's purpose + history
/explain --history "<topic>"   "Did we already solve this?" — cross-source search
\`\`\`

**Full SKILL.md:** `skills/explain/SKILL.md`

When to use this vs. typing /

  • Type / in Claude — for autocomplete on a skill you already know the name of (fastest single-skill lookup)
  • Run /skills — when you want to discover what's available, refresh your memory on a skill's options, or share a quick reference with a teammate (the output is copy-pasteable)
  • Open the SKILL.md directly — when you need the full "how it works" body (this skill only renders the frontmatter contract)

Sources

  • skills/*​/SKILL.md frontmatter — the canonical truth read by both Claude Code AND this helper. If /skills shows wrong info, the SKILL.md itself is wrong (not the helper).
  • .claude/skills/ mirror is intentionally ignored — that's the generated copy, not authoritative.

Cost

Zero external calls. Pure local file scan. Sub-100ms even with 50+ skills.


Reference files

File Summary Read when
references/worktree-preflight.md Worktree preflight remedy — the skills:hydrate npm script to add when a linked worktree lacks the tooling tree. A command dies with MODULE_NOT_FOUND in a linked worktree AND this repo has no skills:hydrate script.

04 同仓库更多 Skills

Lbstrydom
Lbstrydom/claude-engineering-skills

stated-absent

Negative fixture — the contract's stated string never appears in this file.

律师与法务
★ 0
Lbstrydom
Lbstrydom/claude-engineering-skills

nonexistent-implementation

Negative fixture — contract references an implementation file that does not exist.

律师与法务
★ 0
Lbstrydom
Lbstrydom/claude-engineering-skills

document-only-with-params

Negative fixture — a document-only gate illegally carries params (schema must refuse this fake-check pattern).

文档处理
★ 0
Lbstrydom
Lbstrydom/claude-engineering-skills

lying-skill

Fixture skill for the gate-honesty self-check — every gate here is deliberately dishonest.

Skill与智能体开发
★ 0
Lbstrydom
Lbstrydom/claude-engineering-skills

visual-audit

Math-first, deterministic visual/paint inspection — the 4th UX lens, complementing persona-test (journey), click-test (page), and nav-audit (system). Drives Playwright + computed styles + bounding boxes + CDP forced-pseudo-state to audit declared-token conformance, light/dark theme parity, layout physics, and affordance signifiers. A VLM is advisory-only and never gates. CI gate is drift-only on the changed contracted surface. Triggers on: "visual audit", "check styling consistency", "theme parity", "dark mode parity", "design token drift", "paint audit", "button/card consistency", "focus ring audit", "/visual-audit".

设计师测试与质量视觉设计
★ 0
Lbstrydom
Lbstrydom/claude-engineering-skills

ux-lock

Generate Playwright e2e specs. Two modes: 1. LOCK mode — pin a fix's DOM contract so it doesn't regress (default). 2. VERIFY mode — check that a /plan plan was actually implemented by parsing its Acceptance Criteria section and driving the live URL. VERIFY mode grades a plan against a RUNNING app. To judge the plan document itself, before anything is built, that is /audit-plan. Triggers on: "ux lock", "lock ux", "lock in the fix", "write regression spec", "generate e2e test for", "regression test for commit", "lock this fix", "verify the plan", "verify plan implementation", "check the plan was built", "audit frontend implementation", "did we ship the plan". Full command syntax: see the Usage section in this skill.

设计师律师与法务测试与质量前端开发
★ 0