CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

idk

Calibrate interview explanations from the user's stated understanding

Quality

76%

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/idk/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 highly actionable, well-sequenced instruction skill: concrete syntax and examples, a copy-paste-ready output template, explicit validation checkpoints, and a calibration feedback loop. Its only weaknesses are minor repetition and a longish inline body where a shared reference for the footer convention could relieve token cost.

DimensionReasoningScore

Conciseness

The body is dense with skill-specific instructions (level definitions, an output template, guardrails) and never explains concepts Claude already knows; the only padding is minor, e.g. the meta.interview_calibration pass-through is stated in both section 3 and step 4.5. Not 5 — a few sentences could be trimmed; not 3 — there is no editorializing or unnecessary background explanation.

4 / 5

Actionability

Provides exact CLI syntax ("ooo idk <terms I do not know...>"), three varied input examples, a copy-paste-ready calibration output template, three concretely defined levels with per-level wording rules, a low/medium/high confidence scale, and explicit argument-passing instructions for the MCP runtime. Not 4 — the common cases are covered and the output format is fully executable with no significant gaps.

5 / 5

Workflow Clarity

Four sequenced phases (extract evidence → estimate level/confidence → emit the calibration block → apply during a pending interview) plus a numbered 5-step mid-interview procedure, with explicit checkpoints: "Ask one short follow-up only when the supplied text is too ambiguous", "advance the interview only after the user answers it", and a feedback loop — "Treat the estimate as provisional. Update it when later answers show stronger or weaker topic knowledge". Not 4 — checkpoints and the update loop are explicit rather than implicit.

5 / 5

Progressive Disclosure

The skill is self-contained (no references/, scripts/, or assets/ directories exist, and the body cites no bundle files, so there are no dead references) with clean, well-labeled sections. Not 5 — at ~119 lines the body exceeds the simple-skill threshold and is entirely inline; the RFC #1392 breadcrumb-footer convention is a cross-cutting rule that could live in a shared reference file; not 3 — everything inlined genuinely belongs to this skill and navigation is easy.

4 / 5

Total

18

/

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 concise, third-person, and states a clear, niche 'what', but it omits any explicit 'when to use' guidance and lacks the natural trigger phrases users would say when they need this skill. Completeness and trigger coverage hold it to the middle of the scale despite low conflict risk.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user says they don't know or only partly understand terms, before or during an ooo interview."

Include the natural phrasings users would actually say — "I don't know", "unfamiliar", "explain at my level", "jargon" — so the skill surfaces from real user wording.

Name one or two more concrete actions (e.g. "defines unknown terms before use and rephrases pending interview questions at the calibrated level") to raise specificity.

DimensionReasoningScore

Specificity

"Calibrate interview explanations from the user's stated understanding" names the domain (interview explanations) and one concrete action (calibrate) with its input basis, but does not list the multiple operations the body actually covers (set explanation level, define unknown terms, rephrase pending questions). Not 4 — only one action verb is given; not 2 — the stated-understanding basis makes it more informative than a bare domain-plus-generic-verb description.

3 / 5

Completeness

The 'what' is clear (calibrates interview explanations from user-stated evidence), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3. Not 4 — the 'when' is only weakly implied by "from the user's stated understanding".

3 / 5

Trigger Term Quality

Relevant keywords are present ("interview", "explanations", "calibrate", "understanding"), but the natural phrases a user would actually say — "I don't know X", "explain at my level", "unfamiliar", "jargon" — are absent. Not 4 — common variations and synonyms are missing; not 2 — several genuinely relevant keywords appear.

3 / 5

Distinctiveness Conflict Risk

The niche focus on interview explanation calibration is mostly distinct, with only minor overlap risk against sibling interview skills (the body shows it operates alongside `ooo interview` rather than competing with it). Not 5 — without explicit trigger phrases, it cannot be fully disambiguated from other interview-related skills.

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

Q00/ouroboros

Path

skills/idk/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.