SKILLEMALL.ai

AB statement-coach

Coach a statement of purpose or personal essay to admission strength — structural diagnosis, specific feedback, and revision plans on YOUR draft; the words stay yours. Use when asked to review my personal statement, improve my SOP, give feedback on my application essay, or why is my essay generic. Produces a diagnostic against what committees actually read for, line-level feedback on the draft, a revision plan, and interview-style questions to mine for better material.

mohitagw15856/pm-claude-skills Agent Skills author: mohitagw15856 MIT 2 files body ≈ 894 tokens Open the sourcegithub.com analyzed 2 d ago

Coach a statement of purpose or personal essay to admission strength — structural diagnosis, specific feedback, and revision plans on YOUR draft; the words…

As a process B 67/100 · Nearly there — weak spots: when it triggers, failures and branches, running it twice

AnalyzerWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
79
Run on models
none yet
Process rating
B
67/100
Nearly there
Failures and branches w 10
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: statement-coach (mohitagw15856/pm-claude-skills)

How to improve

    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: 2. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 67/100

    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 5 mutating operations with no state check
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 23 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 894 tokens
    • low 10 top-level sections: this looks like several domains in one skill

    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
    • -41 reference files, but SKILL.md never points to them: the model will not open them
    • +1No license
    • +2Single-language instructions
    • +3Description length 473: enough signal without eating the budget
    • +4Structure: 12 headings
    • +3Step-by-step instructions: 23 items
    • +3Output format is stated explicitly

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