mcpbeat

Ask

avibebuilder/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.

398 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
111
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/avibebuilder/claude-prime --skill ask

The instruction itself

3 sections, as written by the author

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>

How to use it

Copy the folder

Take avibebuilder/ask from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.