SKILLEMALL.ai
GitHub ↗ RU Sign in

CD interview-coach

High-rigor interview coaching skill for job seekers. Use when someone wants structured prep, transcript analysis, practice drills, storybank management, or performance tracking. Supports quick prep and full-system coaching across PM, Engineering, Design, Data Science, Research, Marketing, and Operations.

noamseg/interview-coach-skill Agent Skills author: noamseg 51 files body ≈ 3 656 tokens Open the sourcegithub.com↗ analyzed 6 d ago

High-rigor interview coaching skill for job seekers.

As a process D 44/100 · Unfinished process — References files that are not bundled: references/commands/[command].md

AnalyzerSales and CRMData and analyticsMarketingtype 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
89/100
safety, quality, tests
Safety 60%
93
Quality 40%
82
Run on models
none yet
Process rating
D
44/100
Unfinished process
References files that are not bundled: references/commands/[command].md
Tools and files w 18
0
Inputs and preconditions w 11
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
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 · 7

✓ No critical or high findings

Medium and low: 7
  • low Risky intent intent-offensive-security references/challenge-protocol.md:23
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    ### Story Red Team — `stories add` / `stories improve`
  • low Risky intent intent-offensive-security references/challenge-protocol.md:129
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    **Challenge without resolution is cruelty.** Every challenge invocation ends with a concrete, actionable fix — either through Lens 5 directly (Story Red Team, Transcript Challenge → Priority Move, Pre
  • low Risky intent intent-offensive-security references/commands/stories.md:71
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    ### Story Red Team (Directness Level 5)
  • low Risky intent intent-offensive-security references/commands/stories.md:173
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    ## Story Red Team (Level 5 only)
  • low Risky intent intent-offensive-security references/commands/stories.md:180
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    **Recommended next**: `stories improve S###` — strengthen the story based on the red team findings. **Alternatives**: `stories find gaps`, `practice retrieval`, `concerns`
  • low Risky intent intent-offensive-security references/commands/stories.md:190
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    ## Story Red Team (Level 5 only)
  • low Risky intent intent-offensive-security references/cross-cutting.md:216
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - `stories add` / `stories improve` → Story Red Team (all 5 lenses)

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: references/commands/[command].md

Process rating: all ten parameters 44/100

Will not run. References files that are not bundled: references/commands/[command].md
  • 0Tools and files. 1 referenced file(s) missing: references/commands/[command].md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (interview-coach) differs from the folder (interview-coach-skill)
  • 55Failures and branches. 1 branches
  • 60Result and completion. Output format stated, no completion criterion
  • 85Steps. 50 steps, 1 vague phrases
  • 100Execution cost. Instruction body is 3656 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress

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)
  • +4No input/output examples
  • +2Single-language instructions
  • +3Description length 305: enough signal without eating the budget
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 50 items
  • +3Output format is stated explicitly
  • +4Reference files are cited in the instructions (18 of 18)
  • +1License stated

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