$ loading_
帮助用户快速掌握 Skills 的基本用法、检索方式与头脑风暴触发场景。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "Getting Started with Skills" 技能： 1. 下载 https://raw.githubusercontent.com/obra/clank/main/skills/getting-started/SKILL.md 2. 保存为 ~/.claude/skills/getting-started/SKILL.md 3. 装好后重载技能，告诉我可以用了
请用中文介绍 Skills 的必备使用流程，包括什么时候先检索、什么时候直接提问，以及如何组织一个清晰的任务请求。
一份清晰的新手入门说明，概括 Skills 的核心使用步骤与注意事项。
请告诉我在 Skills 中如何高效检索合适的能力或工具，并给我几个适合新手照抄的搜索示例。
一组检索技巧与示例查询，帮助用户更快找到合适的技能。
我刚开始使用 Skills，请给我一些适合头脑风暴的提问模板，帮助我发现这个系统还能在哪些任务上派上用场。
若干可直接使用的头脑风暴提示模板，以及对应的适用场景说明。
Your personal wiki of proven techniques, patterns, and tools at ~/.claude/skills/.
DO NOT use @ links - they force-load entire files, burning 200k+ context instantly.
INSTEAD, use skill path references:
skills/category/skill-name (no @ prefix, no /SKILL.md suffix)skills/collaboration/brainstorming or skills/testing/test-driven-developmentWhen you see skill references in documentation:
skills/path/name → Use Read tool on ~/.claude/skills/path/name/SKILL.md1. Search skills:
~/.claude/skills/getting-started/skills-search PATTERN
2. Search conversations: Dispatch subagent (see Workflow 2) to check for relevant past work.
If skills found:
~/.claude/skills/path/skill-name/SKILL.md"This doesn't count as a task" is rationalization. Skills/conversations exist and you didn't search for them or didn't use them = failed task.
When: Your human partner mentions past work, issue feels familiar, starting task in familiar domain, stuck/blocked, before reinventing
When NOT: Info in current convo, codebase state questions, first encounter, partner wants fresh thinking
How (use subagent for 50-100x context savings):
~/.claude/skills/collaboration/remembering-conversations/tool/prompts/search-agent.mdExample:
Partner: "How did we handle auth errors in React Router?"
You: Searching past conversations...
[Dispatch subagent → 350-word synthesis]
[Apply without loading 50k tokens]
Red flags: Reading .jsonl files directly, pasting excerpts, asking "which conversation?", browsing archives
Pattern: Search → Subagent synthesizes → Apply. Fast, focused, context-efficient.
Every time you start using a skill, announce it:
"I'm using the [Skill Name] skill to [what you're doing]."
Examples:
Why: Transparency helps your human partner understand your process and catch errors early.
If a skill contains a checklist, you MUST create TodoWrite todos for EACH checklist item.
Don't:
Why: Checklists without TodoWrite tracking = steps get skipped. Every time.
Examples: TDD (write test, watch fail, implement, verify), Systematic Debugging (4 phases), Creating Skills (RED-GREEN-REFACTOR)
Really, try skills-search first.
Categories: skills/INDEX.md → testing, debugging, coding, architecture, collaboration, meta Individual skill: Load from category INDEX
when_to_use match your situation?Many skills contain rigid rules (TDD, debugging, verification). Follow them exactly. Don't adapt away the discipline.
Some skills are flexible patterns (architecture, naming). Adapt core principles to your context.
The skill itself tells you which type it is.
…
帮助你为变量选择清晰准确、易维护的命名，提升代码可读性。
将当前对话中的可复用流程整理并保存为可反复调用的技能文件