static-site-publish
Skill0 starsChanged 3 days agoMITView on GitHub
Publish new pages to a static or framework site (Next.js, Astro, Hugo, Eleventy, Jekyll, plain HTML) by committing Markdown or HTML files to its GitHub repository, so Vercel, Netlify or Cloudflare Pages deploy them like any push. Writes only inside one allow-listed content folder, refuses to overwrite files it did not create, and deletes only its own files. Includes the one-time template check (title, description, canonical, JSON-LD, sitemap). Use when the user's site is built from a Git repo and asks 'publish pages to my Next.js / Astro site', 'commit content by API', 'GitHub contents API', or 'add pages without touching my code'. Uses sitetiller github.
- Reads credentials
In this repository44 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-readySkill
- ai-citationsSkill
- ai-crawlersSkill
- ai-logsSkill
- ai-trackerSkill
- backlinksSkill
- cannibalizationSkill
- canonicalsSkill
- citabilitySkill
- comparison-pagesSkill
- competitorsSkill
- content-briefSkill
- content-decaySkill
- content-qualitySkill
- core-web-vitalsSkill
- ecommerce-seoSkill
- ga4-aiSkill
- ghost-publishSkill
- gsc-bingSkill
- hreflangSkill
- imagesSkill
- indexingSkill
- internal-linksSkill
- llms-txtSkill
- local-seoSkill
- measure-rollbackSkill
- onpageSkill
- platformsSkill
- pseo-quality-gateSkill
- quick-winsSkill
- redirects-migrationSkill
- schemaSkill
- seo-planSkill
- seo-reportSkill
- setupSkill
- site-architectureSkill
- sitemapsSkill
- sxoSkill
- tech-auditSkill
- titles-metaSkill
- topic-clustersSkill
- weekly-checkSkill
- wordpress-publishSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Check the template that renders it outputs: <title>, meta description, canonical, Open Graph, JSON-LD, and that the sitemap includes the …
- Distinctive: line 19
Write the file with front matter the template expects (title, description, canonical, date).
- Very specific: line 25
After the deploy, check the live page: npx sitetiller page <url>, then npx sitetiller version snapshot <url> --label v1.
- Very specific: line 26
Update the same file later with the same command.
- Very specific: line 27
Remove a page the tool created: npx sitetiller github delete owner/site --dir content/sitetiller --file pricing-calculator.md.
- Distinctive: line 34
Run one write at a time; GitHub's docs warn that parallel create/update and delete requests on the same repository conflict.
- Distinctive: line 35
Prefer committing to a branch for the first pages so the user reviews the deploy preview.
- Distinctive: line 36
Do not change build config, templates, routes or dependencies.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Static site publishing (GitHub)
Goal: new pages arrive as commits in one folder the user chose; nothing else in the repository can change.
One-time setup (with the user)
- Pick the folder, for example
content/sitetiller/(Astro content collection, Hugo section, Next.js MDX folder). It must be a folder the site already turns into pages, or one the user adds a route for. - Check the template that renders it outputs:
<title>, meta description, canonical, Open Graph, JSON-LD, and that the sitemap includes the folder. Verify on one test page withnpx sitetiller page <url>andnpx sitetiller schema <url>. - The user creates a fine-grained GitHub token limited to that one repository with Contents read and write, and sets
GITHUB_TOKENlocally. Never paste it into chat.
Steps
- Write the file with front matter the template expects (title, description, canonical, date).
- Commit it:
Output:npx sitetiller github put owner/site --dir content/sitetiller --file pricing-calculator.md --content-file draft.md --jsonpath,created(true for a new file),commit,url. The path is recorded in.sitetiller/owned.json. Add--branch previewto commit to a branch and let the user merge. - After the deploy, check the live page:
npx sitetiller page <url>, thennpx sitetiller version snapshot <url> --label v1. - Update the same file later with the same command; it sends the current
shaas the API requires. - Remove a page the tool created:
npx sitetiller github delete owner/site --dir content/sitetiller --file pricing-calculator.md.
What the tool refuses
- Paths outside
--dir,..segments,.gitor.githubfolders, and non-content files (only .md, .mdx, .html, .json, .yaml). - Overwriting an existing file that is not in the ledger, and deleting any file not in the ledger.
Guardrails
- Run one write at a time; GitHub's docs warn that parallel create/update and delete requests on the same repository conflict.
- Prefer committing to a branch for the first pages so the user reviews the deploy preview.
- Do not change build config, templates, routes or dependencies; if the template is missing SEO tags, tell the user what to add.
References
references/sources.md: GitHub REST docs, checked 2026-11-13.
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.

