$ loading_
Learn core Skills workflows, search patterns, and brainstorming use cases quickly.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "Getting Started with Skills" skill from askskill: 1. Download https://raw.githubusercontent.com/obra/clank/main/skills/getting-started/SKILL.md 2. Save it as ~/.claude/skills/getting-started/SKILL.md 3. Reload skills and tell me it's ready
Explain the essential Skills workflow in English, including when to search first, when to ask directly, and how to structure a clear task request.
A clear beginner guide summarizing the core steps and best practices for using Skills.
Show me how to efficiently search for the right capability or tool in Skills, and give me a few beginner-friendly search examples I can reuse.
A set of search tips and example queries to help users find the right skills faster.
I’m new to Skills. Give me some brainstorming prompt templates to help me discover what kinds of tasks this system can assist with.
Several ready-to-use brainstorming prompt templates with notes on when to use each one.
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.
…
Write evergreen comments focused on what and why, not historical context.
Compare 2-3 approaches before execution to choose a stronger solution.
Plan with pseudocode first, refine approaches, then translate into working code.
Search past Claude Code chats to recover facts, decisions, and context.
Design systems by hiding implementation details behind domain-level interfaces.
Name code by domain meaning to improve clarity and team alignment.
Find reusable skills across local and online sources before creating one.
Explains how to use abilities effectively before starting any conversation.
Turn a repeated workflow into a reusable skill file from the current session.
Create or update skills that extend Codex with knowledge, workflows, and tools.
Create reusable SKILL.md skills that package repeatable workflows for future use.
Create, refine, and troubleshoot AI skills, specs, invocation, and compatibility.