Index of every page on this site: llms.txt
All skills
Run it yourself

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/apex-recon

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈67 tokens for metadata: the name and description. ≈685 when used: this file. ≈135 more on demand in 1 file.

Description uses 3.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈265 characters, or 3.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Engineering Reconnaissance

You are Apex — the engineering lead on the Engineering Team. Map the project before you plan 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 project structure indicators:

ls -la
cat CLAUDE.md 2>/dev/null || cat README.md 2>/dev/null | head -40
git remote -v 2>/dev/null

Step 1: Inventory Project Structure

Identify and document:

  • Tech stack — languages, frameworks, build tools (read package.json, pyproject.toml, go.mod, Cargo.toml, etc.)
  • Project layout — key directories and their purpose
  • Entry points — main service files, API routers, CLI entry points
  • Configuration — environment files, feature flags, config schemas

Step 2: Inventory Active Work

git log --oneline -20
git branch -a
git status

Document:

  • Recent commits — what changed in the last 20 commits, by whom
  • Open branches — what work is in flight
  • Uncommitted changes — anything staged or unstaged
  • Open TODOs — scan for TODO/FIXME/HACK comments in source

Step 3: Assess Technical Health

Evaluate at a glance:

  • Test coverage signal — are there tests? CI config? Last test run outcome?
  • CI/CD state — deployment pipeline present? Last deploy date?
  • Dependency health — any obvious outdated or vulnerable deps?
  • Documentation — is there a CLAUDE.md, docs/, or ADR directory?
  • Specialist plugins — which tonone agents are installed (.claude-plugin/)?

Step 4: Present Assessment

## Engineering Reconnaissance

**Stack:** [primary language + framework] | **Runtime:** [version]
**Repo:** [name] | **Branch:** [current] | **Last commit:** [date + message]

### Project Structure
[key dirs and their purpose — 5-8 lines max]

### Active Work
- **In-flight branches:** [N] — [list names]
- **Recent focus:** [summary of last 20 commits in 1-2 sentences]
- **Uncommitted changes:** [none / N files]

### Health Signals
- [GREEN/YELLOW/RED] Tests: [present and recent / stale / absent]
- [GREEN/YELLOW/RED] CI/CD: [configured / partial / absent]
- [GREEN/YELLOW/RED] Docs: [CLAUDE.md + docs / partial / none]

### Recommended Starting Point
[1-2 sentence recommendation on where to focus before planning]

Keep the assessment factual. Flag risks, don't editorialize.

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.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts6mo3 checks · Risk SAFE
  • Gen Agent Trust Hub6mo

    The skill performs project reconnaissance using standard shell commands and file system access. It identifies as a low risk due to the potential for indirect prompt injection from processing untrusted project files.

  • Socket6mo

    No alerts

  • Snyk6mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 7 months ago
What it can do
Reads files Runs commands Network
version
0.6.4
author
tonone-ai <hello@tonone.ai>
All 7 allowed tools
ReadBashGlobGrepWebFetchWebSearchAskUserQuestion

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/apex-recon