Skip to content
Back to skills

Investigate Tokenrollai Cc Plugin 2

ASecurity

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.

  • 666 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 2, 2026
ai-agentsbashapidocumentation

Works with

  • api

Security analysis

A100/100

Scanned September 2, 2026

npx -y skills add majiayu000/claude-skill-registry --skill investigate-tokenrollai-cc-plugin-2 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Investigate Tokenrollai Cc Plugin 2?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Investigate Tokenrollai Cc Plugin 2
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-investigate-tokenrollai-cc-plugin-2/badge)](https://www.skillsdirectory.com/skills/majiayu000-investigate-tokenrollai-cc-plugin-2)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: investigate
description: "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."
disable-model-invocation: false
context: fork
allowed-tools: Read, Glob, Grep, Bash, WebSearch, WebFetch
---

# /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/file.ext:line~line` (SymbolName): Brief description

#### Report

**Conclusions:**
> Key findings...

**Relations:**
> File/module relationships...

**Result:**
> Direct answer to the question...
```

## Key Practices

- **Stateless**: Output directly, do not write files.
- **Concise**: Report under 150 lines.
- **No Code Blocks**: Reference code with `path/file.ext` format, not paste.
- **Objective**: State facts only, no subjective judgments.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.