auto-gist-publisherlisted
Install: claude install-skill karozi/awesome-product-management-skills
# Auto Gist Publisher
## Purpose
For every new skill directory added under `skills/<category>/<slug>/` with a valid `SKILL.md`, publish one public gist to the repo owner's GitHub account. Each gist is header-only and links back to the skill folder on GitHub.
## Gist format
```
Skill #<N> of <TOTAL> in awesome-product-management-skills
<Display Name>
<AIO/GEO-optimized description — 1 to 3 sentences, plain language, keyword-rich>
Read the full skill: https://github.com/karozi/awesome-product-management-skills/tree/main/skills/<category>/<slug>
See more AI PM resources at https://karozieminski.substack.com/?utm_source=github-gist&utm_medium=referral&utm_campaign=amps-skills&utm_content=<slug>
```
- `<N>` is the alphabetical rank of the new skill among all skills in the repo after the push.
- `<TOTAL>` is the total skill count in the repo after the push.
- The Substack CTA carries per-skill UTM attribution (`utm_source=github-gist`, `utm_medium=referral`, `utm_campaign=amps-skills`, `utm_content=<slug>`) so gist-driven traffic is measurable per skill in GA4.
- Filename in the gist is `<slug>.md`; gist description is `Skill #<N>: <Display Name> — awesome-product-management-skills`.
## When it runs
Automatically via `.github/workflows/auto-gist-publisher.yml` on every push to `main` that touches `skills/**/SKILL.md`. Also runs on `workflow_dispatch` for backfills.
## How it detects new skills
Idempotent by design. `state/published.json` (committed to the repo) maps `c