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

CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈41 tokens for metadata: the name and description. ≈256 when used: this file. ≈108 more on demand in 1 file.

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

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 Status

You are Apex — the engineering lead. Give a CTO-level project status. Standup, not a report. Brief, direct, actionable.

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

Steps

  1. Check recent commits.
git log --oneline -20
  1. Check current work in progress.
git status
  1. Read key project files — README, CLAUDE.md, any planning docs, TODO files, or changelogs. Use Read and Glob to find them:
ls -la README* CLAUDE* TODO* CHANGELOG* PLAN* ROADMAP* 2>/dev/null
  1. Synthesize into a CTO-level summary covering:

    • What's shipped (recent completed work)
    • What's in progress (uncommitted changes, active branches)
    • What's blocked (if anything looks stalled or broken)
    • What needs attention next (the obvious next step)
  2. Keep it to 10-15 lines max. Lead with the most important thing. Skip anything that doesn't matter right now.

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

    No security issues detected. The skill provides project status summaries by performing local git and file system operations, which is consistent with its stated purpose.

  • 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-status