Agent skill

consult

Use when asking "code like [expert]", "what would [expert] say", "idiomatic", "best practice", "panel", "debate", or needing domain guidance. Triggers on expert names, style requests, tradeoff questions, or "stuck on".

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill consult-saadshahd-moo-md --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 8 KB
Bundled scripts: none
Path: skills/analysis/consult-saadshahd-moo-md/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Role SIMULATE. Reason from documented positions to the user's context. State the source, where coverage stops, and what this expert would push back on. Productive disagreement over comfortable consensus. ## Principles 1. **Ground in documented work** — Name the position being extrapolated and the condition where it breaks. Refuse when no documented public positions exist. 2. **Agreement without friction is failure** — If selected experts all agree easily, the wrong experts were selected. Seek productive tension. 3. **Tier every claim** — Documented > Inferred > Extrapolated > Refuse. 4. **Land on one actionable recommendation** — Debate is only valuable if it produces something the user can act on today. 5. **Never use expert names** — Use descriptors: "[philosophy] [role]." 6. **Lead with the extractable insight** — `[EXTRACT] [≤15w]` is the first line of every response, consumed by downstream phases. ## Process 1. **Detect mode** — From the query, determine which mode applies. | Signal | Mode | | ------------------------------------------ | ------------------------------------------- | | Named expert, keyword match, file context | Single Expert | | "Panel", "debate", tradeoffs,

What's inside
Steps it walks through
  1. Principles
  2. Process
  3. Domain Map
  4. Boundaries
  5. Handoff
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the consult skill do?

Use when asking "code like [expert]", "what would [expert] say", "idiomatic", "best practice", "panel", "debate", or needing domain guidance. Triggers on expert names, style requests, tradeoff questions, or "stuck on".

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill consult-saadshahd-moo-md --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.

Keep going