Orca CLI
stablyai/orca
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…
A skill your agent uses when integrating detective skills across plugins.
$ npx skills add MadAppGang/claude-code --skill cross-plugin-detective -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MadAppGang/claude-code cross-plugin-detective --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/MadAppGang/claude-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/code-analysis/skills/cross-plugin-detective .claude/skills/cross-plugin-detective && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cross-plugin-detective" agent skill from https://github.com/MadAppGang/claude-code/tree/main/plugins/code-analysis/skills/cross-plugin-detective into .claude/skills/cross-plugin-detective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-plugin-detective", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/MadAppGang/claude-code/tree/main/plugins/code-analysis/skills/cross-plugin-detectiveType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add MadAppGang/claude-code --skill cross-plugin-detective -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MadAppGang/claude-code cross-plugin-detective --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MadAppGang/claude-code.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/code-analysis/skills/cross-plugin-detective .agents/skills/cross-plugin-detective && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cross-plugin-detective" agent skill from https://github.com/MadAppGang/claude-code/tree/main/plugins/code-analysis/skills/cross-plugin-detective into .agents/skills/cross-plugin-detective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-plugin-detective", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MadAppGang/claude-code --skill cross-plugin-detective -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MadAppGang/claude-code cross-plugin-detective --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MadAppGang/claude-code.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/code-analysis/skills/cross-plugin-detective .cursor/skills/cross-plugin-detective && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cross-plugin-detective" agent skill from https://github.com/MadAppGang/claude-code/tree/main/plugins/code-analysis/skills/cross-plugin-detective into .cursor/skills/cross-plugin-detective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-plugin-detective", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/MadAppGang/claude-code.git --path plugins/code-analysis/skills/cross-plugin-detective--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add MadAppGang/claude-code --skill cross-plugin-detective -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MadAppGang/claude-code cross-plugin-detective --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MadAppGang/claude-code.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/code-analysis/skills/cross-plugin-detective .gemini/skills/cross-plugin-detective && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cross-plugin-detective" agent skill from https://github.com/MadAppGang/claude-code/tree/main/plugins/code-analysis/skills/cross-plugin-detective into .gemini/skills/cross-plugin-detective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-plugin-detective", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install MadAppGang/claude-code cross-plugin-detectiveInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add MadAppGang/claude-code --skill cross-plugin-detective -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/MadAppGang/claude-code.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/code-analysis/skills/cross-plugin-detective .github/skills/cross-plugin-detective && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cross-plugin-detective" agent skill from https://github.com/MadAppGang/claude-code/tree/main/plugins/code-analysis/skills/cross-plugin-detective into .github/skills/cross-plugin-detective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-plugin-detective", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add MadAppGang/claude-code --skill cross-plugin-detective -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install MadAppGang/claude-code cross-plugin-detective --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MadAppGang/claude-code.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/code-analysis/skills/cross-plugin-detective .opencode/skills/cross-plugin-detective && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cross-plugin-detective" agent skill from https://github.com/MadAppGang/claude-code/tree/main/plugins/code-analysis/skills/cross-plugin-detective into .opencode/skills/cross-plugin-detective/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cross-plugin-detective", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
cross-plugin-detectiveA skill your agent uses when integrating detective skills across plugins.
Cross Plugin Detective is an agent skill from MadAppGang/claude-code. Use when integrating detective skills across plugins. Maps agent roles to appropriate detective skills (developer → developer-detective, architect → architect-detective). Reference this to connect agents with claudemem investigation capabilities.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Multi-agent orchestration. The repository describes itself as: claude code plugins marketplace. The licence is MIT.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 6097ad4. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
BashTaskReadAskUserQuestionFrom allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml, typescript and json).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Cross Plugin Detective loads about 2.4k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 273 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
allowed-tools: Bash, Task, Read, AskUserQuestionAutomated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from MadAppGang/claude-code at commit 6097ad4, republished under its MIT licence (© MadAppGang). 273 words, ~2,392 tokens.
.claude/skills/cross-plugin-detective/SKILL.md (or your agent's skills folder).Version: 1.0.0 Purpose: Connect ANY agent to the appropriate detective skill based on role
╔══════════════════════════════════════════════════════════════════════════════╗
║ ║
║ ALL DETECTIVE SKILLS USE claudemem (INDEXED MEMORY) EXCLUSIVELY ║
║ ║
║ When ANY agent references a detective skill, they MUST: ║
║ ❌ NEVER use grep, find, rg, Glob tool, Grep tool ║
║ ✅ ALWAYS use claudemem search "query" ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝| Agent | Should Use Skill | Purpose |
|---|---|---|
typescript-frontend-dev | code-analysis:developer-detective | Find implementations, trace data flow |
frontend-architect | code-analysis:architect-detective | Analyze architecture, design patterns |
test-architect | code-analysis:tester-detective | Coverage analysis, test quality |
senior-code-reviewer | code-analysis:ultrathink-detective | Comprehensive code review |
ui-developer | code-analysis:developer-detective | Find UI implementations |
designer | code-analysis:architect-detective | Understand component structure |
plan-reviewer | code-analysis:architect-detective | Review architecture plans |
| Agent | Should Use Skill | Purpose |
|---|---|---|
backend-developer | code-analysis:developer-detective | Find implementations, trace data flow |
api-architect | code-analysis:architect-detective | API architecture analysis |
apidog | code-analysis:developer-detective | Find API implementations |
| Agent | Should Use Skill | Purpose |
|---|---|---|
codebase-detective | All detective skills | Full investigation capability |
| Agent Role | Should Use Skill |
|---|---|
| Any "developer" agent | code-analysis:developer-detective |
| Any "architect" agent | code-analysis:architect-detective |
| Any "tester" agent | code-analysis:tester-detective |
| Any "reviewer" agent | code-analysis:ultrathink-detective |
| Any "debugger" agent | code-analysis:debugger-detective |
---
name: my-developer-agent
description: Implements features
skills: code-analysis:developer-detective
---
# My Developer Agent
When investigating code, use the developer-detective skill.
This gives you access to indexed memory search via claudemem.
## Investigation Pattern
Before implementing:
1. Check claudemem status: `claudemem status`
2. Search for related code: `claudemem search "feature I'm implementing"`
3. Read specific files from results
4. NEVER use grep or find for discovery---
name: my-architect-agent
description: Designs architecture
skills: code-analysis:architect-detective
---
# My Architect Agent
When analyzing architecture, use the architect-detective skill.
## Architecture Discovery
1. Check claudemem status: `claudemem status`
2. Search for patterns: `claudemem search "service layer architecture"`
3. Map dependencies: `claudemem search "import dependency injection"`
4. NEVER use grep or find for discovery---
name: comprehensive-reviewer
description: Reviews all aspects
skills: code-analysis:ultrathink-detective, code-analysis:tester-detective
---┌─────────────────────────────────────────────────────────────────────────────┐
│ WHICH DETECTIVE SKILL TO USE? │
├─────────────────────────────────────────────────────────────────────────────┤
│ │
│ What is the agent's PRIMARY focus? │
│ │
│ ├── IMPLEMENTING code / Finding where to change │
│ │ └── Use: developer-detective │
│ │ │
│ ├── DESIGNING architecture / Understanding patterns │
│ │ └── Use: architect-detective │
│ │ │
│ ├── TESTING / Coverage analysis / Quality │
│ │ └── Use: tester-detective │
│ │ │
│ ├── DEBUGGING / Finding root cause │
│ │ └── Use: debugger-detective │
│ │ │
│ └── COMPREHENSIVE analysis / Technical debt / Audit │
│ └── Use: ultrathink-detective │
│ │
└─────────────────────────────────────────────────────────────────────────────┘// In frontend plugin's typescript-frontend-dev agent:
// ❌ WRONG - Never do this
Grep({ pattern: "UserService", type: "ts" });
Glob({ pattern: "**/user*.ts" });
// ✅ CORRECT - Use indexed memory via developer-detective skill
// The skill teaches the agent to use:
claudemem search "UserService implementation methods"// In bun plugin's api-architect agent:
// ❌ WRONG - Never do this
find . -name "*.controller.ts"
grep -r "router\." . --include="*.ts"
// ✅ CORRECT - Use indexed memory via architect-detective skill
claudemem search "API controller endpoint handler"
claudemem search "router pattern REST GraphQL"// In frontend plugin's test-architect agent:
// ❌ WRONG - Never do this
Glob({ pattern: "**/*.test.ts" });
Grep({ pattern: "describe" });
// ✅ CORRECT - Use indexed memory via tester-detective skill
claudemem search "test coverage describe spec"
claudemem search "mock stub test assertion"When an agent needs code investigation, it should:
---
name: any-agent-that-needs-investigation
skills: code-analysis:developer-detective # or architect/tester/debugger/ultrathink
---
# This agent inherits:
# - INDEXED MEMORY requirement (claudemem only)
# - Role-specific search patterns
# - Output format guidance
# - FORBIDDEN: grep, find, Glob, Grep toolsIf your plugin has agents that need code investigation, add this dependency:
{
"name": "your-plugin",
"dependencies": {
"code-analysis@mag-claude-plugins": "^1.6.0"
}
}This ensures:
code-analysis:* prefix╔══════════════════════════════════════════════════════════════════════════════╗
║ ║
║ ANY AGENT + CODE INVESTIGATION = claudemem ONLY ║
║ ║
║ Developer agents → code-analysis:developer-detective ║
║ Architect agents → code-analysis:architect-detective ║
║ Tester agents → code-analysis:tester-detective ║
║ Debugger agents → code-analysis:debugger-detective ║
║ Reviewer agents → code-analysis:ultrathink-detective ║
║ ║
║ grep/find/Glob/Grep = FORBIDDEN (always, everywhere, no exceptions) ║
║ ║
╚══════════════════════════════════════════════════════════════════════════════╝Maintained by: MadAppGang Plugin: code-analysis Last Updated: December 2025
© MadAppGang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/code-analysis/skills/cross-plugin-detective of MadAppGang/claude-code.
Open the folder on GitHubat commit 6097ad4
Cross Plugin Detective next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cross Plugin Detective this skillMadAppGang/claude-code | 285 | — | ~2.4k | Automated safety check: Notes | MIT | |
| Orca CLIstablyai/orca | 89k | 2 repos | ~593 | Automated safety check: Pass | MIT | |
| Paseo Advisor Second Opiniongetpaseo/paseo | 20k | 1 repos | ~756 | Automated safety check: Pass | Custom licence | |
| O2 Review Loopopenobserve/openobserve | 22k | — | ~3.7k | Automated safety check: Pass | AGPL-3.0 | |
| Paseo Committeegetpaseo/paseo | 20k | 1 repos | ~496 | Automated safety check: Pass | Custom licence | |
| Mission Control Agent APIbuilderz-labs/mission-control | 6.3k | — | ~2.1k | Automated safety check: Pass | MIT |
stablyai/orca
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…
getpaseo/paseo
Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.
openobserve/openobserve
Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.
getpaseo/paseo
Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.
builderz-labs/mission-control
Teaches an agent to use the Mission Control dashboard API: register, send heartbeats, fetch assigned tasks, report progress and disconnect, with API key auth.
getpaseo/paseo
Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.
MadAppGang/claude-code
Content brief template and creation methodology for SEO-optimized content.
MadAppGang/claude-code
A skill your agent uses when detecting project technology stack from files/configs/directory structure, auto-loading framework-specific skills, or analyzing multi-stack fullstack projects (e.g…
MadAppGang/claude-code
On-page SEO optimization techniques including keyword density, meta tags, heading structure, and readability.
MadAppGang/claude-code
Techniques for expanding seed keywords and clustering by topic and intent.
MadAppGang/claude-code
SERP analysis techniques for intent classification, feature identification, and competitive intelligence.
MadAppGang/claude-code
A skill your agent uses when deciding whether to launch an agent, selecting which agent to use, or coordinating multiple agents.
Categories
A skill your agent uses when integrating detective skills across plugins. Cross Plugin Detective is an agent skill from MadAppGang/claude-code. Use when integrating detective skills across plugins.
Cross Plugin Detective fits situations like: integrating detective skills across plugins; tasks that involve Multi-agent orchestration.
Run `npx skills add MadAppGang/claude-code --skill cross-plugin-detective -a claude-code`. Or copy the skill folder (plugins/code-analysis/skills/cross-plugin-detective in MadAppGang/claude-code) into .claude/skills/cross-plugin-detective in your project. Claude Code loads it when a task matches its description.
Run `npx skills add MadAppGang/claude-code --skill cross-plugin-detective -a codex`. Or copy the skill folder (plugins/code-analysis/skills/cross-plugin-detective in MadAppGang/claude-code) into .agents/skills/cross-plugin-detective in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MadAppGang/claude-code --skill cross-plugin-detective -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cross-plugin-detective, .gemini/skills/cross-plugin-detective, .github/skills/cross-plugin-detective and .opencode/skills/cross-plugin-detective in your project.
SKILL.md names no scripts, command-line tools or credentials: Cross Plugin Detective is instructions for the agent only. Its frontmatter pre-approves these tools: Bash, Task, Read, AskUserQuestion.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Cross Plugin Detective is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.4k tokens (SKILL.md is roughly 9.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Cross Plugin Detective: Orca CLI (stablyai/orca, 89k stars), Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars), O2 Review Loop (openobserve/openobserve, 22k stars) and Paseo Committee (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
MadAppGang (a GitHub organization) maintains it in MadAppGang/claude-code, which has 285 GitHub stars. The repository holds 69 skills in this directory. The repository was last updated on March 15, 2026.
Source: MadAppGang/claude-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.