caveman-explore

Locates relevant code in repositories and returns path:line citations without editing files.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/tkogut/agents-os-core --skill caveman-explore-tkogut
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: caveman-explore
Source: https://github.com/tkogut/agents-os-core/tree/main/vault/.agents/skills/caveman-explore
Command: npx skills add https://github.com/tkogut/agents-os-core --skill caveman-explore-tkogut

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an AI agent needs to find where specific logic lives in an unfamiliar codebase, broad manual searching wastes context tokens and time. This Skill acts as a read-only scout that fans out parallel searches and reports only the relevant file locations with line ranges, keeping the main agent's context clean. ## Core Features & Use Cases - Parallel Broad Search: Issues multiple Glob, Grep, and Read calls simultaneously to cover complementary hypotheses in a single turn. - Citation-Only Output: Returns a compact evidence block of path:line citations with relevance reasons, with no preamble or explanation. - Read-Only Guarantee: Never edits files, runs commands, or proposes solutions, so it is safe to delegate exploration freely. - Use Case: A solver agent needs to know where route selection happens in a large Go project. It delegates to this Skill, which replies with citations like src/router/pick.go:42-71 so the solver reads only what matters. ## Quick Start Ask the agent to find where a specific feature or symbol is implemented in this repository and report the file paths with line numbers.

Frequently Asked Questions about caveman-explore

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

FAQPage Schema
How do I find where a function is implemented in a large codebase?▼

Delegate the question to this read-only explorer, which runs parallel Glob, Grep, and Read searches across the repository. It replies with a short list of file paths and line ranges pinpointing the relevant code.

How to search a repository without polluting the main agent context?▼

Use a delegated explorer subagent whose reads stay out of the main context. This Skill performs the searching and returns only compact path:line citations, so the solver's token budget is preserved.

When should I use this explorer instead of a direct Grep search?▼

Use it for cold-start orientation, broad cross-file localization, or when a direct search already failed. Skip it when the exact file or symbol is already named, since a direct read is cheaper.

Can this Skill edit files or run shell commands?▼

No. It is strictly read-only and limited to Read, Glob, and Grep tools. It never edits files, executes commands, or proposes solutions; it only reports where relevant code lives.

What happens if the explorer cannot find anything relevant?▼

It replies with the single line 'no relevant locations found' rather than guessing. This honest negative result prevents the solver from acting on fabricated citations.