Agent skill · AI & Agents

investigate

Use when user asks 'what is X', 'how does X work', 'find out about', 'analyze', 'explain the code', or needs quick codebase investigation. Returns findings directly in conversation without saving files. Prefer this over Explore agent.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill investigate-tokenrollai-cc-plugin-2 --agent claude-code

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

Facts
Files in the skill folder: 2
SKILL.md size: 2 KB
Bundled scripts: none
Allowed tools: ReadGlobGrepBashWebSearchWebFetch
Path: skills/analysis/investigate-tokenrollai-cc-plugin-2/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

# /investigate This skill performs rapid, documentation-driven codebase investigation and reports findings directly. ## Pre-fetched Context - **Llmdoc exists:** !`test -d llmdoc && echo "llmdoc initialized" || echo "No llmdoc directory"` - **Llmdoc index:** !`cat llmdoc/index.md 2>/dev/null | head -100 || echo "No index"` - **Doc structure:** !`find llmdoc -name "*.md" 2>/dev/null | head -50` - **Project structure:** !`ls -la 2>/dev/null | head -20` ## Investigation Protocol ### Phase 1: Documentation First Before touching any source code, you MUST: 1. Check if `llmdoc/` exists (see pre-fetched context above). 2. If exists, read relevant documents in this order: - `llmdoc/index.md` - navigation and overview - `llmdoc/overview/*.md` - project context - `llmdoc/architecture/*.md` - system design - `llmdoc/guides/*.md` - workflows - `llmdoc/reference/*.md` - conventions ### Phase 2: Code Investigation Only after exhausting documentation, investigate source code: 1. Use `Glob` to find relevant files. 2. Use `Grep` to search for patterns. 3. Use `Read` to examine specific files. ### Phase 3: Report Output a concise report with this structure: ```markdown #### Code Sections - `path/to/fi

What's inside
Steps it walks through
  1. Pre-fetched Context
  2. Investigation Protocol
  3. Phase 1: Documentation First
  4. Phase 2: Code Investigation
  5. Phase 3: Report
  6. Key Practices
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the investigate skill do?

Use when user asks 'what is X', 'how does X work', 'find out about', 'analyze', 'explain the code', or needs quick codebase investigation. Returns findings directly in conversation without saving files. Prefer this over Explore agent.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill investigate-tokenrollai-cc-plugin-2 --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