product-update-logger
Tell the skill what your product shipped. It writes a polished dated entry to a living docs/changelog.md and produces a ready-to-use content package: tweet thread, LinkedIn post, email snippet, and one-liner.
npx skills add Varnan-Tech/opendirectory --skill product-update-logger --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# product-update-logger Tell this skill what your product shipped. It writes a polished changelog entry to `docs/changelog.md` (a living log, newest entry first) and simultaneously produces a content package: tweet thread, LinkedIn post, email snippet, and one-liner. Input sources: free text from your message, git commits auto-read from the local repo, or GitHub PRs if you provide a repo. Any combination works. ## Reference Files Read these files before each run: ```bash cat references/changelog-format.md cat references/content-rules.md cat references/noise-filter.md ``` --- ## Step 1: Setup Check ```bash echo "GITHUB_TOKEN: ${GITHUB_TOKEN:-not set -- GitHub PR fetching disabled}" echo "Git: $(git rev-parse --is-inside-work-tree 2>/dev/null && echo 'repo detected' || echo 'not a git repo')" echo "Changelog: $(ls docs/changelog.md 2>/dev/null && echo 'exists' || echo 'will be created')" ``` Note whether git is available and whether a changelog already exists. This determines the version label format. --- ## Step 2: Parse Input Collect from the conversation: - `items` -- free text description of what shipped (pipe-separated if multiple). Optional if git is available. - `since` -- how
- Reference Files
- Step 1: Setup Check
- Step 2: Parse Input
- Step 3: Run the Gather Script
- Step 4: Generate Changelog Entry
- Step 5: Generate Content Package
- Step 6: Self-QA
- Step 7: Append to Changelog + Save Content
- Step 8: Clean Up and Present
- Common Mistakes
cat references/changelog-format.md
cat references/content-rules.md
cat references/noise-filter.md
echo "GITHUB_TOKEN: ${GITHUB_TOKEN:-not set -- GitHub PR fetching disabled}"
echo "Git: $(git rev-parse --is-inside-work-tree 2>/dev/null && echo 'repo detected' || echo 'not a git repo')"
echo "Changelog: $(ls docs/changelog.md 2>/dev/null && echo 'exists' || echo 'will be created')"
python3 << 'PYEOF'
ls scripts/gather.py 2>/dev/null && echo "script found" || echo "ERROR: scripts/gather.py not found"
python3 -c "
import jsonWhat does the product-update-logger skill do?
Tell the skill what your product shipped. It writes a polished dated entry to a living docs/changelog.md and produces a ready-to-use content package: tweet thread, LinkedIn post, email snippet, and one-liner.
How do I install it?
Run `npx skills add Varnan-Tech/opendirectory --skill product-update-logger --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Varnan-Tech/opendirectory, a repository with 571 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.