agentleFS
DevinoSolutionsDevinoSolutions/claude-plugins/skills/editing-page-drafts/SKILL.md

editing-page-drafts

Skill0 starsChanged 9 days agoMITView on GitHub

Edits the draft of a BioFlow link-in-bio page: adds, changes, removes, or reorders links, images, products, newsletter signups, booking embeds, and other blocks, renames a page, or creates a new page. Use when the user asks to 'add a link to my YouTube channel', 'update my bio link page', 'rename my page title', 'move the newsletter block to the top', 'remove this link', 'create a new link in bio page', or edit their creator landing page. Changes the draft only; never publishes.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 3 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    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. If the account has more than one page and the user did not name one, ask which.

    line 32
  4. Very specific:

    Call bioflow:page.get and show the current block order in one short list so the user can refer to blocks by position or name.

    line 33
  5. Very specific:

    Call bioflow:page.get again right before each write and pass its fresh expectedUpdatedAt.

    line 35
  6. Distinctive:

    After each write, report what changed in the draft and the new block id where one was returned.

    line 36
  7. Very specific:

    When the user is done, say the changes are in the draft only and offer the publishing-pages skill.

    line 37
  8. Very specific:

    Never call bioflow:page.publish or bioflow:page.schedule_publish from this skill.

    line 41
  9. Distinctive:

    Do not invent URLs, product details, or handles.

    line 43
  10. Distinctive:

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

    line 45

≈ “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/editing-page-drafts/SKILL.md by scripts/sync-skills.mjs. Edit the plugin copy, then run the script. -->

Edit a BioFlow page draft

Make the user's page changes on the draft. The live page does not change until the user publishes through the publishing-pages skill.

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: the account's pages with slug, public URL, and publish status.
  • bioflow:page.get: one page's draft and published summaries, the ordered block list, and the expectedUpdatedAt snapshot token every write needs.
  • bioflow:page.create: create a new page.
  • bioflow:page.update_draft: change page-level fields on the draft, such as the title.
  • bioflow:page.add_block: append a block to the draft. Returns the new block id.
  • bioflow:page.remove_block: remove named blocks from the draft. It refuses full-page clears.
  • bioflow:page.reorder_blocks: change the order of the draft's blocks.

Workflow

  1. Call bioflow:page.list. If the account has more than one page and the user did not name one, ask which.
  2. Call bioflow:page.get and show the current block order in one short list so the user can refer to blocks by position or name.
  3. Restate the change in one line ("Add a link block 'YouTube' to https://youtube.com/@name at the end"). For bioflow:page.remove_block and bioflow:page.update_draft, which delete or overwrite draft content, wait for the user's explicit yes before the write.
  4. Call bioflow:page.get again right before each write and pass its fresh expectedUpdatedAt. Then call the write tool.
  5. After each write, report what changed in the draft and the new block id where one was returned.
  6. When the user is done, say the changes are in the draft only and offer the publishing-pages skill.

Rules

  • Never call bioflow:page.publish or bioflow:page.schedule_publish from this skill.
  • On STALE_SNAPSHOT, nothing was written. Call bioflow:page.get, show the user what changed, and repeat the write only if it still makes sense.
  • Do not invent URLs, product details, or handles. Ask for the link when a block needs one.
  • To empty a page, remove blocks by name one at a time after the user confirms the list. There is no clear-all operation.
  • If the write tools are missing, the user did not grant the page write 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.