CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

interview-coach

Full job search coaching system — JD decoding, resume, storybank, mock interviews, transcript analysis, comp negotiation. 23 commands, persistent state.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/interview-coach/SKILL.md

The canonical home for this skill is interview-coach in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 works well as a README-style overview: concise, cleanly sectioned, with concrete example invocations. But as a skill it is a launcher for an external repo — the operational content (command catalog, scoring dimensions, state management) that should be bundled in reference files is absent, leaving execution details under-specified.

Suggestions

Bundle a command reference file (e.g. references/commands.md) cataloging all 23 commands with their arguments, instead of showing only 4 examples and deferring the rest to the external repo.

Define the five scoring dimensions used by transcript "analyze" and the answer-scoring workflow, either inline or in a referenced file, so the coaching logic is actually executable.

Document the coaching_state.md lifecycle — where it lives, when it is read/updated, and how kickoff output flows into later prep/mock/negotiation commands — to give the multi-command workflow explicit sequencing.

DimensionReasoningScore

Conciseness

The body is lean with no explanations of concepts Claude already knows; commands are shown once with brief outcomes. Minor trimming possible: the Overview restates the frontmatter description, "23 total commands" repeats it again, and the Examples section partially overlaps "When to Use This Skill" and "What It Covers" — so efficient but not every token earns its place.

4 / 5

Actionability

Concrete invocations exist ("npx skills add dbhat93/job-search-os", "/coach prep Stripe Senior PM", "/coach analyze"), but operational detail is missing: only 4 of the "23 commands" are shown, the "five dimensions" scoring is never defined, and the actual instructions live in the external GitHub repo rather than anywhere in this skill. Some concrete guidance, but key details needed to execute the skill's purpose are absent — not a 2 because the given commands are executable and each example states its outcome.

3 / 5

Workflow Clarity

A rough sequence is implied (install → "/coach kickoff" → per-task commands), and state persistence via "coaching_state.md" is mentioned. But the ordering and relationship between the 23 commands is never laid out, and there are no checkpoints (e.g., how prep feeds mock drills, when to update the storybank). Sequence present but gaps and implicit checkpoints — not a 2 because the install and kickoff entry path is explicit and coherent.

3 / 5

Progressive Disclosure

Sections are well-organized and the SKILL.md stays a genuine overview, with no nested references. However, the bundle contains no reference files at all — the command catalog, scoring rubric, and state-file format that clearly belong in separate one-level-deep files are simply missing (deferred to an external repo), so structure exists but the detail layer is absent rather than well-signaled.

3 / 5

Total

13

/

20

Passed

Description

66%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 specific, well-scoped description with good natural trigger terms for the job-search domain. Its main weakness is the complete absence of an explicit 'Use when...' clause, which caps completeness and weakens its value as a trigger description.

Suggestions

Append an explicit trigger clause, e.g. "Use when starting a job search, preparing for a specific interview, analyzing an interview transcript, or negotiating an offer."

Add common synonym phrasings such as "interview prep", "behavioral interview", "offer negotiation", and "salary expectations" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists several specific capabilities — "JD decoding, resume, storybank, mock interviews, transcript analysis, comp negotiation" — plus "23 commands, persistent state". These are concrete, named capability areas rather than generic fluff, though they are feature nouns rather than action verbs and per-capability detail is thin, so not a 5.

4 / 5

Completeness

The "what" is clear ("Full job search coaching system" with enumerated capabilities and "23 commands, persistent state"), but there is no "Use when..." clause or equivalent explicit trigger guidance anywhere in the description. Per the rubric guideline, a missing 'Use when' clause caps completeness at 3; it is not a 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Contains natural terms users would actually say: "job search", "mock interviews", "resume", "transcript analysis", "comp negotiation". Missing common variations like "interview prep", "behavioral interview", "offer negotiation", so it falls just short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The job-search-coaching niche is distinct, with domain-specific triggers like "JD decoding", "storybank", and "comp negotiation". Minor overlap risk remains: "resume" and "mock interviews" could also trigger standalone resume-writing or generic interview-prep skills.

4 / 5

Total

15

/

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/interview-coach/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.