research
Deep codebase exploration with multi-angle analysis for Codex agents. Output: .agents/research/*.md. Triggers: "research", "investigate", "explore codebase", "how does X work".
Profile →npx skills add majiayu000/claude-skill-registry --skill research-boshu2-agentops-3 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# $research — Codebase Exploration (Codex Tailoring) This override captures the Codex-native execution model for research tasks. ## Codex-Native Flow ### Step 1: Setup ```bash ao codex ensure-start 2>/dev/null || true mkdir -p .agents/research ``` ### Step 2: Check Prior Art ```bash ao lookup --query "<topic>" --limit 5 2>/dev/null || true ao search "<topic>" 2>/dev/null || true ``` Search all local knowledge directories by content: ```bash for dir in research learnings knowledge patterns retros plans brainstorm; do grep -r -l -i "<topic>" .agents/${dir}/ 2>/dev/null done ``` Read matched files before proceeding to avoid redundant investigation. ### Step 3: Explore the Codebase Use `spawn_agent(agent_type="explorer", ...)` for parallel exploration branches. Each explorer gets a focused sub-question: ``` spawn_agent( agent_type="explorer", prompt="Investigate: <sub-question>. Search in <directory>. Report file:line citations." ) ``` For inline exploration (no sub-agents), use iterative retrieval: 1. Start broad with `grep -r` and `find` scoped to specific directories 2. Score results by relevance (0-1) 3. Extract new search terms from high-relevance files 4. Repeat for up to 3 refin
- Codex-Native Flow
- Step 1: Setup
- Step 2: Check Prior Art
- Step 3: Explore the Codebase
- Step 4: Synthesize Findings
- Step 5: Report Completion
- Constraints
ao codex ensure-start 2>/dev/null || true
mkdir -p .agents/research
ao lookup --query "<topic>" --limit 5 2>/dev/null || true
ao search "<topic>" 2>/dev/null || true
for dir in research learnings knowledge patterns retros plans brainstorm; do
grep -r -l -i "<topic>" .agents/${dir}/ 2>/dev/null
doneWhat does the research skill do?
Deep codebase exploration with multi-angle analysis for Codex agents. Output: .agents/research/*.md. Triggers: "research", "investigate", "explore codebase", "how does X work".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill research-boshu2-agentops-3 --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.