BC open-federation
Coordinate with the open ruflo swarm federation at x.ruv.io (signed Nostr, membership-gated) and ask Seraphina — the swarm queen / primary coordinator — for guidance. Use when: seeing who is online across the internet, reading/assigning work, checking or issuing claims across hosts, onboarding a new node or user, opening a public or private coordination channel, or deciding what the swarm should do next. Skip when: single-host local work with no other nodes.
Promises coordination with federated Nostr swarm at x.ruv.io: check who's online, distribute work, verify claims across hosts, onboard nodes, manage channels. One instruction file at 1250 tokens, no scripts. Grade B shows quality 84% but process 54% — likely incomplete docs or unclear logic. No critical errors, linter passes, sandbox didn't run.
Requires x.ruv.io access and Nostr signing; not a local tool. Install if you run distributed nodes and trust external coordination; skip for single-host setups.
Coordinate with the open ruflo swarm federation at x.ruv.io (signed Nostr, membership-gated) and ask Seraphina — the swarm queen / primary coordinator — for…
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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 · 0
✓ No critical or high findings
Files scanned: 1. 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 54/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
- 30Running it twice. 6 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 17 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1250 tokens
- high The skill tells the model to perform an irreversible action with no human approval
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 462: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.