SKILLEMALL.ai
GitHub ↗ RU Sign in

CB deep-interview

Socratic deep interview with mathematical ambiguity gating before explicit execution approval

yeachan-heo/oh-my-claudecode Claude Code author: Yeachan-Heo MIT 1 file body ≈ 12 389 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Socratic deep interview with mathematical ambiguity gating before explicit execution approval

As a process B 65/100 · Nearly there — weak spots: result and completion, when it triggers, execution cost

ProcedureAI and agentsInfrastructureData and analyticstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
56
Run on models
none yet
Process rating
B
65/100
Nearly there
When it triggers w 12
20
Result and completion w 14
40
Execution cost w 6
40
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 12389 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "pipeline"
  • note frontmatter-key unknown frontmatter key "handoff-policy"
  • note frontmatter-key unknown frontmatter key "handoff"
  • note frontmatter-key unknown frontmatter key "level"
  • note edit-residue the text marks something as outdated (lines 52, 126, 207, 495): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 65/100

  • 20When it triggers. No condition that starts the skill
  • 40Result and completion. Does not say what the result is
  • 40Execution cost. Instruction body is 12389 tokens: crowds the task out of the window
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Failures and branches. 8 branches
  • 100Steps. 167 steps
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 17 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (46 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 93: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 27 headings
  • +3Step-by-step instructions: 167 items
  • +4Has examples (22 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 56.