ask
/ask
Answer questions about code, architecture, and technical decisions — no implementation. Trigger on questions asking 'why', 'what does this do', 'what is the purpose of', 'explain', 'what's the difference', 'compare', or 'what are the tradeoffs' — even when referencing specific files, code snippets, or inline code. The key signal is the user wants to UNDERSTAND something, not change it. Do NOT trigger for requests to build, fix, plan, review, research, or add/modify code.
- Author
- avibebuilder ↗
- Repository
- claude-prime ↗
- Licence
- MIT
- Last repository change
- 17.05.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 17.05.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Answer questions about code, architecture, and technical decisions — no implementation. Trigger on questions asking 'why', 'what does this do', 'what is the purpose of', 'explain', 'what's the difference', 'compare', or 'what are the tradeoffs' — even when referencing specific files, code snippets, or inline code. The key signal is the user wants to UNDERSTAND something, not change it. Do NOT trigger for requests to build, fix, plan, review, research, or add/modify code.
Triggers from the description
Arguments
/ask question
Original author description
Answer questions about code, architecture, and technical decisions — no implementation. Trigger on questions asking 'why', 'what does this do', 'what is the purpose of', 'explain', 'what's the difference', 'compare', or 'what are the tradeoffs' — even when referencing specific files, code snippets, or inline code. The key signal is the user wants to UNDERSTAND something, not change it. Do NOT trigger for requests to build, fix, plan, review, research, or add/modify code.
How it works
- Verify Before You Answer
- Explain, don't implement
- Question
SKILL.md preview
--- name: ask description: "Answer questions about code, architecture, and technical decisions — no implementation. Trigger on questions asking 'why', 'what does this do', 'what is the purpose of', 'explain', 'what's the difference', 'compare', or 'what are the tradeoffs' — even when referencing specific files, code snippets, or inline code. The key signal is the user wants to UNDERSTAND something, not change it. Do NOT trigger for requests to build, fix, plan, review, research, or add/modify code." argument-hint: question --- Think before answering: do you have verified evidence, or are you about to rely on assumption? ## Verify Before You Answer Your trained knowledge is stale and your memory of this codebase may be wrong. Verify from source before claiming anything: - **Question about specific code?** → Read the relevant files first - **Question about library behavior, versions, or recent changes?** → Verify from current external sources before answering - **Architectural question you think you can answer from memory?** → Still check the actual codebase — confirm before claiming ## Explain, don't implement This skill ends at the explanation — the user decides what to do next. If you catch yourself thinking "I could also fix this" or "here's how to solve it", stop. Explain only. This is not a coding session. No code blocks — not even to illustrate format or behavior. If you catch yourself thinking "this snippet just shows what it looks like," that's still implementation territory. Explain in prose. ## Question <question>$ARGUMENTS</question>
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · avibebuilder/claude-prime | 90 | MIT |
| eliyce/paqad-ai | 100 | MIT |
| pleaseai/claude-code-plugins | 100 | MIT |
| vegardjorg/ravenseat | 100 | MIT |
| r3dlex/oh-my-auggie | 100 | Apache-2.0 |
| seemseam/claude_codex_bridge | 100 | AGPL-3.0 |
| keli-wen/agy-staff | 100 | MIT |
| inbarajaldrin/devdroid | 100 | Apache-2.0 |
| jayjiangct/knowlery | 100 | MIT |
Database snapshot: 13.11.2026 · package version 689cd3473fad (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90understand-chat
Use when you need to ask questions about a codebase or understand code using a knowledge graph - 100understand-chat
Use when you need to ask questions about a codebase or understand code using a knowledge graph - 100review-code
Review code for quality, correctness, and fit. Use when the user wants judgment on code that already exists — their own changes, a teammate's patch, a PR, branch, commit, diff, staged changes, or one or more files to look over. Activate on requests like review, look over, sanity… - 100note-it
Capture implementation notes after code implementation and review/fix. Records design decisions, deviations, tradeoffs, and open questions to docs/issue#XXXX.html. Triggers on: /note-it, 记录笔记, implementation notes. - 90ctx-explain
Explain code for someone new to the project. Use when the user asks 'what does this do', 'explain this', or wants to understand unfamiliar code. - 90explore
Read-only file search and codebase exploration specialist. Use when you need to find files by pattern, search code with regex, navigate unfamiliar codebases, or understand code architecture without making changes.