What problem does it solve? Work leaving a machine publicly — a repo going public, a release, a plugin-directory submission — often ships with stale README claims, outdated screenshots, missing install instructions, or leaked secrets. This Skill gates every publication against a checklist keyed to the artifact's kind so the public surface matches what actually shipped. ## Core Features & Use Cases - Kind-based checklists: Enforces what each artifact type owes its reader — skills show install lines and typed commands, tools show a real run with real output, visual products show freshly re-shot screenshots, prose shows its reading path. - Shopfront walk on every version push: Re-reads README claims (behaviour, counts, commands, versions) against the pushed truth and fixes stale claims before the push. - Target-specific steps: Adds per-target requirements for GitHub repos (fresh-clone check, release notes, name-collision checks), plugin directories (manifest validation, listing register), and design projects. - Safety sweeps: Scans tree and history for secrets, personal data, and non-shareable fixtures; enforces impersonal language in shipped docs via guardrail scripts. - Use Case: Before pushing a new version of your CLI tool to GitHub, run the publish walk to catch a README still showing the old version's command syntax, re-shoot a changed screenshot, and verify a fresh clone installs cleanly. ## Quick Start Ask the agent to run the publish checklist on this repository before pushing the new release publicly.
