zero-in

Enforce a bounded search protocol with defined targets and stepwise reporting.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/AGM1968/weave --skill zero-in-agm1968
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zero-in
Source: https://github.com/AGM1968/weave/tree/main/.claude/skills/zero-in
Command: npx skills add https://github.com/AGM1968/weave --skill zero-in-agm1968

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents exploration from ballooning into broad, unfocused searches that waste context budgets by guiding users to define a precise target, bound the scope, and document findings before proceeding.

Core Features & Use Cases

  • Bounded search workflow: prioritizes targeted grep, then glob, then read with strict limits.
  • Target-driven discovery: requires explicit WHAT, WHY, WHEN, and HOW MANY to keep searches actionable.
  • Guardrails for high-risk discovery: enables quick pivots or aborts with documented outcomes.

Quick Start

Before starting a broad search, define a precise target and run the bounded zero-in protocol to collect focused findings.

Frequently Asked Questions about zero-in

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

FAQPage Schema
How do I prevent code search scope creep from wasting my context budget?

To prevent code search scope creep, enforce a bounded search protocol that caps scope, prioritizes targeted grep, then glob, then read with strict limits, and documents findings before proceeding.

What is the best way to define a focused search target in a large codebase?

The best way to define a focused search target is to explicitly state the WHAT, WHY, WHEN, and HOW MANY of your query to keep discovery work actionable and bounded within a structured approach.

How do I structure grep, glob, and read operations for targeted code discovery?

Structure grep, glob, and read operations by following a strict tool order: prioritize targeted grep first, then glob to locate files, then read specific sections, applying decision points to pivot or abort with documented outcomes.

When should I use a bounded search protocol for codebase exploration?

You should use a bounded search protocol when discovery work risks becoming broad and unfocused, ensuring searches stay targeted with defined targets, bounded scope, and stepwise reporting to conserve context budget.

Can I abort a high-risk discovery search and save the outcomes?

Yes, you can abort high-risk discovery searches using guardrails that enable quick pivots or aborts with documented outcomes, ensuring you capture findings before stopping the exploration.

What are the limitations of using stepwise reporting for focused code searches?

The stepwise reporting approach requires predefined targets and bounded exploration limits, meaning it is less suited for open-ended, unstructured exploration where the initial WHAT and WHY cannot be clearly defined upfront.