Indexion Agent Orient

Before you start coding in unfamiliar territory, this generates a structure brief that tells you which packages likely own the feature, where consumers call it, and which files you absolutely shouldn't edit. It builds an ownership map from code structure, READMEs, and wiki pages, then renders a short evidence-backed summary you can paste into CLAUDE.md or hand to a subagent. The workflow is explicit about keeping CLI code thin and not mistaking documentation paths for implementation targets. Useful when you need to delegate work to a zero-knowledge agent or when anchoring on prompt keywords would send you to the wrong part of the codebase. The quiz-before-implementation gate is a nice forcing function.

skills.sh installs: 4.9K
GitHub stars: 2
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add trkbt10/indexion-skills --skill indexion-agent-orient --agent claude-code

Installs into .claude/skills of the current project.

Files

Agent Orientation Workflow

Use this skill before starting implementation in an unfamiliar or ambiguous part of a codebase.

Why

Coding agents often anchor on the path or noun in the user prompt and start editing before they have learned the repository's ownership structure. indexion agent orient builds an incremental orientation map across the selected codebase, then renders a short, evidence-backed brief that can be pasted into AGENTS.md, CLAUDE.md, a Claude slash command, a Codex skill, or a subagent prompt.

The rendered --limit is only a display limit. Owner inference must come from the full prebuilt map, including code structure, package READMEs, and wiki pages whose provenance is maintained by wiki pages update, wiki pages ingest, and plan reconcile.

Owner profiles use package documentation and owner-specific wiki pages. Broad wiki pages with multiple source roots are useful background, but they should not be treated as proof that every referenced package owns the task.