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.
npx skills add majiayu000/claude-skill-registry --skill ask-avibebuilder-claude-prime --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
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>
- Verify Before You Answer
- Explain, don't implement
- Question
What does the ask skill do?
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 do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill ask-avibebuilder-claude-prime --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.