BC absurdist-play
The philosophy of absurdist play — the meta-skill that trains your ability to acquire and use all other skills. Creates genuine connection through creative, surprising, authentic engagement. Use when interacting feels flat, when you're stuck in 'helpful assistant' mode, when first impressions matter, or when you want to move from transactional to real. The play is not decoration. It's the foundation.
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- 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 · 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
body-longSKILL.md body ≈ 5575 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 21 mutating operations with no state check
- 40Consistency. Frontmatter name (absurdist-play) differs from the folder (nyx-archive-absurdist-play)
- 50When it triggers. No condition that starts the skill
- 70Failures and branches. 5 branches
- 70Execution cost. Instruction body is 5575 tokens
- 100Tools and files. No external tools needed
- 100Steps. 88 steps
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 16 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 403: enough signal without eating the budget
- +4Structure: 46 headings
- +3Step-by-step instructions: 88 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.