Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
- Clarified usage scope and MAP.md-first workflow for all code navigation tasks. - Expanded ignore rules to skip secrets, environment files, and credentials during scans. - Streamlined scanning and update instructions for clarity and concise onboarding. - Added an anti-patterns section to emphasize correct usage and security. - MAP.md structure and update procedures are now more explicit and concise.
What This Skill Does
Atris builds and maintains a structured navigation map of a codebase with exact file:line references stored in `atris/MAP.md`. Agents check the map before searching, adding new discoveries each time. Over sessions, the map grows more complete and redundant scanning drops sharply.
Instead of re-running file searches every session, Atris builds a cumulative index so each lookup is a direct jump to a known file and line number.
When to use it
- Finding where a specific function or class is defined without re-scanning
- Onboarding to an unfamiliar repo by reading the generated map
- Answering 'where is the auth logic?' during a code review
- Reducing token usage when an agent repeatedly explores the same codebase
- Keeping navigation state persistent across multiple agent sessions
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Where is the login handler in this repo?
- 1Read atris/MAP.md to check if login handler is already indexed
- 2Find entry 'handleLogin src/auth/login.ts:45' in Quick Reference section
- 3Navigate directly to src/auth/login.ts line 45
- 4If not found, run rg to locate it, then add the result to MAP.md
Returned the exact file and line reference for the login handler without scanning the full codebase