CtrlK
BlogDocsLog inGet started
Tessl Logo

ask-codex

Consult Codex as an independent expert. Sends a question or task to codex exec and returns the response.

61

Quality

77%

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/ask-codex/SKILL.md
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.

The content is a lean, actionable guide with executable examples for both invocation variants, a clear unsafe-form warning, and a thorough exit-code error-handling table. It is well-structured for a simple single-task skill with no need for external references.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, with tight sections and a useful error-handling table; the shell-metacharacter sentence is mild justification rather than padding. Not a 5 because a few phrases (the metacharacter list, the 'because the shell will re-parse...' explanation) could be trimmed, and not a 3 because there is no real over-explanation of known concepts.

4 / 5

Actionability

Provides copy-paste-ready executable bash commands for both the with-flag and no-flag cases, plus an explicit unsafe form to avoid, fully covering the common cases. Not a 4 because the guidance is complete and executable with no significant gaps.

5 / 5

Workflow Clarity

This is a single-task skill with an unambiguous action (run the quoted script) and an explicit exit-code feedback table for error recovery, satisfying the simple-skill exception. Not a 4 because both conditional branches and the error-recovery path are clearly sequenced, with no validation gap (the operation is non-destructive).

5 / 5

Progressive Disclosure

The body is under 50 lines with well-organized sections (How to Use, Interpreting Output, Error Handling, Notes) and no nested external references, meeting the simple-skill exception for a 5. Not a 4 because structure is clean and all content is appropriately inlined at one level.

5 / 5

Total

19

/

20

Passed

Description

53%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.

The description is third-person and states a clear 'what' with concrete actions, but it omits any explicit 'Use when...' trigger guidance, which caps completeness and limits trigger-term quality. It is distinct enough as a Codex-specific tool but would benefit from explicit usage triggers.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when you want a second opinion from an independent model or when the user asks to consult Codex.'

Broaden trigger terms with natural phrasings users would say, such as 'ask Codex', 'get a second opinion', or 'cross-check with Codex'.

Expand the action list slightly (e.g., 'consult', 'cross-check', 'delegate a subtask') to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the Codex domain and two concrete actions ('Sends a question or task to codex exec and returns the response'), but coverage is limited rather than comprehensive. It is not a 4 because no list of several specific actions is given, and not a 2 because actions are concrete rather than minimal/generic.

3 / 5

Completeness

It clearly states what the skill does ('Sends a question or task to codex exec and returns the response') but provides no 'Use when...' trigger guidance, which caps completeness at 3 per the rubric. Not a 4 because 'when' is entirely absent rather than weakly implied, and not a 2 because the 'what' is clear.

3 / 5

Trigger Term Quality

Relevant keywords like 'Codex', 'codex exec', and 'question or task' appear, but common natural variations users would say (e.g., 'ask codex', 'get a second opinion') and synonyms are missing. Not a 4 because keyword coverage is not broad enough, and not a 2 because the terms present are relevant rather than purely generic.

3 / 5

Distinctiveness Conflict Risk

The 'Codex as an independent expert' framing carves a fairly distinct niche with low conflict risk, though it could overlap with other Codex-related skills. Not a 5 because the trigger is not maximally distinct, and not a 3 because it is more specific than a broad domain mention.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
PolyArch/humanize
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.