shopify-seo-publish
Skill0 starsChanged 2 months agoMITView on GitHub
Publish approved copy to a live Shopify store through the Shopify MCP, behind an explicit approval gate. Use for: publish this, update the product, put it live, push to Shopify, post the blog.
In this repository7 other files it gives its agents.
- shopify-seo-brandSkill
- shopify-seo-checkSkill
- shopify-seo-fixSkill
- shopify-seo-geoSkill
- shopify-seo-learnSkill
- shopify-seo-schemaSkill
- shopify-seoSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Not a JSON patch. "The description gains a sentence about the lead time" is a diff.
- Distinctive: line 20
If any of those is missing, stop and ask.
- Distinctive: line 25
Read the product first. Never write from the draft alone.
- Distinctive: line 27
Prefer one product at a time.
- Distinctive: line 33
Never publish on a schedule, a loop, or an implied yes.
- Distinctive: line 34
Never delete a product, variant, image or page.
- Distinctive: line 35
Never change price, inventory or status.
- Distinctive: line 36
Never touch a second store.
≈ “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
Publish
This writes to a live shop. Treat every call as though the owner is watching, because they should be.
The gate
A publish requires all of the following. No exceptions, and no inferring consent from enthusiasm.
- The copy has passed
/shopify-seo check, or the owner has explicitly accepted the remaining findings. - The owner has seen a plain-English diff of what changes on which product or page. Not a JSON patch. "The description gains a sentence about the lead time" is a diff. A blob is not.
- The owner has said yes in this conversation, after seeing that diff.
- You are changing only what they named. One product means one product.
If any of those is missing, stop and ask. Handing back text to paste is always an acceptable outcome and is often the better one.
How to write
- Read the product first. Never write from the draft alone.
- Change only the fields named. Leave everything else exactly as found.
- Prefer one product at a time. If asked for a batch, show the full list and get approval for the list, then report each result as it lands.
- Report the outcome per item, including failures. Never summarise a partial success as a success.
Never
- Never publish on a schedule, a loop, or an implied yes.
- Never delete a product, variant, image or page. Unpublishing is reversible, deletion is not.
- Never change price, inventory or status. This skill writes copy and metadata only.
- Never touch a second store. Confirm the shop domain before the first write of a session.
After
Give the live URL and a one-line summary of what changed, so the owner can look at it themselves.
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.

