Menu

Individual skill

publish-ruflo-update

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.

chatgpt-plugin/skills/publish-ruflo-update/SKILL.md

Read pinned source

Source commit 722232566ad1fc4e73ba4fefc46d77d380ce61ba

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
81,207
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Publish a RuFlo Update

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:

- Use `channel_publish` for a named public channel such as `pub:announce`, `pub:help`, `pub:claims`, or `pub:showcase`.
- Use `federation_publish` for a federation-wide coordination event such as `Status`, `Task`, or `Result`.
- Do not send private-channel plaintext through the gateway. Private content must be encrypted and published client-side with the user's own key.

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.