CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

keep-codex-fast

Diagnose Codex Desktop or CLI local-state bloat and safe recovery options. Use when sessions, archived history, logs, worktrees, or stale Codex config may be making Codex feel slow.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./Skills/agent-ops/keep-codex-fast/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 well-structured safety runbook: the workflow has explicit gates, validation, and failure-recovery loops, and bundle references are real, well-signaled, and one level deep. The main cost is token weight — roughly four sections restate the same mutation-safety rules, which could be consolidated without losing safety coverage.

Suggestions

Consolidate 'Avoid', 'Decision Gates', 'Safety Rules', and 'Execution Boundaries' into one safety section plus the mode table; each currently restates the same confirmation and no-mutation-while-running rules (conciseness).

Add the exact config-prune command and a concrete handoff-creation step (command or file invocation) so steps 3 and the config-prune path are executable like report/backup/apply (actionability).

Either cite references/task-profile.json in the Progressive Disclosure section or remove it from the bundle so every bundled file is discoverable from SKILL.md (progressive_disclosure).

DimensionReasoningScore

Conciseness

The body is mostly efficient runbook prose with no concept explanations Claude already knows, but safety constraints are stated four times across overlapping sections ("Avoid", "Decision Gates", "Safety Rules", "Execution Boundaries") — e.g., the no-mutation-while-running rule and the confirmation requirement each appear in three places. Anchor 3 (mostly efficient but could be tightened) fits; not anchor 2, since there is no padding or basic-concept teaching, and not anchor 4, since the redundant sections are more than minor trimmable instances.

3 / 5

Actionability

Concrete, executable commands are given for report, bounded report, backup, and apply (with the required --confirm-codex-home flag). Minor gaps keep it below anchor 5: the 'dedicated config prune command' is referenced but never shown, handoff creation (step 3) has no command or invocation, and the entrypoint path assumes a specific repo layout (Skills/agent-ops/...).

4 / 5

Workflow Clarity

The 8-step workflow is clearly sequenced with an explicit pre-apply confirmation checklist, a verification step ('Verify with a second report'), and a dedicated Failure Mode section with feedback loops ('If backup or apply validation fails, do not proceed ... rerun report mode after fixing or classifying the blocker'). This destructive/batch skill has validation and recovery loops, matching anchor 5 rather than anchor 4's 'minor validation gaps'.

5 / 5

Progressive Disclosure

The body is an overview with a dedicated 'Progressive Disclosure' section that signals each one-level-deep reference and its purpose: contract.yaml, evals.yaml, handoff-template.md, and source-review.md all exist in references/, and scripts/keep_codex_fast.py exists as the stable entrypoint exactly as described. Not anchor 4 only because of minor gaps (references/task-profile.json is in the bundle but never cited, and two Infrastructure/... paths point outside the bundle), which are navigation nits rather than organization problems.

5 / 5

Total

17

/

20

Passed

Description

73%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 solid, distinct description with an explicit third-person 'Use when' trigger clause and natural keywords. Its main weakness is that the 'what' stays at two high-level actions ('diagnose', 'safe recovery options') without naming the concrete operations (report, backup, archive, prune) the skill actually performs.

DimensionReasoningScore

Specificity

"Diagnose Codex Desktop or CLI local-state bloat and safe recovery options" names the domain plus two actions (diagnose, recovery options), but the actions stay high-level — backup, archive, report, config-prune are never named. This matches anchor 3 (domain and 1-2 concrete actions, not comprehensive) better than anchor 4, which expects several specific listed actions, and clearly above anchor 2, since 'diagnose' and 'recovery' are concrete verbs rather than generic processing.

3 / 5

Completeness

Both parts are present: a what ("Diagnose ... local-state bloat and safe recovery options") and an explicit when ("Use when sessions, archived history, logs, worktrees, or stale Codex config may be making Codex feel slow"). The when-clause is explicit with concrete triggers, but the what is slightly abstract — "safe recovery options" is not a concrete action list like anchor 5's example — so anchor 4 fits best.

4 / 5

Trigger Term Quality

Natural user phrases are well covered: "sessions, archived history, logs, worktrees, or stale Codex config", "Codex feel slow", "Codex Desktop or CLI". A few natural terms users might say are missing (e.g., 'cleanup', 'free up space', 'speed up Codex', 'disk usage'), so it fits anchor 4 (good coverage, a few natural terms missing) rather than anchor 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche: Codex-specific local-state maintenance, with product names ("Codex Desktop or CLI") and distinct trigger artifacts (sessions, worktrees, stale config). It is third-person and would not plausibly fire for other skills, matching anchor 5 (clear niche, distinct triggers, minimal conflict risk).

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/agent-ops/keep-codex-fast/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.