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.
In this repository66 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adding-uptime-monitorsSkill
- analyzing-page-performanceSkill
- booking-meetingsSkill
- building-onboarding-workflowsSkill
- building-study-guidesSkill
- capturing-tasksSkill
- capturing-web-pagesSkill
- chasing-unpaid-invoicesSkill
- checking-domain-connectionsSkill
- checking-email-deliverabilitySkill
- checking-notification-deliverySkill
- checking-uptime-statusSkill
- cleaning-up-bookkeepingSkill
- connecting-customer-domainsSkill
- discussing-buildsSkill
- drafting-invoicesSkill
- drafting-social-postsSkill
- editing-demosSkill
- editing-page-draftsSkill
- extracting-document-textSkill
- finding-meeting-timesSkill
- handling-flaky-changesSkill
- investigating-tasksSkill
- making-demo-videosSkill
- managing-bookingsSkill
- managing-content-calendarSkill
- managing-demosSkill
- managing-voice-librarySkill
- planning-revisionSkill
- preflighting-domainsSkill
- reading-financial-reportsSkill
- reading-text-aloudSkill
- reading-web-pagesSkill
- reporting-snapvisor-usageSkill
- researching-course-materialSkill
- researching-summary-librarySkill
- responding-to-incidentsSkill
- reviewing-email-performanceSkill
- reviewing-notification-workflowsSkill
- reviewing-social-performanceSkill
- reviewing-visual-buildsSkill
- reviewing-workloadSkill
- searching-getitdone-api-docsSkill
- sending-email-campaignsSkill
- sending-notificationsSkill
- setup-bioflowSkill
- setup-calySkill
- setup-demofySkill
- setup-dodomainSkill
- setup-getitdoneSkill
- setup-notiflySkill
- setup-postifySkill
- setup-sendlySkill
- setup-shortySkill
- setup-snapvisorSkill
- setup-superbooksSkill
- setup-unotesSkill
- setup-upapiSkill
- setup-uptimelySkill
- The first 60 shown.
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
- Very specific: line 13
Every tool in this skill comes from the bioflow MCP server, the BioFlow connector, and is written here as bioflow:<tool>.
- Very specific: line 15
Tools listed by name: call them directly, for example bioflow:page.list.
- Very specific: line 29
Call bioflow:page.list and confirm which page the user means.
- Very specific: line 30
Call bioflow:page.get and summarize what is in the draft but not yet live.
- Very specific: line 32
Call bioflow:page.publish or bioflow:page.schedule_publish without a confirmToken.
- Distinctive: line 34
Ask for an explicit yes. Do not treat silence, "ok, looks fine", or an earlier request as confirmation.
- Very specific: line 35
After a clear yes, call the same tool again with the confirmToken.
- Very specific: line 40
Never pass a confirmToken the user has not approved in this conversation, and never reuse a token.
- Very specific: line 43
If the publish tools are missing, the user did not grant the publish scope.
≈ “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.
Files
<!-- 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_toolsandbioflow:execute_typescriptlisted (Code Mode, the default): callbioflow:search_toolsfirst, then call each tool insidebioflow:execute_typescriptasexternal_plus the tool name with dots swapped for underscores (for exampleexternal_page_listforbioflow:page.list); the program mustreturnits 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_toolsdoes not return the tool either, its OAuth scope was not granted; the user reconnects BioFlow and approves that scope. - No
bioflowtools at all: BioFlow is not connected yet. Follow thesetup-bioflowskill.
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 withoutconfirmTokenreturns a preview of exactly what would go live plus a short-livedconfirmTokenand publishes nothing; a second call carrying that token commits.bioflow:page.schedule_publish: schedule the draft to publish atstartsAt, an ISO 8601 timestamp in the future. Same two-step contract: the first call schedules nothing and returns a preview andconfirmToken; the second call carries the samestartsAtplus the token.
Workflow
- Call
bioflow:page.listand confirm which page the user means. - Call
bioflow:page.getand summarize what is in the draft but not yet live. - 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. - Call
bioflow:page.publishorbioflow:page.schedule_publishwithout aconfirmToken. Nothing goes live on this call. - 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.
- Ask for an explicit yes. Do not treat silence, "ok, looks fine", or an earlier request as confirmation.
- 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
confirmTokenthe 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 withSTALE_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
publishscope. Say so and tell them to reconnect with it.
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
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.

