62 lines
2.2 KiB
Markdown
62 lines
2.2 KiB
Markdown
---
|
|
name: ck-help
|
|
description: ClaudeKit skills and commands cheatsheet. Use when asking about available skills, how to use a command, finding the right tool for a task, or getting workflow guidance for fix, plan, test, review, or deploy.
|
|
---
|
|
|
|
# CK Help — Skills Cheatsheet
|
|
|
|
All-in-one guide for discovering and using ClaudeKit skills and commands.
|
|
|
|
## When to Use
|
|
|
|
- "What skills are available?"
|
|
- "How do I use the plan command?"
|
|
- "Find me a skill for X"
|
|
- "What's the workflow for fixing bugs / deploying / testing?"
|
|
|
|
## Don't Use When
|
|
|
|
- Task is clear and a specific skill is already known — activate that skill directly
|
|
|
|
## Execution
|
|
|
|
Run the help script with the user's query (translate to English first if needed):
|
|
|
|
```bash
|
|
python $HOME/.claude/scripts/ck-help.py "$QUERY"
|
|
```
|
|
|
|
Always translate non-English queries to English before passing to the script — it uses English keyword matching.
|
|
|
|
## Output Types
|
|
|
|
The script outputs a type marker on the first line: `@CK_OUTPUT_TYPE:<type>`
|
|
|
|
| Type | Presentation |
|
|
|------|-------------|
|
|
| `comprehensive-docs` | Show full output verbatim, then add real-world tips and a follow-up question |
|
|
| `category-guide` | Show complete workflow + command list, add practical context |
|
|
| `command-details` | Show full command info, add concrete usage example and alternatives |
|
|
| `search-results` | Show all matches, group by relevance, suggest most likely match |
|
|
| `task-recommendations` | Show recommended commands, explain reasoning and suggested order |
|
|
|
|
## Key Principle
|
|
|
|
Script output = foundation. Always show it fully, then add value with context, examples, and tips. Never summarize or replace script output.
|
|
|
|
## Important Workflow Notes
|
|
|
|
- `/plan` → `/cook`: plan first, then execute
|
|
- `/cook`: standalone — plans internally, no separate `/plan` needed
|
|
- Never suggest `/plan` → `/cook` (cook has its own planning)
|
|
|
|
## Intent Heuristics
|
|
|
|
| Sentence Pattern | Primary Intent |
|
|
|-----------------|----------------|
|
|
| `[action verb] my [object]` | The action verb |
|
|
| `[context] [subject noun]` | The subject noun |
|
|
| `[noun] [noun]` | Last noun (topic) |
|
|
|
|
Action verbs (high intent): fix, test, commit, push, build, create, review, deploy, run, check, find, plan, refactor
|