SKILLEMALL.ai

BC ai-interview

Run AI-powered mock interviews using Fuku.ai's free public service.

modbender/skill-library-mcp Agent Skills author: modbender MIT 4 files body ≈ 1 428 tokens Open the sourcegithub.com analyzed 2 d ago

Run AI-powered mock interviews using Fuku.ai's free public service.

As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureWordAI and agentsSoftware developmentData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
98
Quality 40%
69
Run on models
none yet
Process rating
C
54/100
Has gaps
Result and completion w 14
0
When it triggers w 12
20
Inputs and preconditions w 11
30
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.
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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Secrets in code secret-high-entropy-token run.js:85
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "X-NUMBER": "job-…aF0",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:22
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | **X-NUMBER Header** | `job-…aF0` |
    table

Files scanned: 4. 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")

Process rating: all ten parameters 54/100

  • 0Result and completion. Does not say what the result is
  • 20When it triggers. No condition that starts the skill
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 1 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
  • 100Steps. 43 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1428 tokens
  • 100Progress reporting. Reports progress
  • low 10 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (4 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 67: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 43 items
  • +4Has examples (3 code blocks)

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