CtrlK
BlogDocsLog inGet started
Tessl Logo

best-practice-research

[OMX] Bounded best-practice research wrapper using official/upstream evidence first

52

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/oh-my-codex/skills/best-practice-research/SKILL.md

The canonical home for this skill is best-practice-research in Yeachan-Heo/oh-my-codex

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-structured, actionable routing skill with a concrete output template and clear stop/handoff checkpoints. Its main weakness is repetition of the terminal/handoff boundary and routing rules across multiple sections, which inflates token cost without adding guidance.

Suggestions

Consolidate the repeated 'terminal/read-only/do-not-implement/handoff' message into one section (e.g., Terminal By Default) and reference it from Workflow and Stop Rules rather than restating it.

De-duplicate routing across Activate When, Do Not Activate When, Specialist Routing, and Workflow so each section adds distinct information.

Add one short worked example in the Output Contract (a filled-in recommendation for a representative question) to push actionability toward fully executable.

DimensionReasoningScore

Conciseness

The body does not explain concepts Claude already knows, but the 'terminal/read-only/do-not-implement/handoff' message repeats across Terminal By Default, Workflow step 5, Stop Rules, and the Output Contract, and routing recurs across Activate When, Do Not Activate When, Specialist Routing, and Workflow. It is not a 4 because the redundancy is more than minor, and not a 2 because it is not severely padded.

3 / 5

Actionability

Guidance is concrete and executable: named specialists (explore, researcher, dependency-expert), a copy-paste Output Contract template, and specific source-quality rules (include URLs, state date/version). It is not a 5 because no worked example covers a common case end-to-end, and not a 3 because the guidance is specific rather than pseudocode-level.

4 / 5

Workflow Clarity

The 5-step Workflow is clearly sequenced with decision checkpoints (stop when grounded enough, route upward, report exact blocker) reinforced by Stop Rules. It is not a 5 because there is no explicit validate-then-fix-then-retry feedback loop, and not a 3 because checkpoints are present and explicit rather than implicit.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed; the skill is self-contained and well-sectioned with clear headers. It is not a 5 because at ~80 lines it exceeds the under-50-line simple-skill threshold and routing content overlaps across sections, and not a 3 because structure is clearly good with no monolithic wall or buried references.

4 / 5

Total

15

/

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 states a clear purpose and methodology but omits any explicit 'Use when...' trigger guidance, which caps completeness and limits trigger-term coverage. It is reasonably specific to a best-practice research niche yet carries real overlap risk with general research skills.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when a task needs current best practices, official recommendations, standards, version-aware guidance, or upstream behavior').

Broaden trigger-term coverage with natural synonyms users say: 'standards', 'recommended approach', 'current guidance', 'official documentation'.

Sharpen distinctiveness by contrasting the trigger scope against general research (e.g., 'for evidence-gathering on an already-chosen technology, not dependency selection').

DimensionReasoningScore

Specificity

Names the domain ('best-practice research') and one concrete behavior ('using official/upstream evidence first'), matching the anchor that lists domain plus 1-2 concrete actions. It is not a 2 because it does more than generically name the domain, and not a 4 because no list of several specific actions is given.

3 / 5

Completeness

The description gives a clear 'what' ('best-practice research wrapper using official/upstream evidence first') but includes no 'Use when...' trigger clause, so completeness is capped at 3 per the rubric guideline. It is not a 4 because 'when' is entirely absent, and not a 2 because the 'what' is explicit rather than vague.

3 / 5

Trigger Term Quality

'best-practice' is a natural term users say, and 'official/upstream evidence' is partially natural, but common variations like standards, guidance, recommendations, or documentation are missing. It is not a 4 because keyword coverage is thin beyond 'best-practice', and not a 2 because at least one genuinely natural keyword is present.

3 / 5

Distinctiveness Conflict Risk

The 'best-practice research' niche with 'official/upstream evidence first' is somewhat specific, but unresolved overlap with sibling research skills (researcher, deep-research) keeps it at the 'somewhat specific but could overlap' anchor. It is not a 4 because the conflict with those skills is non-trivial within the description alone, and not a 2 because the niche is narrower than 'very broad'.

3 / 5

Total

12

/

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