BC Gifts
Researches special, uncommon, high-quality gift ideas for specific people in the principal's life, from a registry of recipients with ages and interests, using what is trending in each interest right now. USE WHEN gift ideas, gifts for, what should I get, present for, birthday gift, Christmas gift, holiday gift, find a gift, run the gifts workflow, gift ideas for a group, add a gift recipient, new gift person, update their interests. NOT FOR buying or ordering the gift, general product research unrelated to a recipient (Research), looking up who a person is (People via `people who`).
This skill promises to suggest gifts for specific people from a recipient registry, factoring in age, interests, and current trends. The package contains six files and one script, with code quality rated 82. No critical errors found, references intact, safety score maxed. Process score sits at 54—a hint that the matching logic isn't particularly flexible. No model runs or sandbox tests on record. The skill knows its lane: triggers on "gift for", "birthday present", but stays out of purchasing and people lookups. Worth installing if you already maintain a recipient registry and can work with what the workflow surfaces. Hard to judge effectiveness without a real run.
Researches special, uncommon, high-quality gift ideas for specific people in the principal's life, from a registry of recipients with ages and interests…
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "evals"
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 11 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 887 tokens
- low The response is described with custom markup (8 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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 590: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 11 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.