Rsdoctor is a build analyzer for Rspack projects that shows how compilation works, what it produces, and where build problems occur. Development teams use it to inspect build artifacts and timing, check build rules, and add custom scans. The catalogue add-ons provide ways to work with Rsdoctor.
Borrowing it
Nothing to install: this file belongs to web-infra-dev/rsdoctor. 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/web-infra-dev/rsdoctor/main/.agents/skills/release-blog-writer/SKILL.mdgit clone --depth 1 https://github.com/web-infra-dev/rsdoctorWrote 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/web-infra-dev/rsdoctor/release-blog-writer)<a href="https://agentmods.dev/skills/web-infra-dev/rsdoctor/release-blog-writer"><img src="https://agentmods.dev/badge/skills/web-infra-dev/rsdoctor/release-blog-writer/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/web-infra-dev/rsdoctor/release-blog-writer"><img src="https://agentmods.dev/badge/skills/web-infra-dev/rsdoctor/release-blog-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00804 |
| Opus 5 | $0.00016 | $0.00402 |
| Sonnet 5 | $0.00007 | $0.00161 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
release-blog-writer 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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- release-blog-writer — 100% identical, 0 lines differ
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 blog writer
Purpose
Use this skill to write release blogs that feel like product communication, not raw changelog output. The blog may be written in English, Chinese, or another user-requested language, but these instructions stay language-agnostic and project-agnostic.
Core writing rules
- Follow the user's requested language and the style of existing release blogs for the same product.
- Use previous major or minor release posts as the primary style reference when available.
- Prefer clear user value over implementation trivia.
- Avoid turning the blog into a complete changelog.
Recommended shape
Use the project's existing blog metadata and component conventions. If the product has neighboring release posts, mirror their frontmatter, author block, date format, title style, and navigation pattern.
Section writing
Each feature section should usually follow this pattern:
- Describe the change clearly so readers understand its background, purpose, use cases, and user-facing benefits such as performance gains.
- Avoid exhaustive API lists; select the key APIs or behaviors readers need, and when useful, use one precise code or configuration example to make the change clear at a glance.
Headings
- Use sentence case for titles and headings.
- Keep headings short and specific.
- Keep anchors stable and readable.
- If the website is built with Rspress, use the Rspress anchor syntax, such as
\{#foo-bar}. - For multilingual posts, treat the English post as the source of truth for section anchors. Matching headings in other languages should resolve to the same final anchor as the English heading, adding
\{#anchor-id}when their generated anchor would differ. - Default English anchors are generated by lowercasing the heading, removing punctuation, replacing whitespace with hyphens, and appending numeric suffixes for duplicates. If the English heading is long or the generated anchor is not stable enough, choose a short semantic custom anchor and apply it to every language version.
- Do not add a custom anchor when it is identical to the default generated anchor.
- If the website is built with Rspress, use the Rspress anchor syntax, such as
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.
- 10d ago First seen · 71 lines · 33 tokens per session scan A 717da2116749
release-blog-writer is a skill published in the GitHub repository web-infra-dev/rsdoctor (1,139 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 804 once invoked, about $0.0002 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
resume-builder
Generate professional resumes that conform to the Reactive Resume schema. Use when the user wants to create, build, or generate a resume through conversational AI, or asks about resume structure, sections, or content. This skill guides the agent to ask clarifying questions, avoid hallucination, and produce valid JSON…
conventional-commit
Workflow for generating conventional commit messages following the Conventional Commits specification. MUST be invoked every time a commit is created. Guides construction of standardized commit messages with correct type, scope, description, body, and footer.
markdown
Markdown formatting rules for this project. Apply when writing or editing any .md or .mdx file, including documentation and website content.
oh-my-posh
Install, configure, or troubleshoot Oh My Posh/ohmyposh: shell init, themes, segments, Nerd Font icons, and prompt setup on PowerShell, zsh, bash, or fish.
research
Run deep research on any topic using the Deep Research MCP server. Use this skill whenever the user wants to research a topic, gather information, find sources, or create a research document. Triggers on: 'research this', 'find out about', 'gather information on', 'I need to understand', 'deep dive into', or any…
date-formatter
Converts dates between formats and handles timezone differences.