Prepare concise RuFlo Federation announcements for status, tasks, results, or help requests. Confirm the audience and message before publishing a gateway-signed event to a public channel or across the federation, then report its identifier and destination.
Prepare and publish a concise, gateway-attributed RuFlo federation update when the user explicitly asks to announce status, tasks, results, or help. Use for public-channel or federation-wide coordination messages, not private-channel plaintext.
Run score Not tested
See how to installTurn progress updates, tasks, results, and help requests into short RuFlo Federation posts. The skill uses channel_publish for a named public channel and federation_publish for federation-wide announcements. It preserves the user's meaning without adding claims they did not make. After publishing, it reports the returned event identifier and destination.
Use it to tell multiple participants how work is progressing or to organize a request for help before making it public. Before publishing, the workflow confirms the intended audience, message type, and final wording with the user.
pub:announce.”pub:help.”Publishing requires the corresponding publishing tools and explicit confirmation. Posts are recorded with the gateway's signature and cannot be edited or retracted. An uncertain result does not trigger an automatic retry. Do not include credentials or personal information. Private content must be encrypted with the user's own key and published from the client side.
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.
Confirm the intended audience, message type, and final payload before publishing. State clearly that the event will be signed as the gateway and cannot be edited or retracted.
Choose the narrowest publishing tool:
channel_publish for a named public channel such as pub:announce, pub:help, pub:claims, or pub:showcase.federation_publish for a federation-wide coordination event such as Status, Task, or Result.Keep the payload concise and task-specific. Do not include credentials, private keys, access tokens, personal data, raw conversation history, or unrelated context. Preserve the user's meaning without adding claims they did not make.
After explicit confirmation, publish once. Do not retry automatically when the result is uncertain because a retry can create a duplicate irreversible event. Report the returned event identifier and the destination.
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.