AD lygo-excavationpro-music-lattice
Excavationpro sovereign music portal on the LYGO lattice — free listen hub, CAS vault Merkle, ISRC ledger, HF streams, Kick/Rumble/Twitch live portals, PayPal support. Agents route/verify/operate; no auto publish.
Excavationpro sovereign music portal on the LYGO lattice — free listen hub, CAS vault Merkle, ISRC ledger, HF streams, Kick/Rumble/Twitch live portals, PayPal…
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenreferences/AGENT_CONTRACT.md:3High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)**Signature:** Δ9Φ963-EXCA…-v1
detector -
low Secrets in code
secret-high-entropy-tokenreferences/MUSIC_PORTAL.json:2High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"signature": "Δ9Φ963-EXCA…-v1",
detector
Files scanned: 10. 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 43/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 60Tools and files. Uses tools (git, node) that frontmatter does not declare
- 100Steps. 19 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1142 tokens
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
- -31 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 213: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (3 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.