CtrlK
BlogDocsLog inGet started
Tessl Logo

codex-agent-creator

Create, validate, install, fold, or troubleshoot Codex subagent role TOML, agents-table config, discoverability wiring, and duplicate-role merges. Use when a user asks for a Codex agent role, reviewer agent, role config, TOML role file, subagent setup, or overlapping agents to merge.

75

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is highly actionable with concrete commands, a clear sequenced procedure, explicit validation feedback loops, and well-structured one-level-deep references. Its main weakness is redundancy across several overlapping sections that inflates token cost without adding new guidance.

Suggestions

Consolidate the overlapping content in Purpose, Philosophy, Preconditions, Execution Boundaries, Failure Mode, and Anti-Patterns so each guideline appears once; this would lift conciseness toward a 3.

Replace the single '<role.toml>' placeholder in the TOML syntax check with a concrete example path or a clearly named variable to keep all commands copy-paste ready.

Drop or relocate the external archived path (Infrastructure/references/deferred-skill-context/...) unless it is verified to exist, since it sits outside the skill bundle and cannot be navigated from the references directory.

DimensionReasoningScore

Conciseness

The body is directive and assumes Claude's competence (no basic-concept filler), but the same ideas recur across Purpose, Philosophy, Preconditions, Execution Boundaries, Procedure, Failure Mode, and Anti-Patterns, so it could be tightened; not a 1 because it never explains things Claude already knows, not a 3 because the cross-section redundancy means not every token earns its place.

2 / 3

Actionability

Provides fully executable, copy-paste-ready commands ('./bin/ask skills audit ... --json --robot', the tomllib one-liner) plus exact source anchors and field names; the few high-level Procedure steps and one '<role.toml>' placeholder do not drop it to the 'pseudocode/incomplete' level of a 2.

3 / 3

Workflow Clarity

A sequenced 9-step Procedure is paired with a Validation Gates section that specifies an explicit stop-and-rerun feedback loop and concrete gate commands, matching the 'clear sequence with explicit validation steps and feedback loops' anchor.

3 / 3

Progressive Disclosure

SKILL.md is an overview with clearly signaled one-level-deep references via the Context Routes section and inline links; verified referenced files (role-creation-guide.md, role-config-examples.md, contract.yaml, evals.yaml, discovery-interview.md) all exist and do not chain into deeper nested references.

3 / 3

Total

11

/

12

Passed

Description

100%

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

The description is specific, third-person, and explicitly pairs capabilities with natural 'Use when...' triggers, covering both what and when with low conflict risk. It is a strong, well-targeted skill description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Create, validate, install, fold, or troubleshoot') against specific objects ('Codex subagent role TOML, agents-table config, discoverability wiring, and duplicate-role merges'), matching the 'lists multiple specific concrete actions' anchor rather than the partial coverage of a 2.

3 / 3

Completeness

Explicitly answers what it does (the verb/object list) and when to use it ('Use when a user asks for a Codex agent role...'); the 'Use when...' trigger clause is present, so it is not capped at 2.

3 / 3

Trigger Term Quality

Natural phrasings a user would actually say ('Codex agent role, reviewer agent, role config, TOML role file, subagent setup, or overlapping agents to merge') give good coverage of common variants, beyond the 'some relevant keywords' bar of a 2.

3 / 3

Distinctiveness Conflict Risk

A clear Codex-subagent-role niche with distinct, domain-specific triggers ('TOML role file', 'subagent setup', 'overlapping agents to merge') makes it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.