Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add nthnclrk/enablement-skills --skill release-notes-to-seller-updatesgit clone --depth 1 https://github.com/nthnclrk/enablement-skillsWrote 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/nthnclrk/enablement-skills/release-notes-to-seller-updates)<a href="https://agentmods.dev/skills/nthnclrk/enablement-skills/release-notes-to-seller-updates"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/release-notes-to-seller-updates/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/nthnclrk/enablement-skills/release-notes-to-seller-updates"><img src="https://agentmods.dev/badge/skills/nthnclrk/enablement-skills/release-notes-to-seller-updates.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.00080 | $0.00905 |
| Opus 5 | $0.00040 | $0.00452 |
| Sonnet 5 | $0.00016 | $0.00181 |
| Haiku 4.5 | $0.00008 | $0.00090 |
Grade A, and why
release-notes-to-seller-updates 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 12d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release notes to seller updates
Turn a release note into a field-usable update for the channel that will carry it. If it reads like a launch plan, rewrite it.
A seller update is one change, one audience, one next action. Training plans, go/no-go ledgers, and owner matrices belong in product-launch-enablement.
Field-usable. "From 18 August, Pro and Enterprise can opt into Escalation Rules 2.0. Mention it when a buyer inspects overdue handoffs. Do not pitch it to Starter."
Launch plan. "Here is the training plan, go/no-go ledger, owner matrix, and 30-day adoption review."
If a seller has to open another doc to know what to say today, it is not done.
Confirm Inputs First
Ask only for the inputs that change the update:
- The source notes, spec, or changelog
- Who must act, and which channel carries the update
- Known status, effective date, and eligibility
- Current talk tracks, FAQs, or battlecards only if they asked for a diff
If status or date is missing, leave it unknown. Do not invent launch dates, availability, or claims.
Read The Right Reference
Read references/release-transformation-guide.md for the field-usable test, status rules, and channel rewrite. Read references/source-system-guide.md when the source or destination is Slack, a wiki, or an enablement platform.
Default Workflow
- Build the factual change record.
Separate product facts from seller implications. Code complete, announced, or partially rolled out is not generally available. Done when each change has status, date or
unknown, eligibility, and source. - Decide who should care. Personas, segments, editions, or use cases that change. Routine fixes with no field action stay in a one-line digest or drop out. Done when you can name who acts and who can ignore it.
- Translate into field language. Customer impact, when to mention it, the qualification cue, the action after the effective date, and approved proof only if you have it. Done when a seller can use it without opening the engineering notes.
- State what did not change. What still works the old way. What this release does not allow. The line sellers should stop using if the old line is now wrong.
- Package it for the requested channel. Slack, email, wiki, and manager briefing are different lengths of the same facts. Rewrite; do not paste. Done when each requested variant can be sent as-is after human approval.
- Diff current assets only if asked.
Mark
create,update,no_change, orretirewith section, owner, and date. If the current asset was not supplied, writecurrent asset not supplied. Do not invent a disposition.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 71 lines · 80 tokens per session scan A 4cc20d66fdcd
release-notes-to-seller-updates is a skill published in the GitHub repository nthnclrk/enablement-skills (13 stars, last pushed 23d ago), licensed MIT. It adds 80 tokens to every session and 905 once invoked, about $0.0004 per session on Opus 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…