CtrlK
BlogDocsLog inGet started
Tessl Logo

codex-automation-architect

Use when designing, reviewing, or updating Codex app automations, cron jobs, scheduled tasks, recurring runs, or heartbeat follow-ups.

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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, token-efficient skill body that assumes Claude's competence and routes detail to verified one-level-deep references. It pairs a sequenced workflow with explicit failure modes and validation checkpoints, with only minor inline-command gaps.

DimensionReasoningScore

Conciseness

The body is lean and sectioned into terse bullet lists with no padding or explanation of concepts Claude already knows; nearly every line is decision-relevant guidance.

5 / 5

Actionability

Gives concrete, executable direction (resolve by id/name/prompt/TOML, prefer heartbeats for short delays, use suggested create/update for worktree automations) but lacks literal tool-call command shapes inline, deferring those to references.

4 / 5

Workflow Clarity

The Workflow section sequences resolve-existing, map-kind, preflight, validate steps, with a dedicated Failure Mode section and explicit 'fail fast / stop at first failed gate' validation checkpoints for destructive automation operations.

5 / 5

Progressive Disclosure

SKILL.md is an overview with a dedicated Progressive Disclosure section pointing one level deep to real bundle files (contract.yaml, tool-examples.md, evals.yaml, task-profile.json), all verified present, plus a clearly signaled legacy path.

5 / 5

Total

19

/

20

Passed

Description

85%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 clear, third-person description with an explicit 'Use when' trigger and concrete domain actions. It is comprehensive on completeness and specificity, with only minor synonym/overlap gaps preventing a top score on trigger terms and distinctiveness.

DimensionReasoningScore

Specificity

Names the domain (Codex app automations) and several concrete actions (designing, reviewing, updating cron jobs, scheduled tasks, recurring runs, heartbeat follow-ups), though it lists object types more than distinct actions, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers 'what' (design/review/update Codex automations) and 'when' via the 'Use when' trigger clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('cron jobs', 'scheduled tasks', 'recurring runs', 'heartbeat follow-ups') with good coverage, but omits common synonyms like 'recurring tasks' or extension tokens.

4 / 5

Distinctiveness Conflict Risk

The Codex-automation niche is fairly distinct, but generic terms like 'scheduled tasks' and 'recurring runs' risk minor overlap with generic CI/scheduling skills.

4 / 5

Total

17

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
jscraik/Agent-Skills
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.