Borrowing it
Nothing to install: this file belongs to Orinks/AccessiWeather. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Orinks/AccessiWeather/main/.claude/skills/writing-changelog-entries/SKILL.mdgit clone --depth 1 https://github.com/Orinks/AccessiWeatherWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/orinks/accessiweather/writing-changelog-entries)<a href="https://agentmods.dev/skills/orinks/accessiweather/writing-changelog-entries"><img src="https://agentmods.dev/badge/skills/orinks/accessiweather/writing-changelog-entries/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/orinks/accessiweather/writing-changelog-entries"><img src="https://agentmods.dev/badge/skills/orinks/accessiweather/writing-changelog-entries.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.00580 |
| Opus 5.5 | $0.00013 | $0.00232 |
| Sonnet 5.5 | $0.00007 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
writing-changelog-entries scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing changelog entries
Overview
A changelog bullet is one change, stated once, in the words a user would use to look for it. Release notes are built from these bullets, read aloud by screen readers, and shown on orinks.net and GitHub, so every extra sentence is one the reader has to sit through to reach the next change.
The entry
An entry is one sentence, in plain present tense, saying what is different now. Direct address is welcome ("You can now..."), contractions are fine, and the sentence must stand on its own without the section heading. A second sentence is allowed only for a setting name or a platform limit the reader needs ("Windows only", "Rebind it on the General tab in Settings").
Length: under 25 words. 40 is the ceiling. Count them.
Example, and this is the entire entry:
- NWS lookups now follow coordinate-precision redirects instead of falling back to another weather source.
Where the rest goes
| Material | Goes to |
|---|---|
| Root cause, why it happened, what the old code did | the commit message |
| How it works, what it reads, sample sizes, thresholds | the PR body |
| Every sub-case, every affected distro or dialog | docs/user_manual.md, or its own bullet if a user would search for it on its own |
| The before-and-after story | nowhere; the sentence says what is different |
| Reassurance that something else is unchanged | nowhere |
| Developer-facing changes (CI, tests, tooling, refactors) | no bullet; [skip changelog] in the commit |
Checklist before saving
- One sentence, or one plus a short limit or setting name.
- Under 25 words, 40 at most.
- Names the setting, tab, button, or key the reader will look for; never a file, function, or API field.
- Section is one of Added, Changed, Fixed, Improved, Removed, Deprecated, Security. Any other heading is dropped from release notes.
- No symbols, tables, code formatting, or em dashes: it is read aloud.
Common mistakes
- Telling the story of the bug before the fix. Say what happens now.
- A parenthetical that repeats the sentence in more detail.
- One bullet carrying a whole feature's sub-parts. Split by what a user would look up, and send the rest to the manual.
- Editing an old bullet to satisfy the changelog gate. The gate needs a new bullet.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 59 lines · 33 tokens per session scan A 45b04987521f
writing-changelog-entries is a skill published in the GitHub repository Orinks/AccessiWeather (24 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 580 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-15.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.