CtrlK
BlogDocsLog inGet started
Tessl Logo

autoresearch-goal

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

61

Quality

71%

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

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 a tight, well-structured workflow with concrete commands and a strong validation gate; its only weakness is redundant restatement of the Codex-state-immutability caveat.

Suggestions

State the "must not mutate hidden Codex goal state" constraint once (e.g. in the Boundary section) and reference it from Flow/Lifecycle rather than repeating it verbatim.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes competence, but the caveat "must not mutate hidden Codex goal state" repeats across Boundary, Flow step 6, and Lifecycle, which could be consolidated.

2 / 3

Actionability

Provides concrete, executable command signatures with real flags (e.g. "omx autoresearch-goal create --topic ... --rubric ... --critic-command ...") and specific tool calls ("get_goal", "update_goal({status: \"complete\"})").

3 / 3

Workflow Clarity

The 7-step Flow is clearly sequenced with an explicit validation gate ("Completion is blocked until professor-critic validation records verdict=pass") and a pass/fail/blocked feedback loop.

3 / 3

Progressive Disclosure

Under 50 lines, single-purpose, with well-organized sections (Boundary, Artifacts, Flow, Completion gate, Lifecycle) and no need for external references.

3 / 3

Total

11

/

12

Passed

Description

57%

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 carves a clear, low-conflict niche, but it is jargon-heavy and lacks an explicit "Use when..." trigger, so it tells Claude what the skill is without clearly telling it when to invoke it.

Suggestions

Add an explicit trigger clause, e.g. "Use when binding a research mission to Codex goal-mode focus with professor/critic validation."

Rewrite around natural user phrases (e.g. "run an autoresearch goal", "Codex goal mode") and drop internal qualifiers like "durable" and "without reviving deprecated" from the description.

DimensionReasoningScore

Specificity

Uses third-person voice and names the domain ("research workflow over Codex goal mode") plus an action surface ("omx autoresearch"), but does not list multiple concrete actions, falling short of the score-3 anchor.

2 / 3

Completeness

It states what the skill is ("Durable professor-critic research workflow over Codex goal mode") but provides no "Use when..." trigger, so per the guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

Contains some recognizable domain keywords ("autoresearch", "Codex goal mode") a tool user might say, but the phrasing ("durable professor-critic", "without reviving deprecated") is internal jargon rather than natural user triggers.

2 / 3

Distinctiveness Conflict Risk

The niche is specific and unlikely to conflict — binding research to Codex goal mode while explicitly distinguishing it from the deprecated "omx autoresearch" surface.

3 / 3

Total

9

/

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