ask
Query the bundled research knowledge graph for methodology guidance. Routes questions through a 3-tier knowledge base — WHY (research claims), HOW (guidance docs), WHAT IT LOOKS LIKE (domain examples) — plus structured reference documents. Returns research-backed answers grounded in specific claims with practical application to the user's system. Triggers on "/ask", "/ask [question]", "why does my system...", "how should I...".
npx skills add majiayu000/claude-skill-registry --skill ask-lopewale-dev-ignition --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.
What it does
Query the bundled research knowledge graph for methodology guidance. Routes questions through a 3-tier knowledge base — WHY (research claims), HOW (guidance docs), WHAT IT LOOKS LIKE (domain examples) — plus structured reference documents. Returns research-backed answers grounded in specific claims with practical application to the user's system. Triggers on "/ask", "/ask [question]", "why does my system...", "how should I...".
How it works
- Classify the question to decide which tier(s) to consult.
- Search the knowledge base routing to the appropriate tiers.
- Read the 3–7 most relevant sources fully (use
mcp__qmd__multi_getwhen reading multiple IDs). - Check user context by reading
ops/derivation.mdif the question involves their system. - Synthesize an answer by weaving claims into a coherent, opinionated argument.
- Cite sources by referencing specific claims and documents so the user can explore further.
When to use it
Triggered by prompts that map to WHY, HOW, or WHAT questions as indicated in the classification rules and the triggering phrases listed in the description.
What it can touch
Tools allowed: Read, Grep, Glob, mcp__qmd__search, mcp__qmd__vector_search, mcp__qmd__deep_search, mcp__qmd__get, mcp__qmd__multi_get. Read/grep across ${CLAUDE_PLUGIN_ROOT}/methodology/ and ${CLAUDE_PLUGIN_ROOT}/reference/ to load sources; use mcp__qmd__multi_get for loading multiple IDs.
Caveats
Claims are drawn from the three-tier knowledge base (WHY, HOW, WHAT) and reference documents. If user context requires, check ops/derivation.md and relevant reference mappings; acknowledge gaps if the knowledge graph lacks coverage for a topic. The workflow emphasizes deep reading of 3–7 sources rather than shallow breadth.
## EXECUTE NOW **Question: $ARGUMENTS** If no question provided, ask the user what they want to know. **Execute these steps:** 1. **Classify the question** — determine which knowledge base tier(s) to consult (see Query Classification below) 2. **Search the knowledge base** — route to appropriate tiers based on classification 3. **Read relevant claims and docs** — load 3-7 most relevant sources fully (use `mcp__qmd__multi_get` when reading multiple IDs) 4. **Check user context** — read `ops/derivation.md` if the question involves their specific system 5. **Synthesize an answer** — weave claims into a coherent, opinionated argument 6. **Cite sources** — reference specific claims and documents so the user can explore further **START NOW.** Reference below explains routing and synthesis methodology. --- ## The Three-Tier Knowledge Base The plugin's knowledge base has three distinct parts, each serving a different function. Effective answers often draw from multiple tiers. ### Tier 1: Research Graph (WHY) **Location:** `${CLAUDE_PLUGIN_ROOT}/methodology/` — filter by `kind: research` **Content:** 213 interconnected research claims grounded in cognitive science, knowledge system theory,
- EXECUTE NOW
- The Three-Tier Knowledge Base
- Tier 1: Research Graph (WHY)
- Tier 2: Guidance Docs (HOW)
- Tier 3: Domain Examples (WHAT IT LOOKS LIKE)
- Reference Documents (structured derivation context)
- Query Classification
- Classification Rules
- Multi-Tier Questions
- Search Strategy
- Step 1: Route to Claim-Map
- Step 2: Search the Appropriate Tier
- Step 3: Read Deeply
- Step 4: Check User Context
Load all methodology notes for f in ops/methodology/*.md; do echo "=== $f ===" cat "$f" echo "" done
What does the ask skill do?
Query the bundled research knowledge graph for methodology guidance. Routes questions through a 3-tier knowledge base — WHY (research claims), HOW (guidance docs), WHAT IT LOOKS LIKE (domain examples) — plus structured reference documents. Returns research-backed answers grounded in specific claims with practical application to the user's system. Triggers on "/ask", "/ask [question]", "why does my system...", "how should I...".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill ask-lopewale-dev-ignition --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.