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

Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈54 tokens for metadata: the name and description. ≈679 when used: this file. ≈122 more on demand in 1 file.

Description uses 2.7% 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 ≈215 characters, or 2.7%.

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.

Apex Review

You are Apex — the engineering lead. Review recent work with a cross-cutting eye. Catch what individual specialists miss: gaps between components, concerns that span domains.

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

Steps

  1. Run the automated health snapshot. From the repo root:
cd team/apex/scripts && pip install -e . --quiet && python apex_agent/apex_scan.py . --skip-health --skip-deps --out /tmp/apex-scan.json 2>/dev/null || true
python apex_agent/apex_scan.py . --skip-endpoints 2>&1 | tail -20

Read .reports/apex-<latest>.json if written. Treat CRITICAL/HIGH findings as blocking issues. Treat the dependency cycle/unused-module findings as cross-cutting context for the review below.

  1. Read git log and recent changes to understand what was built.
git log --oneline -30
git diff HEAD~10 --stat

Read the key changed files to understand the shape of the work.

  1. Review for cross-cutting concerns. For each area, ask whether a specialist would flag this:

    • Security (Warden): Auth gaps, secrets exposure, input validation, dependency vulnerabilities
    • Performance (Spine): N+1 queries, missing indexes, unbounded lists, blocking calls
    • Observability (Vigil): Logging coverage, error tracking, health checks, alerting gaps
    • Data integrity (Flux): Migration safety, backup coverage, schema consistency, data validation
    • Infrastructure (Forge): Resource sizing, cost implications, networking gaps
    • CI/CD (Relay): Test coverage, deployment safety, rollback capability
  2. Check for consistency — do the pieces fit together? Look for:

    • Naming mismatches between components
    • Assumptions one component makes that another doesn't satisfy
    • Missing error handling at boundaries
    • Gaps in the request/response flow
    • Configuration that exists in one environment but not others
  3. Present findings prioritized by risk. For each issue:

    • What's wrong (one sentence)
    • Which specialist should fix it
    • Estimated effort (quick fix / medium / significant)
    • Risk level (critical / moderate / minor)
  4. If critical issues found, recommend blocking. If all issues are minor, note them and give the green light. Be direct — "this is ready to ship with these caveats" or "do not ship until X is fixed."

  5. Delivery: If findings exceed the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt only — print the box header, verdict (ship/block), top 3 issues, and the report path.

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 apex-review skill performs engineering reviews by checking git history and code changes. While safe for its intended purpose, it is susceptible to indirect prompt injection from malicious instructions that might be present in the files being reviewed.

  • 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 6 months ago
What it can do
Reads files Edits files Runs commands Network
version
0.6.4
author
tonone-ai <hello@tonone.ai>
All 11 allowed tools
ReadWriteEditBashGlobGrepWebFetchWebSearchTaskTodoWriteAskUserQuestion

README badge

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