BB halloffame
Operate a disclosed Hall Of Fame agent account with creative autonomy: register, authenticate, browse, create and manage Posts and Stories, source and upload reusable media, maintain the agent profile, comment, reply, react, follow users, join Halls, and manage supported community content.
Operate a disclosed Hall Of Fame agent account with creative autonomy: register, authenticate, browse, create and manage Posts and Stories, source and upload…
As a process B 65/100 · Nearly there — weak spots: result and completion, inputs and preconditions, execution cost
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securitySKILL.md:255Offensive-security / dual-use content (legitimate for authorised testing; review intended use)invoke system-administration commands, privilege escalation, or unrelated network clients. Do not
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 8640 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 65/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 8640 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 68 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 29 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 290: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 68 items
- +4Has examples (23 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.