New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Atlas Recon

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps.

MITAuto-check: notesDevelopment

Install Atlas Recon

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill atlas-recon -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace atlas-recon --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/atlas-recon .claude/skills/atlas-recon && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
atlas-recon
GitHub stars
2.8k
Token cost
~1.1k tokens
SKILL.md length
380 words
Files
2
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps.

  • Works in 5 steps: Detect Environment → Assess Each Documentation Source → Identify Knowledge Gaps → …
  • Asked what docs exist
  • SKILL.md covers Steps and Delivery
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Atlas Recon is an agent skill from jeremylongshore/tons-of-skills-marketplace. Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked "what docs exist", "documentation assessment", or "knowledge gaps".

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `.claude-plugin/plugin.json`).

It sits in Development. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Asked what docs exist
  • Documentation assessment

Example prompts

  • “what docs exist”
  • “documentation assessment”
  • “knowledge gaps”
  • “/atlas-recon”

Requirements

  • Pre-approved tools (allowed-tools): Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Detect Environment
  2. Assess Each Documentation Source
  3. Identify Knowledge Gaps
  4. Identify Risks
  5. Present Coverage Map

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash
    • Glob
    • Grep
    • WebFetch
    • WebSearch
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Atlas Recon loads about 1.1k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 380 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~63
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 380 words, ~1,118 tokens.

Download SKILL.mdSave it as .claude/skills/atlas-recon/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
atlas-recon
description
Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked "what docs exist", "documentation assessment", or "knowledge gaps".
allowed-tools
Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
version
0.6.4
author
tonone-ai <hello@tonone.ai>
license
MIT

Documentation Reconnaissance

You are Atlas — the knowledge engineer from the Engineering Team. Map the knowledge terrain before you change anything.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Steps

Step 0: Detect Environment

Scan the workspace for documentation in all locations:

  • README.md (root and nested)
  • docs/, doc/, documentation/ directories
  • docs/adr/, docs/decisions/ — Architecture Decision Records
  • CONTRIBUTING.md, CHANGELOG.md, SECURITY.md
  • *.md files scattered through the codebase
  • API spec files: openapi.yaml, swagger.json, *.proto, schema.graphql
  • Wiki references in README or config (GitHub wiki, Notion, Confluence links)
  • Inline documentation: JSDoc, docstrings, Go doc comments
  • CI/CD configs that reference docs (doc generation steps)
Step 1: Assess Each Documentation Source

For every doc found, evaluate:

  • Accuracy — does it match the current code? Check key claims (commands, paths, configs) against reality
  • Freshness — when was it last modified? (use git log for the file) Is it older than 6 months with active code changes?
  • Completeness — does it cover what it claims to? Are there TODO/FIXME markers? Missing sections?
  • Discoverability — can someone find it? Is it linked from README? Is it in an obvious location?
Step 2: Identify Knowledge Gaps

Check for these critical areas and note which are documented vs undocumented:

  • Architecture — how the system fits together (C4 diagrams, component descriptions)
  • Setup — how to get running locally (step-by-step, verified)
  • API contracts — endpoint documentation, request/response schemas
  • Key decisions — ADRs or equivalent explaining why things are the way they are
  • Deploy process — how code gets to production
  • Runbooks — what to do when things break
  • Data model — schema documentation, entity relationships
  • Onboarding — getting a new engineer productive
Show full SKILL.md (117 more words)Show less
Step 3: Identify Risks

Flag:

  • Stale docs that are wrong — worse than no docs, they create false confidence
  • Tribal knowledge — areas where the code is complex but no documentation exists
  • Single points of knowledge — only one person knows how something works
  • Broken links — docs that reference other docs that don't exist
  • Orphaned docs — files that exist but aren't linked from anywhere
Step 4: Present Coverage Map
## Documentation Reconnaissance

### Coverage Map
| Area | Status | Location | Last Updated | Accuracy |
|------|--------|----------|-------------|----------|
| README | [exists/missing] | [path] | [date] | [accurate/stale/wrong] |
| Architecture | [exists/missing] | [path] | [date] | [accurate/stale/wrong] |
| Setup guide | [exists/missing] | [path] | [date] | [accurate/stale/wrong] |
| API specs | [exists/missing] | [path] | [date] | [accurate/stale/wrong] |
| ADRs | [N found / missing] | [path] | [date] | [accurate/stale/wrong] |
| Deploy docs | [exists/missing] | [path] | [date] | [accurate/stale/wrong] |
| Runbooks | [exists/missing] | [path] | [date] | [accurate/stale/wrong] |
| Data model | [exists/missing] | [path] | [date] | [accurate/stale/wrong] |
| Onboarding | [exists/missing] | [path] | [date] | [accurate/stale/wrong] |

### Priority Gaps (fix these first)
1. [most critical undocumented area — why it matters]
2. [second priority]
3. [third priority]

### Stale Docs (update or delete)
- [doc] — last updated [date], [what's wrong]

### Tribal Knowledge Risks
- [area with no docs and complex code]

### What's Good
- [positive observation — docs that are accurate and maintained]

Keep the assessment factual. Prioritize gaps by risk to the team.

Delivery

If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in plugins/ai-agency/tonone/skills/atlas-recon of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • .claude-plugin/plugin.json

Open the folder on GitHubat commit cfae287

Compare with similar skills

Atlas Recon next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Atlas Recon compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Atlas Recon this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.1kAutomated safety check: NotesMIT
Backend Code Reviewlanggenius/dify158k—~676Automated safety check: PassCustom licence
Native Data FetchingCherryHQ/cherry-studio-app4k6 repos~2.9kAutomated safety check: NotesMIT
Twenty App Entity Developmenttwentyhq/twenty58k—~1.8kAutomated safety check: PassCustom licence
Go Pedantrychromedp/chromedp13k—~3.7kAutomated safety check: PassMIT
Gumroad Prod Consoleantiwork/gumroad9.8k—~2.9kAutomated safety check: NotesMIT

Similar skills

  • Backend Code Review

    langgenius/dify

    Reviews backend code under api/ for concrete, reproducible defects, routes to rule packs for architecture, schema, repositories and SQLAlchemy, and ranks findings from P0 to P3.

    158k GitHub stars~676 tokensUpdated today
    DevelopmentAuto-check passed

  • Native Data Fetching

    CherryHQ/cherry-studio-app

    A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.

    4k GitHub starsUsed in 6 repos~2.9k tokens
    DevelopmentAuto-check: notes

  • Twenty App Entity Development

    twentyhq/twenty

    Guides changes to an existing Twenty app: adding or editing objects, layouts, logic functions and front components, with a plan stated before multi-entity edits.

    58k GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Go Pedantry

    chromedp/chromedp

    This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…

    13k GitHub stars~3.7k tokensUpdated today
    DevelopmentAuto-check passed

  • Gumroad Prod Console

    antiwork/gumroad

    Execute read-only Ruby/Rails commands against Gumroad's production database for debugging and investigation.

    9.8k GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check: notes

  • LangBot Plugin Development

    langbot-app/LangBot

    Guides building, debugging and testing LangBot plugins: components, SDK calls, README and locale rules, SDK pitfalls and WebSocket-based testing.

    18k GitHub stars~3.9k tokensUpdated today
    DevelopmentAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo

  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes

  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed

  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Atlas Recon

What does Atlas Recon do?

Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Atlas Recon is an agent skill from jeremylongshore/tons-of-skills-marketplace. Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps.

When should I use Atlas Recon?

Atlas Recon fits situations like: asked what docs exist; documentation assessment.

How do I install Atlas Recon in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill atlas-recon -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/atlas-recon in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/atlas-recon in your project. Claude Code loads it when a task matches its description.

How do I install Atlas Recon in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill atlas-recon -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/atlas-recon in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/atlas-recon in your project. Codex loads it when a task matches its description.

Can I use Atlas Recon in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill atlas-recon -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/atlas-recon, .gemini/skills/atlas-recon, .github/skills/atlas-recon and .opencode/skills/atlas-recon in your project.

What does Atlas Recon need to run?

SKILL.md names no scripts, command-line tools or credentials: Atlas Recon is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion.

Does Atlas Recon access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Atlas Recon safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Atlas Recon use?

Atlas Recon is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Atlas Recon use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Atlas Recon?

Skills that share tags, products or a category with Atlas Recon: Backend Code Review (langgenius/dify, 158k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Twenty App Entity Development (twentyhq/twenty, 58k stars) and Go Pedantry (chromedp/chromedp, 13k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Atlas Recon?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.