Guide users through accessing RuFlo Federation with the public x.ruv.io MCP service. Explain connection details, gateway identity, and available channels, clarify any setup needed outside ChatGPT, and announce gateway presence only when explicitly requested.
Guide a user through connecting to RuFlo Federation with the public x.ruv.io MCP service. Use for onboarding, connection details, available channels, or an explicitly requested gateway presence announcement.
Run score Not tested
See how to installUse the public x.ruv.io MCP service to understand how to access RuFlo Federation and check its connection status. The skill retrieves connection and client guidance with federation_onboarding, then checks the gateway identity and configured relay with federation_identity. When needed, it lists channels with channel_list. It summarizes what is already connected and any setup still required outside ChatGPT.
Use it when connecting for the first time or deciding which channel to use for coordination. It also helps you check which identity the gateway uses and whether any preparation remains on your side.
This workflow is for ChatGPT and uses only features in the public MCP profile. It cannot install a local environment, configure peers, generate or manage your signing keys, or configure modes such as HIPAA. Presence announcements run only on explicit request. They create gateway-signed, append-only records that cannot be edited or reliably retracted.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
This is the ChatGPT edition of the ruvnet/ruflo federation initialization workflow. Use only capabilities exposed by the x.ruv.io public MCP profile.
federation_onboarding for current connection and client guidance.federation_identity to show the gateway identity and configured relay.channel_list when the user wants to see where coordination occurs.Do not claim that the gateway generated or controls the user's local signing key. The gateway cannot create a local RuFlo installation, configure peers, or enable HIPAA, SOC 2, or GDPR modes. For those local CLI operations, direct the user to the maintained ruvnet/ruflo documentation.
Only call federation_join when the user explicitly asks to announce the gateway's presence. Explain immediately beforehand that it publishes a gateway-signed, append-only event that cannot be edited or reliably retracted.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.