协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
create-skill【开发与工程】Create a new SKILL.md file following the Agent Skills open standard (agentskills.io). Covers frontmatter schema, section structure, writing effective procedures with Expected/On failure pairs, validation checklists, cross-referencing, and registry integration. Use when codifying a repeatable procedure for agents, adding a new capability to the skills…
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
書代系可消以行具法之 SKILL.md。
skills/_registry.yml 之 48 域之一各技居己目:
mkdir -p skills/<skill-name>/
命規:
submit-to-cran、非 SubmitToCRANcreate-、setup-、write-、deploy-、configure-create-r-dockerfile 非 create-dockerfile得: 目 skills/<skill-name>/ 存、名循小寫 kebab-case 起於動。
敗: 名不起動→重命目。察命衝:ls skills/ | grep <keyword> 保無存技含重名。
---
name: skill-name-here
description: >
One to three sentences plus key activation triggers. Must be clear
enough for an agent to decide whether to activate this skill from
the description alone. Max 1024 characters. Start with a verb.
license: MIT
allowed-tools: Read Write Edit Bash Grep Glob # optional, experimental
metadata:
author: Philipp Thoss
version: "1.0"
domain: general
complexity: intermediate
language: R | TypeScript | Python | Docker | Rust | multi
tags: comma, separated, lowercase, tags
---
必欄:name、description
可欄:license、allowed-tools(試)、metadata、compatibility
備規:
complexity:basic(< 5 步、無邊例)、intermediate(5-10 步、含判)、advanced(10+ 步、深域)language:主語;跨語技用 multitags:3-6 標為發;含域名得: YAML frontmatter 無誤解析、name 合目名、description 於 1024 字符內含明觸。
敗: 驗 YAML 合 --- 界、版串正引(如 "1.0" 非 1.0)、述欄 > 多行折文正。
# Skill Title (Imperative Verb Form)
One paragraph: what this skill accomplishes and the value it provides.
標當合 name 而為人讀式。「Submit to CRAN」非「submit-to-cran」。
得: 頂 # 題為命令式後一段述技成何。
敗: 標為名短非動短→重書。「Package Submission」為「Submit to CRAN」。
列 3-5 觸件——代當活之具景:
## When to Use
- Starting a new R package from scratch
- Converting loose R scripts into a package
- Setting up a package skeleton for collaborative development
自代角書。此為代察定活之件。
注:主觸件亦當現於
descriptionfrontmatter,彼於發現階全體前讀。## When to Use予細與脈。
得: 3-5 點述代當活此技之具可觀件。
敗: 觸感泛(「須作何時」)→自代角書:何可觀態或用請觸活?
分必與可。具於型與默:
## Inputs
- **Required**: Package name (lowercase, no special characters except `.`)
- **Required**: One-line description of the package purpose
- **Optional**: License type (default: MIT)
- **Optional**: Whether to initialize renv (default: yes)
得: 入節明分必與可、各含型提與默值(若適)。
敗: 參型歧→括加具例:「Package name (lowercase, no special characters except .)」。
此為技核。各步循此模:
### Step N: Action Title
Context sentence explaining what this step accomplishes.
\```language
concrete_code("that the agent can execute")
\```
**Expected:** What success looks like. Be specific — file created, output matches pattern, command exits 0.
**On failure:** Recovery steps. Don't just say "fix it" — provide the most common failure cause and its resolution.
效步書:
為譯書:
得: 行節含 5-12 編步、各含具碼、**Expected:** 果、**On failure:** 復。
敗: 步缺碼→加真令或設。Expected/On failure 缺→即書——可敗步皆需二。
法畢後代行之清:
## Validation
- [ ] Criterion 1 (testable, binary pass/fail)
- [ ] Criterion 2
- [ ] No errors or warnings in output
各項須客可驗。「碼潔」差。「devtools::check() 返零誤」佳。
得: markdown 清(- [ ])含 3-8 二分通敗準、代可程或察驗。
敗: 代主觀準為量可。「備善」為「諸出函含 @param、@return、@examples roxygen 標」。
3-6 陷含因與避:
## Common Pitfalls
- **Pitfall name**: What goes wrong and how to avoid it. Be specific about the symptom and the fix.
取自實歷。佳陷為費大時且不明者。
得: 3-6 陷、各含粗名、何誤述、如何避。
敗: 陷感泛(「於 X 慎」)→具:名症、因、修。取自發試中實敗。
交引 2-5 常於此前、後、或同用之技:
## Related Skills
- `prerequisite-skill` - must be done before this skill
- `follow-up-skill` - commonly done after this skill
- `alternative-skill` - alternative approach to the same goal
用技 name 欄(kebab-case)、非標。
得: 2-5 相關技以 kebab-case ID 列、各含關係短述(前、後、代)。
敗: 驗各引技存:ls skills/<skill-name>/SKILL.md。除改名或去之引。
編 skills/_registry.yml 於合域下加新技:
- id: skill-name-here
path: skill-name-here/SKILL.md
complexity: intermediate
language: multi
description: One-line description matching the frontmatter
更庫首 total_skills 計。
得: 新項現於 skills/_registry.yml 合域下、total_skills 計合碟上技目實數。
敗: 以 find skills -name SKILL.md | wc -l 計技、較 total_skills。驗 id 欄全合目名。
技基於立法、研論、軟包、標準→於 references/ 加引子檔:
mkdir -p skills/<skill-name>/references/
建二檔:
references/CITATIONS.bib — 機可讀 BibTeX(真源)references/CITATIONS.md — 人讀式引為 GitHub 覽% references/CITATIONS.bib
@article{author2024title,
author = {Author, First and Other, Second},
title = {Paper Title},
journal = {Journal Name},
year = {2024},
doi = {10.xxxx/xxxxx}
}
<!-- references/CITATIONS.md -->
# Citations
References underpinning the **skill-name** skill.
1. Author, F., & Other, S. (2024). *Paper Title*. Journal Name. https://doi.org/10.xxxx/xxxxx
引為可——源追要時加(學法、刊標、規架)。
譯中理 references/:references/EXAMPLES.md 中文述當譯。references/CITATIONS.bib 留英(BibTeX 語中性)。譯可連英 references/ 目若其僅碼。
得: 二檔存且 .bib 解為有效 BibTeX。
敗: 以 bibtool -d references/CITATIONS.bib 或線驗器驗 BibTeX 文。
承前行地驗:
# Check line count (must be ≤500)
lines=$(wc -l < skills/<skill-name>/SKILL.md)
[ "$lines" -le 500 ] && echo "OK ($lines lines)" || echo "FAIL: $lines lines > 500"
# Check required frontmatter fields
head -20 skills/<skill-name>/SKILL.md | grep -q '^name:' && echo "name: OK"
head -20 skills/<skill-name>/SKILL.md | grep -q '^description:' && echo "description: OK"
得: 行數 ≤500、諸必欄存。
敗: 過 500 行→施漸揭——取大碼塊(>15 行)至 references/EXAMPLES.md:
mkdir -p skills/<skill-name>/references/
移擴碼例、全設檔、多變例至 references/EXAMPLES.md。於 SKILL.md 加交引:See [EXAMPLES.md](references/EXAMPLES.md) for complete configuration examples. 保短內(3-10 行)於主 SKILL.md。.github/workflows/validate-skills.yml 於諸 PR 強此限。
建軟連使 Claude Code 以 /slash-command 發現技:
# Project-level (available in this project)
ln -s ../../skills/<skill-name> .claude/skills/<skill-name>
# Global (available in all projects)
ln -s /mnt/d/dev/p/agent-almanac/skills/<skill-name> ~/.claude/skills/<skill-name>
得: ls -la .claude/skills/<skill-name>/SKILL.md 解至技檔。
敗: 驗相路正。自 .claude/skills/ 路 ../../skills/<skill-name> 當達技目。以 readlink -f 除軟連解。Claude Code 期平構於 .claude/skills/<name>/SKILL.md。
諸技必。此步施於人作者與循此程之 AI 代。勿略——缺譯積為陳備。
承新技後即為諸 4 locales 架譯檔:
for locale in de zh-CN ja es; do
npm run translate:scaffold -- skills <skill-name> "$locale"
done
續譯各檔之架詞(碼塊與 ID 留英)。終重生態檔:
npm run translation:status
得: i18n/{de,zh-CN,ja,es}/skills/<skill-name>/SKILL.md 建四檔、source_commit 皆合現 HEAD。npm run validate:translations 顯零陳警於新技。
敗: 架敗→架前驗技存於 skills/_registry.yml——本讀庫。translation:status 顯新檔陳→察 source_commit 合英源末改之承雜。
skills/<skill-name>/SKILL.mdname 欄合目名description 於 1024 字符內_registry.yml 含正路total_skills 計已更references/EXAMPLES.md)references/CITATIONS.bib + CITATIONS.md.claude/skills/<skill-name> 指技目~/.claude/skills/<skill-name>(若全可)references/EXAMPLES.md)git mv:/mnt/ 路之目 git mv 或建破權(d?????????)。用 mkdir -p + 複檔 + git rm 舊路良構技循此質清:
此庫之寸考:
references/EXAMPLES.mdevolve-skill - 演精以此法造之技create-agent - 造代定之並法create-team - 造團組之並法write-claude-md - CLAUDE.md 可引案專流之技configure-git-repository - 技當版控commit-changes - 承新技與其軟連security-audit-codebase - 評技為誤含之密或證