role-creator

Create and update Codex custom agents using standalone custom-agent TOML files.

Quality

58%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/role-creator/SKILL.md

Quality

Discovery

40%

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 identifies a clear and distinctive niche (Codex custom agent TOML files) but is too terse. It lacks an explicit 'Use when...' clause and doesn't enumerate enough concrete actions or natural trigger terms to reliably guide skill selection from a large pool.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create, edit, or configure a Codex custom agent, or mentions .toml agent files.'

Expand the list of concrete actions, e.g., 'Create, update, validate, and manage Codex custom agent definitions in standalone TOML configuration files.'

Include natural keyword variations users might use, such as 'agent config', 'agent definition', '.toml', 'custom agent setup'.

Dimension	Reasoning	Score
Specificity	Names the domain (Codex custom agents) and two actions (create and update), but doesn't list more granular capabilities like configuring parameters, managing TOML fields, or validating agent configurations.	2 / 3
Completeness	Describes what the skill does (create and update custom agents via TOML files) but has no explicit 'Use when...' clause or trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also fairly thin, placing this at 1.	1 / 3
Trigger Term Quality	Includes relevant terms like 'Codex', 'custom agents', and 'TOML files', but misses natural variations users might say such as 'agent config', 'agent definition', '.toml', or 'configure agent'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Codex custom agents' and 'TOML files' is a very specific niche that is unlikely to conflict with other skills.	3 / 3
	Total	8 / 12 Passed

Implementation

77%

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

This is a well-structured, actionable skill with clear workflows and concrete executable examples. Its main weakness is moderate verbosity from overlapping sections (non-negotiable inputs vs. role file contract) and inline content that could be split out. The guardrails and validation steps are a notable strength for operational safety.

Suggestions

Consolidate the 'Non-Negotiable Inputs' and 'Role file contract' sections to eliminate redundancy around required/optional keys.

Move the detailed role file contract and nickname_candidates requirements to a separate REFERENCE.md, keeping only a brief summary inline.

Dimension	Reasoning	Score
Conciseness	Generally efficient but includes some redundancy—e.g., restating the role file contract details that overlap with the non-negotiable inputs section, and the 'current behavior' bullets partially duplicate the workflow. The 'default policy' section is lean and useful.	2 / 3
Actionability	Provides concrete, executable shell commands with full flag examples, a ready-to-run JSON invocation example, specific file paths, and clear validation steps (tomlq). The commands section is copy-paste ready with realistic arguments.	3 / 3
Workflow Clarity	The workflow is clearly sequenced (collect → resolve path → write → validate → return example), includes a validation step (step 4: validate TOML parse and required keys), and the guardrails section provides error recovery guidance for common failure modes like unknown agent_type.	3 / 3
Progressive Disclosure	References to external docs and templates are present and one-level deep, but the templates/ reference is vague with no description of contents. The skill inlines the full role file contract and commands rather than splitting detailed reference material into separate files, making it slightly monolithic for its length.	2 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: am-will/codex-skills
Commit: ca2c3b3

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

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.