BB college-prep-tracker
Keep an ongoing, saved tracker of a student's college application process: schools, application and essay status, recommendation letters, test scores, scholarships, financial aid, and deadlines, with a built-in junior and senior year timeline. Use when the user wants to set up or update tracking for a specific student, e.g. 'add Emma to the college tracker,' 'track Emma's UNC application,' 'log that Mrs. Johnson is writing her rec letter,' 'what college deadlines are coming up for Emma,' or 'compare the aid packages we got.' Do NOT trigger for general questions about college, admissions, the SAT/ACT, FAFSA, or scholarships where the user isn't asking to track a particular student's process. Saves data locally in college-data.json (no network); tells the user what's saved and deletes on request.
Keep an ongoing, saved tracker of a student's college application process: schools, application and essay status, recommendation letters, test scores…
As a process B 74/100 · Nearly there — weak spots: inputs and preconditions, running it twice
How to improve
- 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: 4. 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 74/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 10 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 85Steps. 132 steps, 2 vague phrases
- 100Tools and files. No external tools needed
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3655 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 805: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 28 headings
- +3Step-by-step instructions: 132 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.