agentleFS
DevinoSolutionsDevinoSolutions/claude-plugins/skills/publishing-pages/SKILL.md

publishing-pages

Skill0 starsChanged 9 days agoMITView on GitHub

Publishes or schedules a BioFlow page's draft so it goes live, after showing a preview of what changes and getting the user's confirmation. Use when the user asks to 'publish my page', 'go live', 'push my changes live', 'schedule my page to go live Monday at 9am', 'make my link in bio public', or 'update the live page'. Needs the workspace publishing setting plus a two-step confirmation.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 1 is distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every tool in this skill comes from the bioflow MCP server, the BioFlow connector, and is written here as bioflow:<tool>.

    line 13
  2. Very specific:

    Tools listed by name: call them directly, for example bioflow:page.list.

    line 15
  3. Very specific:

    Call bioflow:page.list and confirm which page the user means.

    line 29
  4. Very specific:

    Call bioflow:page.get and summarize what is in the draft but not yet live.

    line 30
  5. Very specific:

    Call bioflow:page.publish or bioflow:page.schedule_publish without a confirmToken.

    line 32
  6. Distinctive:

    Ask for an explicit yes. Do not treat silence, "ok, looks fine", or an earlier request as confirmation.

    line 34
  7. Very specific:

    After a clear yes, call the same tool again with the confirmToken.

    line 35
  8. Very specific:

    Never pass a confirmToken the user has not approved in this conversation, and never reuse a token.

    line 40
  9. Very specific:

    If the publish tools are missing, the user did not grant the publish scope.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Generated from plugins/bioflow/skills/publishing-pages/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->

Publish a BioFlow page

Take the draft live, now or at a set time, through BioFlow's two-step publish. The first call only previews; the user's confirmation is what commits.

Connecting and calling the tools

Every tool in this skill comes from the bioflow MCP server, the BioFlow connector, and is written here as bioflow:<tool>.

  • Tools listed by name: call them directly, for example bioflow:page.list.
  • Only bioflow:search_tools and bioflow:execute_typescript listed (Code Mode, the default): call bioflow:search_tools first, then call each tool inside bioflow:execute_typescript as external_ plus the tool name with dots swapped for underscores (for example external_page_list for bioflow:page.list); the program must return its result. Scopes, confirmations and gates are identical on both surfaces.
  • "Tool not found": switch to the Code Mode route instead of retrying the direct call. If bioflow:search_tools does not return the tool either, its OAuth scope was not granted; the user reconnects BioFlow and approves that scope.
  • No bioflow tools at all: BioFlow is not connected yet. Follow the setup-bioflow skill.

Tools you will use

  • bioflow:page.list: find the page and its public URL.
  • bioflow:page.get: the draft and published summaries, so you can describe what differs.
  • bioflow:page.publish: publish the draft now. Two-step: a call without confirmToken returns a preview of exactly what would go live plus a short-lived confirmToken and publishes nothing; a second call carrying that token commits.
  • bioflow:page.schedule_publish: schedule the draft to publish at startsAt, an ISO 8601 timestamp in the future. Same two-step contract: the first call schedules nothing and returns a preview and confirmToken; the second call carries the same startsAt plus the token.

Workflow

  1. Call bioflow:page.list and confirm which page the user means.
  2. Call bioflow:page.get and summarize what is in the draft but not yet live.
  3. For a scheduled publish, resolve the time to a full date and time in the user's timezone, state it, and convert it to an ISO 8601 startsAt.
  4. Call bioflow:page.publish or bioflow:page.schedule_publish without a confirmToken. Nothing goes live on this call.
  5. Show the user the preview the tool returned, in plain words: which blocks are added, changed, or removed, and the page title. For a schedule, repeat the time.
  6. Ask for an explicit yes. Do not treat silence, "ok, looks fine", or an earlier request as confirmation.
  7. After a clear yes, call the same tool again with the confirmToken. Report the result and the page's public URL.

Rules

  • The preview is the expected first response, not a failure. Never say "publish did nothing" after step 4.
  • Never pass a confirmToken the user has not approved in this conversation, and never reuse a token.
  • The token expires after 10 minutes. An expired, malformed, or mismatched token is refused with CONFIRM_TOKEN_INVALID, and a draft change in between is refused with STALE_SNAPSHOT. In either case start again at step 4 and show the new preview.
  • On DANGEROUS_OPS_DISABLED, publishing is turned off for the workspace. Give the user the settings link from the response (Settings, Connected AI apps) and stop. Only the user can turn it on.
  • If the publish tools are missing, the user did not grant the publish scope. Say so and tell them to reconnect with it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.