CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

figure-it-out

Design a rigorous bespoke playbook for a task no bundled skill fits — steps that each end in a check, verification commands, failure branches — stored where the checker validates and anchor-validated. For recurring unusual task shapes.

Quality

82%

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

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.

An unusually strong body: concrete executable commands, a rigorously sequenced workflow with explicit validation and failure branches, and tight token economy. The only structural consideration is that the environment-specific checker-resolution logic sits inline where a reference file could keep SKILL.md leaner.

DimensionReasoningScore

Conciseness

The body is dense and imperative with rationale lines that earn their place ("Improvisation under failure is where playbooks die; write the branch"), but a few spots could be trimmed — "Standalone installs reach the script by walking up from the `omc` binary..." restates what the code loop visibly does — fitting anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: the checker-resolution bash block, `node "$checker" "$PWD" --print-playbooks-dir`, the `$playbooks_dir/<name>.md` storage template with frontmatter, concrete anchoring operators, `node "$checker" .`, and the ledger path. Matches anchor 5.

5 / 5

Workflow Clarity

The 5-step design workflow is clearly sequenced with every step ending in a check, an explicit validation command, and feedback loops for error recovery (dry-run with fix-the-playbook loop, retry/rollback/stop-and-report branches, "Report what it prints; never guess"). Matches anchor 5.

5 / 5

Progressive Disclosure

No bundle files exist and the ~95-line body is well-organized into clear sections with content appropriately inline (the resolution script is needed on every invocation). It misses anchor 5 because it is over the 50-line simple-skill threshold and the OMC resolution detail is borderline reference material with no well-signaled external reference structure — anchor 4 fits.

4 / 5

Total

18

/

20

Passed

Description

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

A dense, distinctive description with concrete capability enumeration and an explicit when-clause, weakened mainly by jargon-heavy trigger language that users would rarely type verbatim. The niche (fallback playbook designer for uncovered recurring tasks) is unusually well-differentiated.

Suggestions

Rewrite the when-clause around natural user phrases, e.g. "Use when a recurring task has no bundled skill covering it (e.g. a recurring unusual release, compliance, or backfill procedure)".

Replace or gloss jargon terms like "bespoke", "anchor-validated", and "task shapes" with plain wording users would actually say.

Mention the dry-run/validation loop in the description since it is a core part of the skill's workflow.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Design a rigorous bespoke playbook", "steps that each end in a check, verification commands, failure branches", "stored where the checker validates and anchor-validated" — but coverage has minor gaps (the dry-run loop is absent) and "anchor-validated" is opaque, matching anchor 4 rather than the comprehensive anchor 5.

4 / 5

Completeness

Both parts are explicit: a clear "what" (design a playbook with checkable steps, verification commands, failure branches, validated storage) and a "when" ("For recurring unusual task shapes"). The when-clause is present but could be more explicit with concrete trigger phrases, matching anchor 4 rather than 5.

4 / 5

Trigger Term Quality

Phrases like "recurring unusual task shapes" and "a task no bundled skill fits" give some relevant keywords, but the language leans designer-jargon ("bespoke", "task shapes", "anchor-validated") over natural user phrasing and misses common variations, fitting anchor 3.

3 / 5

Distinctiveness Conflict Risk

"a task no bundled skill fits" explicitly carves out a fallback niche that defers to every other skill, giving distinct triggers and minimal conflict risk — a clear match for anchor 5.

5 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository

Yeachan-Heo/oh-my-claudecode

Path

skills/figure-it-out/SKILL.md

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.