BF structs-onboarding
Onboards a new player into Structs. Handles key creation/recovery, player creation (via reactor-infuse or guild signup), planet exploration, and initial infrastructure builds. Use when starting fresh, setting up a new agent, creating a player, claiming first planet, or building initial infrastructure. Build times range from ~17 min (Command Ship) to ~57 min (Ore Extractor/Refinery).
As a process F 60/100 · Will not run — References files that are not bundled: scripts/preflight.sh
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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-tokenscripts/package-lock.json:155High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…lB9+ogoo…IWq+UIzl…tXw==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:164High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…H0O+758r…IEX/WHlX…MIQ==",
detector
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5426 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: scripts/preflight.sh - note
frontmatter-keyunknown frontmatter key "meta_description"
Process rating: all ten parameters 60/100
- 0Tools and files. 1 referenced file(s) missing: scripts/preflight.sh
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 5426 tokens
- 100Steps. 45 steps
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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)
- +1No license
- +2Single-language instructions
- +3Description length 385: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 45 items
- +3Output format is stated explicitly
- +4Has examples (16 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.