CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

apex-status

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.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, token-efficient body with concrete commands and a clear step sequence — genuinely strong on efficiency and actionability for the investigation steps. Its main defects are the missing `docs/output-kit.md` bundle file, which leaves the core output format underspecified and breaks the skill's only reference, and an internal inconsistency between the 40-line and 10-15-line output limits.

Suggestions

Ship the referenced `docs/output-kit.md` in the skill bundle (e.g., under `references/`), or inline the output-format skeleton into SKILL.md so the deliverable is fully specified without the missing file.

Resolve the conflicting output-length constraint: pick one limit (e.g., '10-15 lines, 40-line hard max') and state it once so the model isn't given two different targets.

Add one or two natural trigger synonyms (e.g., 'status update', 'progress check') to the description to broaden trigger coverage.

DimensionReasoningScore

Conciseness

The body is lean and efficient ("Standup, not a report. Brief, direct, actionable.") with bare commands and no explanation of concepts Claude already knows. Every token earns its place, matching the anchor-5 example of terse, heading-plus-command structure.

5 / 5

Actionability

Steps 1-3 provide copy-paste-ready commands (`git log --oneline -20`, `git status`, `ls -la README* CLAUDE* ...`), but the actual deliverable — the output format — is delegated to `docs/output-kit.md`, which does not exist in the bundle. The inline summary ("40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose") partially compensates, so this is concrete guidance with a real gap rather than a minor one, fitting anchor 4 more than 5.

4 / 5

Workflow Clarity

The five steps are clearly sequenced with a concrete command attached to each, and the skill is read-only so no validation checkpoints are required. It falls short of 5 because of a conflicting length constraint: line 14 says "40-line CLI max" (from the output kit) while step 5 says "Keep it to 10-15 lines max", leaving the model with ambiguous instructions.

4 / 5

Progressive Disclosure

Sections are well organized and the single reference is clearly signaled and only one level deep, but `docs/output-kit.md` is a broken reference — no `docs/` (or `references/`/`scripts/`/`assets/`) directory exists in the skill bundle. Navigation dead-ends at the one file the skill depends on for its output format, which fits anchor 3 (structure present but organization undermined) better than 4.

3 / 5

Total

16

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly and explicitly states both what the skill does and when to use it, with natural trigger phrases. Its only weaknesses are modest action coverage (one composite action rather than several listed) and a few missing trigger synonyms. Third-person voice is used correctly.

DimensionReasoningScore

Specificity

"CTO-level project status from git and codebase state" names the domain and one concrete action (producing a status summary) with its data source, but does not list several specific actions. This matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive') and falls short of anchor 4, which expects multiple specific actions listed.

3 / 5

Completeness

Explicitly answers both questions: what ("CTO-level project status from git and codebase state") and when ("Use when asked 'where are we', 'project status', 'what's done', or at the start of a work session") with concrete trigger phrases. This directly matches the anchor-5 example structure.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say — "where are we", "project status", "what's done", "at the start of a work session" — giving good keyword coverage. It is not a 5 because common variations such as "status update", "standup", or "progress report" are missing.

4 / 5

Distinctiveness Conflict Risk

The CTO-status niche with triggers like "where are we" and "project status" is mostly distinct from other skills. Minor overlap risk remains with general git-helper or standup/reporting skills, keeping it below a 5.

4 / 5

Total

16

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

jeremylongshore/tons-of-skills-marketplace

Path

plugins/ai-agency/tonone/skills/apex-status/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.