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.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

83%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, token-efficient reference with executable commands and clear sections. The main weakness is the onboarding workflow's lack of explicit validation/verification steps for irreversible federation operations.

Suggestions

Add an explicit verification step to the onboarding workflow (e.g., 'after NIP-42 auth, confirm the node appears in `federation roster` before declaring onboarding complete').

Insert a validate-then-proceed checkpoint before admin-gated, hard-to-reverse operations (admit, grant, publish) since the skill notes there is no revocation path.

Consider moving the full CLI command reference into a references/ file and keeping SKILL.md as a concise overview, which would tighten progressive disclosure toward a 5.

Dimension	Reasoning	Score
Conciseness	The body is dense and lean — it references Nostr/NIP-98/NIP-42/NIP-44/ECDH/secp256k1 without explaining them, assuming Claude's competence, and nearly every line carries concrete commands, rules, or caveats.	5 / 5
Actionability	It provides copy-paste-ready CLI commands with flags ('npx ruflo federation sync [--since 3600] [--limit 100] [--type Task]') and MCP tool signatures with parameters, covering the common cases.	5 / 5
Workflow Clarity	The onboarding section is a clear 3-step sequence, but it lacks explicit validation checkpoints for hard-to-reverse operations (admit/grant/publish — the skill itself warns 'there is no revocation'), capping it at 3.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections (CLI, MCP tools, Channels, Seraphina, Rules, Onboarding) in a single file with no external references, though the body slightly exceeds 50 lines and some inline reference material could live in a separate file.	4 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete capabilities, an explicit and broad trigger list, a clear skip clause, and a highly distinctive niche. The only minor gap is the absence of synonym/extension-style trigger variants.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'reading/assigning work', 'checking or issuing claims across hosts', 'onboarding a new node or user', 'opening a public or private coordination channel' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	It explicitly answers both 'what' ('Coordinate with the open ruflo swarm federation… ask Seraphina… for guidance') and 'when' (a concrete 'Use when:' trigger list plus a 'Skip when:' clause).	5 / 5
Trigger Term Quality	Natural user-facing phrases like 'seeing who is online across the internet', 'reading/assigning work', and 'onboarding a new node or user' provide good keyword coverage, though there are few synonym variants and no file-extension-style triggers.	4 / 5
Distinctiveness Conflict Risk	'Coordinate with the open ruflo swarm federation at x.ruv.io (signed Nostr, membership-gated)' names a clear, narrow niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: ruvnet/ruflo
Path: .agents/skills/open-federation/SKILL.md
Commit: b14c79e

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.