agentleFS
Sign inStart free
OKHP3OKHP3/skillz/.agents/skills/publishing-trigger-check/SKILL.md

publishing-trigger-check

Skill3 starsChanged 2 months agoMITView on GitHub

Verify GitHub Pages publishing remains family-agnostic and fail-closed.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run after changing .github/workflows/deploy-pages.yml (the real path GitHub Actions executes) or family/skill folder conventions.

    line 10

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Publishing trigger check

Use when

Run after changing .github/workflows/deploy-pages.yml (the real path GitHub Actions executes) or family/skill folder conventions. It reuses the repository's existing verify-deploy-trigger.mjs.

Callable command

node .agents/skills/publishing-trigger-check/run.mjs

The check requires the workflow to contain a family-independent **/FAMILY.md or **/SKILL.md glob, rejects hardcoded current family names, and exits non-zero when the workflow is absent or unsafe. It never pushes, publishes, force-pushes, or handles tokens.

Companion-site release audit

From a network-enabled environment, run:

node .agents/skills/publishing-trigger-check/audit-sites.mjs --strict

This independently probes OverKill Hill, Glee-fully Tools, and AskJamie for home/about/legal/sitemap responses, canonical and OG metadata, OG image reachability, sitemap samples, CNAME alignment, workflow deploy handoff, and repository-vs-live freshness. Add --json for archival automation output.

--strict blocks when a repository has no proven deploy step; this currently identifies a site as blocked only when neither a repository deploy step nor a successful GitHub-managed Pages run can be proven. If GitHub manages the deployment outside repository YAML, the runner reports that limitation explicitly rather than silently treating validation as publishing. It does not infer or change DNS, repository settings, or deployment ownership.

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.

Check your setup, free