AF phasonic-flipper
Phason state resolution skill for Reson8-Labs. Use when the system encounters a split-brain state, HTTP 408 timeout deadlock, push/flip paradox, or coherence density spike. The Phasonic Flipper resolves state without re-transmission by applying a "Flip" — a quasicrystal phason field correction that restores the topological knot sequence. Triggers on: "split brain", "408 timeout", "deadlock", "density spike", "phason", "flip state", "push conflict", "Knot 16", "resolve", "state conflict", "HTTP 408", or any mention of transmission failure in POP.
As a process F 40/100 · Will not run — References files that are not bundled: references/protocol-spec.md
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/protocol-spec.md
Process rating: all ten parameters 40/100
- 0Tools and files. 1 referenced file(s) missing: references/protocol-spec.md
- 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. 9 mutating operations with no state check
- 40Consistency. Frontmatter name (phasonic-flipper) differs from the folder (phason-flipper)
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 100Steps. 7 steps
- 100Execution cost. Instruction body is 1053 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
- +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
- +5Description quotes 11 example trigger phrases
- +3Description length 551: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.