CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deep-interview

Socratic deep interview with mathematical ambiguity gating before explicit execution approval

Quality

68%

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/deep-interview/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 skill body is exceptionally actionable and workflow-safe, with concrete prompts, schemas, gating logic, and feedback loops throughout. Its main weaknesses are significant verbosity from repeated rules and padded explanations, and a monolithic structure with no progressive disclosure despite citing nonexistent docs files.

Suggestions

Consolidate the repeated instructions into a single statement each: the Phase 0 threshold-marker requirement, the prompt-budget/summarization rules, and the artifact-path discipline are each restated 3-5 times across Execution Policy, phases, and the Final Checklist.

Split the body into one-level-deep reference files (e.g. the Advanced/configuration material, the full spec template, and the quality-gates/company-context procedures) and either ship the cited docs/*.md files or remove those references.

Trim explanatory asides that assume low reader competence, such as 'This avoids division by zero', the 'Why 3 stages?' rationale section, and the Round 0 four-component fixture narrative.

DimensionReasoningScore

Conciseness

The ~815-line body repeatedly restates the same rules (the threshold-marker requirement appears in Phase 0, the Phase 1 announcement, step 3.5, and the Final Checklist; prompt-budget rules appear in at least five places) and includes tutorial-style padding such as the 'Why 3 stages?' explainer and the four-component fixture narrative. This matches 'noticeably verbose; several unnecessary explanations or padded sections'; not 1 because it avoids explaining basic concepts Claude already knows, and not 3 because the redundancy goes beyond a few trimmable spots.

2 / 5

Actionability

The body provides fully executable guidance: an exact state JSON schema, a copy-paste ambiguity-scoring prompt, explicit formulas, a complete spec template, exact artifact paths (e.g. '.omc/specs/deep-interview-{slug}.md'), an exact required first output line, and concrete Skill() invocations for each execution option. This matches the 'fully executable; copy-paste ready' anchor; not 4 because the remaining gaps are negligible.

5 / 5

Workflow Clarity

The multi-phase sequence is clearly ordered (blocking Phase 0 → Phase 1 init → Round 0 topology gate → interview loop → challenge agents → crystallization → execution bridge) with explicit validation checkpoints and feedback loops: step 3.5 re-verifies Phase 0 resolution, quality-gate BLOCK verdicts return to Phase 2 for revision and re-gating, round caps and escalation conditions are enumerated, and a final checklist consolidates verification. Matches the top anchor with validation steps, feedback loops, and checklists; not 4 because checkpoints are pervasive rather than merely 'most'.

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), and the two cited paths ('docs/company-context-interface.md', 'docs/quality-gates-configuration.md') are absent from the bundle, so everything — Advanced/configuration, the full spec template, examples, and gate procedures — is inlined in a single 815-line file. Real section structure exists, matching 'some structure but content that should be separate is inline'; not 2 because the structure is far from minimal, and not 4 because the bulk clearly belongs in one-level-deep reference files.

3 / 5

Total

15

/

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 a distinctive, jargon-leaning tagline that communicates a clear niche but omits trigger guidance entirely and lists few concrete actions. It would benefit most from an explicit 'Use when...' clause and a richer set of natural trigger phrases.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user has a vague idea, says "interview me" or "ask me everything", or wants requirements clarified before execution.'

Replace abstract phrasing ('mathematical ambiguity gating') with one or two concrete actions such as 'asks one targeted question per round, scores clarity across weighted dimensions, and writes a crystallized spec'.

Include natural user phrasings and synonyms ('requirements gathering', 'clarify my idea', 'don't assume') to improve trigger term coverage and disambiguation from general planning skills.

DimensionReasoningScore

Specificity

The description names the domain with two action-ish phrases ("Socratic deep interview", "mathematical ambiguity gating") but lists no concrete actions such as asking targeted questions, scoring clarity dimensions, or writing a spec, matching the 'names domain and 1-2 concrete actions' anchor. It is not 4 because coverage of specific capabilities is thin, and not 2 because it conveys more than a bare domain label.

3 / 5

Completeness

The 'what' is moderately clear (Socratic interviewing with ambiguity gating before approved execution), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline. Not 2 because the 'what' is not vague; not 4 or higher because 'when' is entirely absent.

3 / 5

Trigger Term Quality

"deep interview" is a natural phrase a user would say, but common variations like "requirements", "clarify my idea", "vague idea", or "ask me questions" are missing, matching the 'some relevant keywords but missing common variations' anchor. Not 4 because keyword coverage is sparse; not 2 because the present terms are genuinely user-spoken rather than generic.

3 / 5

Distinctiveness Conflict Risk

"Socratic deep interview with mathematical ambiguity gating" carves a distinct niche with low collision risk against other skills, though it could mildly overlap with general planning/requirements-gathering skills. Matches 'mostly distinct; minor overlap risk'; not 5 because no distinct trigger phrases are supplied to fully disambiguate from those adjacent skills.

4 / 5

Total

13

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (824 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

Yeachan-Heo/oh-my-claudecode

Path

skills/deep-interview/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.