How do I install the Publishing Trigger Check skill?

Run npx skillmds@latest add okhp3/publishing-trigger-check in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Publishing Trigger Check skill do?

Verify GitHub Pages publishing remains family-agnostic and fail-closed. It is listed under Coding & Dev Tools on SkillMD.

Is Publishing Trigger Check safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Publishing Trigger Check?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Publishing Trigger Check free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Publishing Trigger Check?

OKHP3 (@okhp3) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Publishing Trigger Check by okhp3 — Agent Skill

Name: Publishing Trigger Check
Author: OKHP3

File contents

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.

Frequently asked questions

Publishing Trigger Check