atlas-recon

Map and assess documentation sources for accuracy, freshness, completeness, and discoverability.

69|8|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/tonone-ai/tonone --skill atlas-recon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atlas-recon
Source: https://github.com/tonone-ai/tonone/tree/main/team/atlas/skills/atlas-recon
Command: npx skills add https://github.com/tonone-ai/tonone --skill atlas-recon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map and assess all documentation sources across the workspace for accuracy, freshness, completeness, and discoverability.

Core Features & Use Cases

  • Detection: Detect documentation across README.md, docs/, doc/, documentation/, ADRs, and inline docs.
  • Assessment: Evaluate accuracy, freshness, completeness, and discoverability of each source.
  • Gap Analysis: Identify critical knowledge gaps in architecture, setup, API contracts, runbooks, data models, and onboarding.
  • Risks: Highlight stale docs, tribal knowledge, single points of knowledge, and broken links.

Quick Start

Run a documentation reconnaissance to map all docs and identify gaps in the knowledge base.

Frequently Asked Questions about atlas-recon

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

FAQPage Schema
How do I identify documentation gaps across architecture decisions and runbooks?

Documentation freshness is evaluated by detecting all sources and assessing each for accuracy and staleness. The assessment highlights stale docs and broken links across README files, ADRs, and inline docs to ensure knowledge base validity.

What is the best way to assess documentation discoverability and completeness?

The best way to assess discoverability and completeness is to run a reconnaissance that maps all documentation sources and evaluates quality. This identifies tribal knowledge, single points of knowledge, and broken links following standard governance practices.

Does documentation reconnaissance work for API specs and setup guides?

Documentation reconnaissance works for API specs and setup guides by detecting sources across docs directories, inline docs, and ADRs. It evaluates accuracy, freshness, completeness, and discoverability to map gaps and present a coverage risk assessment.

When should I use a documentation assessment instead of manual review?

Use a documentation assessment instead of manual review when you need to detect sources across an entire workspace and map critical knowledge gaps in data models or onboarding materials. It provides a structured coverage and risk assessment following governance practices.