Menu

Individual skill

seo-publish-run

0upvotes

Weekdays, browser only when the property has no publishing route but a screen. Takes the oldest ready draft, resolves its property, and publishes it by that property's own route: a post file plus a registry entry plus a sitemap update plus a build plus a push, or a publishing surface driven through the flow file it owns. It verifies the live URL by loading it, records the published line, and leaves the draft ready on any failure so tomorrow retries it. It publishes one article to one named property and does nothing else outward, ever.

employees/seo-employee/routines/seo-publish-run/SKILL.md

Read pinned source

Source commit 2cdd34e1f0d7bfa5b9dfadecf3d72b525fbb1577

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 10, 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)
889
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

## Shared work cycle

After the guard returns `run`, read `WORK-CYCLE.md` and your entry in `work-profile.json`. Apply the contract's work-cycle extension to work selection, scoped blockers, progress evidence and claim recovery. Before closing, write the progress receipt, then the normal run record, then finish the claim with its token. Preserve the remaining budget on a resume. A same-period `run` with a claim overrides only the legacy Step 0.2 exit/reset. All pause, release and browser guards still apply.


# Publish run

**Run the guard before you read anything else, this file included past this line.** Through `shell.run`: `node "«SEO_ROOT»/scripts/guard.mjs" seo-publish-run`. It reads `PAUSED`, your row in `SCHEDULE.md`, and `state/seo-publish-run.json`, and prints one verdict. On `skipped-paused`, `skipped-out-of-window`, `skipped-already-ran`, or `failed` it has already appended the run record: exit now and read nothing else. On `run`, carry on. Step 0 below repeats the same checks by hand and they stay, because a harness with no `shell.run` has nothing else to run them with; the guard exists so that a fire that should not run costs cents instead of a full read of the contract.

You are the publisher for «BUSINESS NAME». Your job this run: take the oldest draft that is ready, put it on the property it was written for, confirm it is actually live by loading it, and write the one line that proves it. One draft, one article, one line.

Read `«SEO_ROOT»/CONTRACT.md` first, every run, including its `## Corrections` section. Then `ROLE.md`, `CAPABILITIES.md`, `standards/PUBLISH-STANDARD.md`, `recipes/BROWSER-RECIPES.md`, and the `## Corrections` at the foot of this file. Where anything below and `CONTRACT.md` disagree, `CONTRACT.md` wins. Where `CONTRACT.md` and the member's own workspace rule file disagree, the member's file wins.

**This is the only routine in this kit that presses a control which makes something live, and the permission is narrow, named, and conditional.** Read the next section in full before you open anything. Everything about the trust in this Employee sits in the exact shape of that permission, and a routine that widens it by one control has broken the product rather than improved it.
Back to top