Agent skill

a

Trigger: /a. Never auto-trigger on think, scan, consider, or examine.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill a --agent claude-code

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

Facts
Files in the skill folder: 2
SKILL.md size: 3 KB
Bundled scripts: none
Path: skills/analysis/a/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

# /analyze - Explore → Interrogate → Bridge Structured Q&A that converges on decisions. Questions evolve based on answers. ## Arguments - `/analyze` — asks "What needs solving?" - `/analyze <topic>` — skips opening question - `/analyze resume` — finds last decision tracker in conversation, continues ## Flow ### 1. EXPLORE 1. Read relevant codebase files (5-10). For greenfield projects, ask about constraints instead. 2. Identify decision points. Form an opinion on each from codebase evidence. 3. Output: `"~N decisions to work through (some will be auto-decided)"` ### 2. INTERROGATE One question at a time via `AskUserQuestion`. **Auto-decide** when codebase evidence makes one option overwhelmingly correct. Present initial auto-decisions as a batch before the first human question: ``` ### Auto-decided (review before we continue) 1. ✅ (auto) [topic]: [answer] — [rationale] ``` Ask: "Want to revisit any of these, or move on?" If flagged, convert to regular question. **Questions:** - Order options by recommendation strength (best first) - All option slots are for real answers — user can type "go back" or "park" via Other **After each answer:** - Reassess: does this reveal new decisions (

What's inside
Steps it walks through
  1. Arguments
  2. Flow
  3. 1. EXPLORE
  4. 2. INTERROGATE
  5. 3. BRIDGE
  6. Rules
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
descriptive-statisticsSummarizing and visualizing data through measures of center, spread, shape, and position. Covers…Data & Analyticsperplexity-researcher-reasoning-proHighest level of research and reasoning capabilities for complex decision-making with significant…OtherretroBrutally honest engineering retrospective. Analyzes git history for what actually happened — not…Data & AnalyticsanalyzeUniversal multi-perspective analyzer for any topic, file, idea, or decision. Extract key points…Otherarize-prompt-optimizationINVOKE THIS SKILL when optimizing, improving, or debugging LLM prompts using production trace data…Data & Analyticscellxgene-contextGuide for integrating CellxGene Census single-cell data with ENCODE bulk experiments. Use when…Data & Analytics
About this skill
What does the a skill do?

Trigger: /a. Never auto-trigger on think, scan, consider, or examine.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill a --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
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.