research-worker

Explore codebases read-only and report findings, options, and unknowns.

5|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/lidge-jun/cli-jaw-skills --skill research-worker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-worker
Source: https://github.com/lidge-jun/cli-jaw-skills/tree/main/research-worker
Command: npx skills add https://github.com/lidge-jun/cli-jaw-skills --skill research-worker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill acts as a read-only investigator, helping to reduce uncertainty about a codebase before planning or during development by searching and analyzing existing code and documentation.

Core Features & Use Cases

  • Codebase Exploration: Safely search and read code files, identify imports, and check function signatures without making any changes.
  • Uncertainty Reduction: Investigate ambiguous requests or unfamiliar code patterns before committing to a plan or implementation.
  • Structured Reporting: Provides clear, actionable reports on findings, options, and unknowns.
  • Use Case: Before starting a new feature, use this Skill to understand how a similar feature was implemented in the past by searching for relevant code patterns and dependencies.

Quick Start

Use the research-worker skill to find all usages of the 'getUserById' function within the src directory.

Frequently Asked Questions about research-worker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce uncertainty about a codebase before planning a new feature?

You can reduce codebase uncertainty by performing a read-only investigation to search local files and memory for existing patterns and dependencies. This approach safely analyzes code and documentation to provide structured reports on findings, options, and unknowns before you commit to a plan.

How do I safely explore code and identify imports without modifying files?

Safely exploring code requires a strictly read-only investigator that searches local files and checks function signatures without writing code. This method prohibits file modifications and destructive commands, ensuring your codebase analysis remains completely non-destructive.

What is the best way to investigate unfamiliar code patterns during development?

The best way to investigate unfamiliar code patterns is using an AI agent to search local codebases and external documentation. This reduces uncertainty by delivering structured reports on findings, options, and unknowns regarding ambiguous requests or dependencies.

Can I use an AI agent to find all usages of a function within the src directory?

Yes, you can use an AI agent to find all usages of a function within the src directory. The agent performs read-only codebase exploration, prioritizing local searches to identify imports and check function signatures without making any file modifications.

What are the limitations of using a read-only codebase analysis approach?

The main limitation of read-only codebase analysis is the strict prohibition on file modifications, code writing, or destructive commands. It is designed solely for investigation and uncertainty reduction, meaning you cannot use it to directly implement or deploy changes.

Why does my AI agent need structured reports on findings and unknowns?

AI agents need structured reports on findings and unknowns to effectively reduce uncertainty before planning or during development. These reports consolidate codebase exploration results, options, and external documentation into clear, actionable insights.