CtrlK
BlogDocsLog inGet started
Tessl Logo

autoresearch-goal

Durable professor-critic research workflow over Codex goal mode without reviving deprecated omx autoresearch

60

Quality

69%

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 ./plugins/oh-my-codex/skills/autoresearch-goal/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 body is a tight, actionable workflow with strong sequencing and an explicit completion gate. The main weakness is repeated restatement of the no-mutation boundary and the lifecycle, which could be consolidated to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence, but the prohibition on mutating hidden Codex goal state is stated three times (Boundary, Flow step 6, and the final Lifecycle paragraph) and the create/update/clear lifecycle is restated, which is more than minor padding.

3.5 / 5

Actionability

The flow gives concrete, copy-paste-ready commands for every step (omx autoresearch-goal create/handoff/verdict/complete plus get_goal, create_goal, update_goal({status: "complete"}), /goal clear), covering the common cases.

5 / 5

Workflow Clarity

A clear seven-step sequence with an explicit completion gate ('blocked until professor-critic validation records verdict=pass'), a re-query of get_goal before completion, and the terminal /goal clear cleanup, providing explicit checkpoints and feedback loops for the state-mutating operations.

5 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files in references/scripts/assets, and is organized into clearly labeled sections (Boundary, Artifacts, Flow, Completion gate), satisfying the simple-skill exception for a top progressive_disclosure score.

5 / 5

Total

18.5

/

20

Passed

Description

50%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 distinctive and names a clear niche, but it leans on internal jargon rather than natural trigger terms and omits any explicit 'Use when...' guidance. Adding user-facing trigger phrases would lift both completeness and trigger_term_quality.

Suggestions

Append a 'Use when ...' clause naming natural trigger situations (e.g., 'Use when a research mission needs Codex goal-mode focus with professor/critic validation').

Replace or supplement jargon terms ('professor-critic', 'OMX state owner') with phrases users would actually say, like 'goal-driven research' or 'validated research mission'.

Lead with the concrete capability (e.g., 'Runs a validated, goal-bound research mission') before the boundary caveat.

DimensionReasoningScore

Specificity

Names the domain and a concrete workflow type ('professor-critic research workflow over Codex goal mode'), but the only true action verbs are conceptual and the trailing 'without reviving deprecated omx autoresearch' is a boundary constraint rather than a capability.

3 / 5

Completeness

The 'what' is clear (a durable research/validation workflow bound to Codex goal mode), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

The keywords ('Codex goal mode', 'professor-critic', 'omx autoresearch') are internal jargon; a user is unlikely to naturally say 'professor-critic research workflow over Codex goal mode', and common natural phrasings for triggering the skill are absent.

2 / 5

Distinctiveness Conflict Risk

The niche is highly specific (Codex goal mode + OMX state ownership + professor-critic validation) and unlikely to overlap with other skills, giving it distinct triggers and minimal conflict risk.

5 / 5

Total

13

/

20

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
Yeachan-Heo/oh-my-codex
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.