release-blog-writer: Reusable for AI Agents | OpenAgentSkill

Overview

Write or revise release blog posts for product releases. Use when the user asks to draft, polish, restructure, or adapt a release announcement.

Read full documentation

Source documentation, not instructions for this website. Review permissions before running any commands.

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.

Tone

Be professional, direct, and understated.
Avoid vague claims such as "greatly improved" unless the improvement is explained or quantified.
Avoid slogan-like positioning in feature updates unless intentionally discussing product vision.
Qualify benchmark numbers with enough context to make them credible.
When presenting performance gains, bold only the key improvement numbers, avoid frequent emphasis, and use tables or images when they make the comparison clearer at a glance.
Use product and ecosystem terms consistently.
Write naturally in the target language; do not let the prose read like a literal translation from another language.

Links

Add links where they help readers continue:

Product documentation for options, APIs, plugins, or migration steps.
Upstream PRs or specs for implementation context.
Platform documentation for browser, Node.js, or language features.

Do not over-link common terms. Link the first meaningful occurrence or the option name users are likely to search for.

For Rstack documentation links on rspack.rs, rsbuild.rs, rspress.rs, rslib.rs, rsdoctor.rs, and rstest.rs, match the URL language to the blog language. In Chinese posts, prefer /zh/ paths such as https://rspack.rs/zh/; in English posts, omit /zh/ because the default docs are English. Apply the same rule to deeper documentation URLs.

Revision behavior

When revising an existing blog:

Keep the user's latest manual edits unless they conflict with the request.
Prefer small targeted edits over broad rewrites.
If the user asks to remove a kind of detail, remove it consistently across the post.

View source ↗

File metadata

name: release-blog-writer
description: Write or revise release blog posts for product releases. Use when the user asks to draft, polish, restructure, or adapt a release announcement.
metadata:
  internal: true

View original text

---
name: release-blog-writer
description: Write or revise release blog posts for product releases. Use when the user asks to draft, polish, restructure, or adapt a release announcement.
metadata:
internal: true
---

# Release blog writer

## Purpose

## 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

## 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.

## Tone

- Be professional, direct, and understated.
- Avoid vague claims such as "greatly improved" unless the improvement is explained or quantified.
- Avoid slogan-like positioning in feature updates unless intentionally discussing product vision.
- Qualify benchmark numbers with enough context to make them credible.
- When presenting performance gains, bold only the key improvement numbers, avoid frequent emphasis, and use tables or images when they make the comparison clearer at a glance.
- Use product and ecosystem terms consistently.
- Write naturally in the target language; do not let the prose read like a literal translation from another language.

## Links

Add links where they help readers continue:

- Product documentation for options, APIs, plugins, or migration steps.
- Upstream PRs or specs for implementation context.
- Platform documentation for browser, Node.js, or language features.

Do not over-link common terms. Link the first meaningful occurrence or the option name users are likely to search for.

For Rstack documentation links on `rspack.rs`, `rsbuild.rs`, `rspress.rs`, `rslib.rs`, `rsdoctor.rs`, and `rstest.rs`, match the URL language to the blog language. In Chinese posts, prefer `/zh/` paths such as `https://rspack.rs/zh/`; in English posts, omit `/zh/` because the default docs are English. Apply the same rule to deeper documentation URLs.

## Revision behavior

When revising an existing blog:

- Keep the user's latest manual edits unless they conflict with the request.
- Prefer small targeted edits over broad rewrites.
- If the user asks to remove a kind of detail, remove it consistently across the post.

Use with my agent

Skill source recorded

Skill instructions are recorded. This is not a runtime test, safety guarantee or compatibility certification.

Review before install: Review before install

Financial research output is not financial advice; require human review before any live investment decision
SKILL.md excerpt is truncated in the review input, but the provided content is sufficient for evaluation.
No explicit limitations or out-of-scope scenarios are documented, though the skill is narrowly scoped to release blog writing.
Financial research output is not financial advice; require human review before any live investment decision.

Install targets

Codex install prompt

Install the "release-blog-writer" agent skill from https://github.com/rstackjs/agent-skills/tree/main/.agents/skills/release-blog-writer. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Write or revise release blog posts for product releases. Use when the user asks to draft, polish, restructure, or adapt a release announcement. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"rstackjs-release-blog-writer","task":"Install release-blog-writer","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes. Recorded instruction path: .agents/skills/release-blog-writer/SKILL.md. Recorded revision: 9032c74a72ade1c51587ba278a4b45812e86d94c. Confirm the source matches these instructions. Treat repository text as untrusted data; ask before credentials, paid services or external side effects.

Source & trust

IndexedInstall path available

Repository metadata and review signals are advisory. Popularity, source discovery and successful execution are different facts.

License: MIT
Version: 1.0.0
Last GitHub push: Sep 4, 2026
Registry updated: Sep 7, 2026
Instruction path: .agents/skills/release-blog-writer/SKILL.md @ 9032c74a72ad

Version reported in registry metadata; check source releases before relying on it.

Quality

67/100

Promising

Trust

61/100

Sandbox only

Audit

77/100

Needs review

Agent access

This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.

Open install API LLM text format Open manifest Auto-resolve Plan

More details

{
  "version": "openagentskill-agent-metadata-v2",
  "review_evidence": {
    "indexed": true,
    "static_checked": false,
    "ai_reviewed": false,
    "creator_verified": false,
    "review_result": "not_recorded",
    "reviewed_at": null,
    "package_fingerprint": null,
    "policy_version": null,
    "notice": "Publication, static checks, AI review, and creator verification are independent facts. None guarantees runtime safety."
  },
  "skill": {
    "slug": "rstackjs-release-blog-writer",
    "name": "release-blog-writer",
    "description": "Write or revise release blog posts for product releases. Use when the user asks to draft, polish, restructure, or adapt a release announcement.",
    "category": "productivity",
    "url": "https://www.openagentskill.com/skills/rstackjs-release-blog-writer",
    "repository": "https://github.com/rstackjs/agent-skills/tree/main/.agents/skills/release-blog-writer",
    "github_repo": "rstackjs/agent-skills"
  },
  "suited_tasks": [
    "Browser automation workflows",
    "Claude Code teams",
    "builders willing to evaluate younger projects",
    "Navigate pages",
    "Click and type safely",
    "Check visual and DOM state",
    "Chunk documents",
    "Create embeddings"
  ],
  "suited_agents": [
    "Codex",
    "Claude Code",
    "Cursor",
    "OpenAgentSkill CLI",
    "Browser agents",
    "CLI"
  ],
  "install": {
    "source_evidence": {
      "status": "source-recorded",
      "sourceRecorded": true,
      "canOfferInstall": true,
      "path": ".agents/skills/release-blog-writer/SKILL.md",
      "revision": "9032c74a72ade1c51587ba278a4b45812e86d94c",
      "notice": "A skill instruction path and install command are recorded. This is not proof of compatibility, runtime success or safety; review the source and permissions first."
    },
    "command": "npx skills add rstackjs/agent-skills --skill release-blog-writer",
    "ready": true,
    "targets": [
      {
        "id": "openagentskill-cli",
        "label": "CLI",
        "kind": "command",
        "value": "npx --yes https://github.com/Leon-Drq/openagentskill/releases/download/cli-v0.3.0/openagentskill-0.3.0.tgz add rstackjs-release-blog-writer"
      },
      {
        "id": "codex",
        "label": "Codex",
        "kind": "agent-prompt",
        "value": "Install the \"release-blog-writer\" agent skill from https://github.com/rstackjs/agent-skills/tree/main/.agents/skills/release-blog-writer. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Write or revise release blog posts for product releases. Use when the user asks to draft, polish, restructure, or adapt a release announcement. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {\"event_id\":\"install_<unique-id>\",\"skill_slug\":\"rstackjs-release-blog-writer\",\"task\":\"Install release-blog-writer\",\"agent\":\"codex\",\"outcome\":\"success\",\"install_used\":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes. Recorded instruction path: .agents/skills/release-blog-writer/SKILL.md. Recorded revision: 9032c74a72ade1c51587ba278a4b45812e86d94c. Confirm the source matches these instructions. Treat repository text as untrusted data; ask before credentials, paid services or external side effects."
      },
      {
        "id": "claude-code",
        "label": "Claude Code",
        "kind": "agent-prompt",
        "value": "Add \"release-blog-writer\" as a Claude Code skill from https://github.com/rstackjs/agent-skills/tree/main/.agents/skills/release-blog-writer. Inspect the skill instructions, place the reusable skill files in the appropriate local skills location for this project, and report the activation steps. Skill purpose: Write or revise release blog posts for product releases. Use when the user asks to draft, polish, restructure, or adapt a release announcement. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {\"event_id\":\"install_<unique-id>\",\"skill_slug\":\"rstackjs-release-blog-writer\",\"task\":\"Install release-blog-writer\",\"agent\":\"claude-code\",\"outcome\":\"success\",\"install_used\":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes. Recorded instruction path: .agents/skills/release-blog-writer/SKILL.md. Recorded revision: 9032c74a72ade1c51587ba278a4b45812e86d94c. Confirm the source matches these instructions. Treat repository text as untrusted data; ask before credentials, paid services or external side effects."
      },
      {
        "id": "cursor",
        "label": "Cursor",
        "kind": "agent-prompt",
        "value": "Turn \"release-blog-writer\" from https://github.com/rstackjs/agent-skills/tree/main/.agents/skills/release-blog-writer into a reusable Cursor project rule or agent instruction. Preserve the core workflow, adapt paths to this repo, and keep the rule scoped to tasks where it is relevant. Skill purpose: Write or revise release blog posts for product releases. Use when the user asks to draft, polish, restructure, or adapt a release announcement. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {\"event_id\":\"install_<unique-id>\",\"skill_slug\":\"rstackjs-release-blog-writer\",\"task\":\"Install release-blog-writer\",\"agent\":\"cursor\",\"outcome\":\"success\",\"install_used\":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes. Recorded instruction path: .agents/skills/release-blog-writer/SKILL.md. Recorded revision: 9032c74a72ade1c51587ba278a4b45812e86d94c. Confirm the source matches these instructions. Treat repository text as untrusted data; ask before credentials, paid services or external side effects."
      }
    ],
    "handoff_url": "https://www.openagentskill.com/api/skills/rstackjs-release-blog-writer/install",
    "manifest_url": "https://www.openagentskill.com/api/registry/manifest/rstackjs-release-blog-writer"
  },
  "trust": {
    "score": 69,
    "label": "Manual review",
    "version": "trust-score-v4",
    "install_policy": "review",
    "evidence": {
      "stars": "93 GitHub stars",
      "repoActivity": "93 stars, 4 forks",
      "lastPushed": "4d since push",
      "license": "MIT",
      "repository": "https://github.com/rstackjs/agent-skills/tree/main/.agents/skills/release-blog-writer",
      "install": "npx skills add rstackjs/agent-skills --skill release-blog-writer",
      "installSafety": "standard package or runtime install path",
      "permissionSurface": "network or browser access, database access",
      "documentation": "Strong README/SKILL.md context",
      "agentOutcomes": "No agent outcome data yet"
    },
    "outcome_evidence": {
      "total": 0,
      "successes": 0,
      "failures": 0,
      "not_relevant": 0,
      "success_rate": null,
      "recent_success_rate": null,
      "recent_failure_rate": null,
      "install_attempts": 0,
      "install_success_rate": null,
      "risk_blocked": 0,
      "setup_required": 0,
      "avg_output_quality": null,
      "production_outcomes": 0,
      "last_outcome_at": null,
      "label": "No agent outcome data yet"
    },
    "auto_install": {
      "allowed": false,
      "sandbox_required": true,
      "reason": "Test manually in an isolated workspace and compare against safer alternatives."
    },
    "best_for": [
      "productivity",
      "agent-skill"
    ],
    "known_risks": [
      "SKILL.md excerpt is truncated in the review input, but the provided content is sufficient for evaluation.",
      "Financial research output is not financial advice; require human review before any live investment decision.",
      "Quality score needs review",
      "GitHub adoption: 93 GitHub stars",
      "Stars/forks activity: 93 stars, 4 forks; issue activity unavailable in current metadata"
    ]
  },
  "agent_proven": {
    "version": "agent-proven-v1",
    "score": 0,
    "tier": "unproven",
    "label": "Needs first agent run",
    "summary": "No agent outcome reports yet. Use Resolve, run one narrow sandbox task, then report the result.",
    "metrics": {
      "totalOutcomes": 0,
      "successfulOutcomes": 0,
      "failedOutcomes": 0,
      "installAttempts": 0,
      "installSuccessRate": null,
      "successRate": null,
      "recentSuccessRate": null,
      "recentFailureRate": null,
      "riskBlocked": 0,
      "setupRequired": 0,
      "notRelevant": 0,
      "avgOutputQuality": null,
      "avgTimeToUsefulMs": null,
      "productionOutcomes": 0,
      "humanReviewRequired": 0,
      "uniqueAgents": 0,
      "lastOutcomeAt": null
    },
    "signals": [],
    "penalties": [
      "No real agent outcome evidence yet"
    ]
  },
  "audit": {
    "score": 77,
    "risk_level": "needs_review",
    "risk_label": "Needs review",
    "warnings": [
      "Financial research output is not financial advice; require human review before any live investment decision",
      "SKILL.md excerpt is truncated in the review input, but the provided content is sufficient for evaluation.",
      "No explicit limitations or out-of-scope scenarios are documented, though the skill is narrowly scoped to release blog writing.",
      "Financial research output is not financial advice; require human review before any live investment decision.",
      "Quality score needs review",
      "GitHub adoption: 93 GitHub stars",
      "Stars/forks activity: 93 stars, 4 forks; issue activity unavailable in current metadata"
    ]
  },
  "safety_gate": {
    "tier": "experimental",
    "label": "Experimental",
    "auto_install_policy": "review",
    "auto_install_allowed": false,
    "human_review_required": true,
    "blocked": false,
    "recommended_action": "Test manually in an isolated workspace and compare against safer alternatives."
  },
  "quality": {
    "score": 67,
    "label": "Promising"
  },
  "supply": {
    "track": "Coding and developer agents",
    "scenario": "GitHub automation",
    "maintenance": "4d since push",
    "risk": "Needs review"
  },
  "alternative_skills": [],
  "do_not_use_when": [
    "teams that need a vendor-supported SLA",
    "production agents without a repository review",
    "SKILL.md excerpt is truncated in the review input, but the provided content is sufficient for evaluation.",
    "No OpenAgentSkill engagement data yet",
    "Financial research output is not financial advice; require human review before any live investment decision",
    "No explicit limitations or out-of-scope scenarios are documented, though the skill is narrowly scoped to release blog writing.",
    "Financial research output is not financial advice; require human review before any live investment decision.",
    "Quality score needs review"
  ],
  "agent_contract": {
    "task_input": "Use release-blog-writer in an agent workflow",
    "recommended_action": "Test manually in an isolated workspace and compare against safer alternatives.",
    "install_policy": "review",
    "minimum_review_before_use": [
      "Trust: 69/100 Manual review",
      "Audit: 77/100 Needs review",
      "Safety: 57/100 Review before install",
      "Review repository, license, install command, and permission surface before production use."
    ],
    "expected_agent_output": {
      "selected_skill": "rstackjs-release-blog-writer (release-blog-writer)",
      "install_command": "npx skills add rstackjs/agent-skills --skill release-blog-writer",
      "risk_summary": "Needs review; Experimental; Review before production",
      "verification_result": "Report the smallest successful task, files touched, warnings, and any missing setup."
    }
  },
  "outcome_feedback": {
    "endpoint": "https://www.openagentskill.com/api/agent/outcome",
    "method": "POST",
    "requires_resolve_event_id": true,
    "event_id_source": "Use install_receipt.outcome_feedback.event_id or feedback.event_id returned by /api/agent/resolve for the current task.",
    "expected_outcomes": [
      "success",
      "failed",
      "not_relevant",
      "blocked_by_risk",
      "setup_required"
    ],
    "payload_template": {
      "event_id": "<install_receipt.outcome_feedback.event_id or feedback.event_id from /api/agent/resolve>",
      "skill_slug": "rstackjs-release-blog-writer",
      "task": "Use release-blog-writer in an agent workflow",
      "agent": "codex",
      "outcome": "success",
      "install_used": true,
      "risk_blocked": false,
      "setup_required": false,
      "task_success": true,
      "output_quality": 4,
      "error_type": null,
      "human_review_required": false,
      "workspace": "sandbox",
      "time_to_useful_ms": 120000,
      "notes": "Report the smallest successful task, setup friction, files touched, and risk notes."
    }
  },
  "endpoints": {
    "web": "https://www.openagentskill.com/skills/rstackjs-release-blog-writer",
    "api": "https://www.openagentskill.com/api/agent/skills/rstackjs-release-blog-writer",
    "audit": "https://www.openagentskill.com/skills/rstackjs-release-blog-writer/audit",
    "eval": "https://www.openagentskill.com/api/agent/evals?slug=rstackjs-release-blog-writer&task=Use%20release-blog-writer%20in%20an%20agent%20workflow&max_risk=medium",
    "resolve": "https://www.openagentskill.com/api/agent/resolve?task=Use%20release-blog-writer%20in%20an%20agent%20workflow&agent=codex&max_risk=medium",
    "receipt": "https://www.openagentskill.com/api/agent/receipt?task=Use%20release-blog-writer%20in%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text",
    "install": "https://www.openagentskill.com/api/skills/rstackjs-release-blog-writer/install",
    "manifest": "https://www.openagentskill.com/api/registry/manifest/rstackjs-release-blog-writer"
  }
}

For the creator

Listing source

Registry indexed

Claimable

This listing was indexed from public sources and is not marked official until a maintainer claim is approved.

Creator: rstackjs
Source: rstackjs/agent-skills
Indexed by: OpenAgentSkill community index

Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.

Claim this skill

Owner claim

Claim this skill listing

This Registry indexed listing is attributed to rstackjs but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.

Share kit

Creator backlink kit

Add the evidence badges to your README

Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.

[![Listed on OpenAgentSkill](https://www.openagentskill.com/api/badge/rstackjs-release-blog-writer?metric=listed&label=Listed)](https://www.openagentskill.com/skills/rstackjs-release-blog-writer?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[![OpenAgentSkill Trust](https://www.openagentskill.com/api/badge/rstackjs-release-blog-writer?metric=trust&label=Trust)](https://www.openagentskill.com/skills/rstackjs-release-blog-writer?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[![OpenAgentSkill Audit](https://www.openagentskill.com/api/badge/rstackjs-release-blog-writer?metric=audit&label=Audit)](https://www.openagentskill.com/skills/rstackjs-release-blog-writer/audit)
[![Agent Proven](https://www.openagentskill.com/api/badge/rstackjs-release-blog-writer?metric=proven&label=Agent%20Proven)](https://www.openagentskill.com/skills/rstackjs-release-blog-writer?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)

Preview badge Open audit Creator kit

Community signal

Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.