Agent skill

Write Biweekly Announcement

Generate bi-weekly announcement posts for Blade Design System updates by analyzing changelog entries from the past two weeks

MITAuto-check passedDevelopment

Install Write Biweekly Announcement

skills CLI

$ npx skills add razorpay/blade --skill write-biweekly-announcement -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install razorpay/blade write-biweekly-announcement --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/razorpay/blade.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/write-biweekly-announcement .claude/skills/write-biweekly-announcement && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "write-biweekly-announcement" agent skill from https://github.com/razorpay/blade/tree/master/.agents/skills/write-biweekly-announcement into .claude/skills/write-biweekly-announcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-biweekly-announcement", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/razorpay/blade/tree/master/.agents/skills/write-biweekly-announcement

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add razorpay/blade --skill write-biweekly-announcement -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install razorpay/blade write-biweekly-announcement --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/razorpay/blade.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/write-biweekly-announcement .agents/skills/write-biweekly-announcement && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "write-biweekly-announcement" agent skill from https://github.com/razorpay/blade/tree/master/.agents/skills/write-biweekly-announcement into .agents/skills/write-biweekly-announcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-biweekly-announcement", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add razorpay/blade --skill write-biweekly-announcement -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install razorpay/blade write-biweekly-announcement --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/razorpay/blade.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/write-biweekly-announcement .cursor/skills/write-biweekly-announcement && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "write-biweekly-announcement" agent skill from https://github.com/razorpay/blade/tree/master/.agents/skills/write-biweekly-announcement into .cursor/skills/write-biweekly-announcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-biweekly-announcement", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/razorpay/blade.git --path .agents/skills/write-biweekly-announcement

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add razorpay/blade --skill write-biweekly-announcement -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install razorpay/blade write-biweekly-announcement --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/razorpay/blade.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/write-biweekly-announcement .gemini/skills/write-biweekly-announcement && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "write-biweekly-announcement" agent skill from https://github.com/razorpay/blade/tree/master/.agents/skills/write-biweekly-announcement into .gemini/skills/write-biweekly-announcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-biweekly-announcement", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install razorpay/blade write-biweekly-announcement

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add razorpay/blade --skill write-biweekly-announcement -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/razorpay/blade.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/write-biweekly-announcement .github/skills/write-biweekly-announcement && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "write-biweekly-announcement" agent skill from https://github.com/razorpay/blade/tree/master/.agents/skills/write-biweekly-announcement into .github/skills/write-biweekly-announcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-biweekly-announcement", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add razorpay/blade --skill write-biweekly-announcement -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install razorpay/blade write-biweekly-announcement --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/razorpay/blade.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/write-biweekly-announcement .opencode/skills/write-biweekly-announcement && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "write-biweekly-announcement" agent skill from https://github.com/razorpay/blade/tree/master/.agents/skills/write-biweekly-announcement into .opencode/skills/write-biweekly-announcement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-biweekly-announcement", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: write-biweekly-announcement
GitHub stars: 656
Token cost: ~1.5k tokens
SKILL.md length: 467 words
Files: 1
Skills in repo: 16
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Generate bi-weekly announcement posts for Blade Design System updates by analyzing changelog entries from the past two weeks

Works in 8 steps: Data Collection → Content Structure → Content Guidelines → …
Tasks that involve Changelog and release notes
SKILL.md covers Purpose and Instructions
Calls git

What it does

Write Biweekly Announcement is an agent skill from razorpay/blade. Generate bi-weekly announcement posts for Blade Design System updates by analyzing changelog entries from the past two weeks

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes and Design systems. It works with Model Context Protocol and Git. The repository describes itself as: Design System that powers Razorpay. The licence is MIT.

When your agent uses it

Tasks that involve Changelog and release notes
Tasks that involve Design systems

Example prompts

“/write-biweekly-announcement”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Data Collection
Content Structure
Content Guidelines
Analysis Process
Quality Checks
Example Output Format
Tools to Use
Special Considerations

What it can do on your machine

Read from SKILL.md and the folder at commit fa38cf0. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Write Biweekly Announcement loads about 1.5k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 467 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~38
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from razorpay/blade at commit fa38cf0, republished under its MIT licence (© razorpay). 467 words, ~1,539 tokens.

Download SKILL.mdSave it as .claude/skills/write-biweekly-announcement/SKILL.md (or your agent's skills folder).

name: write-biweekly-announcement
description: Generate bi-weekly announcement posts for Blade Design System updates by analyzing changelog entries from the past two weeks
disable-model-invocation: true

Bi-Weekly Announcement Rule

Purpose

Generate bi-weekly announcement posts for Blade Design System updates by analyzing changelog entries from the past two weeks.

Instructions

1. Data Collection

Source: Use git diff command to get the changes we shipped in last 2 week or n weeks.
Scope: Include packages/blade/ and packages/blade-mcp/
Time Period: Calculate the date range for the past two weeks from the current date

2. Content Structure

Follow this exact format for the announcement:

:blade: Design System Enhancement Updates [Start Date - End Date]
:sparkles: Highlights

 New Components & Features:
[Feature 1]: [Brief description]
[Feature 2]: [Brief description]
[Feature 3]: [Brief description]
for example - 
QuickFilter: Introduced the QuickFilter component.



Version Updates - 
version - component: description 

for example - 
12.14.0 - QuickFilter: Add QuickFilters component


:github: Check out Blade Releases for the Full Changelog

3. Content Guidelines

Highlights Section

New Components: List any completely new components added
Major Features: Include significant feature additions to existing components
Big Fixes: Include important bug fixes that significantly improve functionality
Breaking Changes: Highlight any breaking changes with clear explanations

Version Updates Section

Chronological Order: List versions from newest to oldest
Component Focus: Group changes by component name
Clear Descriptions: Use concise but descriptive language
Consistent Format: Follow the pattern [Component]: [description]

4. Analysis Process

Calculate the two-week period from current date. you can use this git command git diff HEAD@{2.weeks.ago} HEAD -- CHANGELOG.md to get the diff. of changes. make sure you get all the diff from the bottom. and use these diff only to write the annoucement. make sure you run this command only on changelog.md for blade and blade-mcp projects
Categorize Changes:
- New components/features
- Bug fixes
- Improvements
- Breaking changes
Prioritize Highlights: Select the most impactful changes for the highlights section
Format Entries: Ensure consistent formatting and clear descriptions

5. Quality Checks

Accuracy: Verify all version numbers and dates are correct
Completeness: Ensure all significant changes are included
Clarity: Use clear, non-technical language when possible
Consistency: Maintain consistent formatting throughout

6. Example Output Format

:blade:  Design System Enhancement Updates [8th Aug - 22nd Aug]
:sparkles: Highlights -
:happy-cat:  New Components & Features:-
Filled Icons: Introduced 49+ new filled icons.
DatePicker: Improved UX with editable input, built-in formatting, leading preset dropdown, optional action buttons, and a simplified single-field for range selection.
Carousel: Introduced a new side navigation button style side-overlap
:nail_care: Bug Fixes-
DatePicker UI: Fixed arrow to hyphen conversion in range input field.
PhoneNumberInput: Reverted virtualization in mobile to maintain stability.
Bottom Sheet Height Logic: Fixed height calculation logic for more accurate component sizing.
ListView Filter Enhancement: Improved horizontal scroll for filters on desktop with gradient overlay removal.
Promotional Toast Flexibility: Made leading prop optional for better component customization.
:chart_with_upwards_trend: Version Updates -
12.49.0 - Icons: We've added a new  49+ filled icons to give you more design options.
12.48.0 - DatePicker: You can now use formatted input, a preset dropdown, and single-field range selection for more flexible date picking.
12.47.1 - Bottom Sheet: We've updated the height calculation logic of bottom sheet heights to ensure a more consistent and predictable user  & developer experience.
12.47.0 - Carousel: A new navigation button position has been added that allows the buttons to overlap with the carousel for a cleaner look.
12.46.2 - ListView: We've improved the desktop experience for ListView by adding horizontal scrolling for filters and removing the distracting gradient overlay for a cleaner, more focused view.
12.46.1 - Need more flexibility with your notifications? The leading prop for promotional toasts is now optional, giving you more control over your designs.
:mcp: Blade MCP Updates -
1.4.1 - Blade MCP: add constraints to component knowledgebase.
:github: Check out Blade Releases for the Full Changelog

Show full SKILL.md (193 more words)Show less

7. Tools to Use

File Reading & Date Calculation: For now just use blade-mcp and blade. Calculate the two-week period from current date. you can use this git command git diff HEAD@{2.weeks.ago} HEAD -- CHANGELOG.md to get the diff. of changes. make sure you get all the diff from the bottom. and use these diff only to write the annoucement. use this command only on blade and blade-mcp project make sure you only include changes that are done in given timeline
Content Analysis: Parse and categorize diff changes and include these only
Formatting: Follow the example given to you. it's going to be a slack message. so don't use markdown. just use txt format.
Release link Add link for github release in https://github.com/razorpay/blade/releases at the end of message
Final File Creation Create a file announcement.md in main repo. so it would be easy to copy paste for developers.

8. Special Considerations

Breaking Changes: Always highlight breaking changes prominently
Performance Improvements: Include significant performance enhancements
Accessibility: Highlight accessibility improvements
Developer Experience: Include DX improvements and new APIs
Regarding Output So onces you are done writing the announcement , make a txt file and write announcement in it.

Files

Just SKILL.md in .agents/skills/write-biweekly-announcement of razorpay/blade.

Open the folder on GitHubat commit fa38cf0

Compare with similar skills

Write Biweekly Announcement next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Write Biweekly Announcement compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Write Biweekly Announcement this skillrazorpay/blade	656	—	~1.5k	Automated safety check: Pass	MIT	yesterday
Git Releasewesammustafa/opencode-primer	398	—	~409	Automated safety check: Pass	MIT	3 mo ago
Changelogratel-ai/ratel	469	—	~1.6k	Automated safety check: Pass	MIT	2 days ago
Stable Release Notesvaadin/web-components	582	—	~1.2k	Automated safety check: Pass	None	today
Release Notesno-human-ai/no_human	332	—	~2k	Automated safety check: Pass	MIT	5 days ago
Release Crater3bl-org/r3bl-open-core	485	—	~2.4k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Git Release
wesammustafa/opencode-primer
Draft release notes from merged PRs, propose a semver bump, and emit a copy-pasteable gh release create command.
398 GitHub stars~409 tokensUpdated 3 mo ago
DevelopmentAuto-check passed
Changelog
ratel-ai/ratel
Update per-package CHANGELOG.md files for a Ratel release. An agent skill from ratel-ai/ratel.
469 GitHub stars~1.6k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Stable Release Notes
vaadin/web-components
Prepare GitHub release notes for a beta or stable web-components release.
582 GitHub stars~1.2k tokensUpdated today
DevelopmentAuto-check passed
Release Notes
no-human-ai/no_human
Write release notes for a tagged release — a business-impact summary of what changed for the user, plus a thanks section naming every contributor whose commits are in the release.
332 GitHub stars~2k tokensUpdated 5 days ago
DevelopmentAuto-check passed
Release Crate
r3bl-org/r3bl-open-core
Publish a crate release to crates.io with changelog, standalone release notes, git tag, and GitHub release.
485 GitHub stars~2.4k tokensUpdated yesterday
DevelopmentAuto-check passed
Release Management
termide/termide
Prepare and publish a project release with version updates, changelog generation, tagging, and validation
172 GitHub stars~6.8k tokensUpdated yesterday
DevelopmentAuto-check passed

Questions about Write Biweekly Announcement

What does Write Biweekly Announcement do?

Generate bi-weekly announcement posts for Blade Design System updates by analyzing changelog entries from the past two weeks. Write Biweekly Announcement is an agent skill from razorpay/blade.

When should I use Write Biweekly Announcement?

Write Biweekly Announcement fits situations like: tasks that involve Changelog and release notes; tasks that involve Design systems.

How do I install Write Biweekly Announcement in Claude Code?

Run `npx skills add razorpay/blade --skill write-biweekly-announcement -a claude-code`. Or copy the skill folder (.agents/skills/write-biweekly-announcement in razorpay/blade) into .claude/skills/write-biweekly-announcement in your project. Claude Code loads it when a task matches its description.

How do I install Write Biweekly Announcement in Codex?

Run `npx skills add razorpay/blade --skill write-biweekly-announcement -a codex`. Or copy the skill folder (.agents/skills/write-biweekly-announcement in razorpay/blade) into .agents/skills/write-biweekly-announcement in your project. Codex loads it when a task matches its description.

Can I use Write Biweekly Announcement in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add razorpay/blade --skill write-biweekly-announcement -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-biweekly-announcement, .gemini/skills/write-biweekly-announcement, .github/skills/write-biweekly-announcement and .opencode/skills/write-biweekly-announcement in your project.

What does Write Biweekly Announcement need to run?

Going by SKILL.md and its folder, Write Biweekly Announcement needs the command-line tools its instructions call (git).

Does Write Biweekly Announcement access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Write Biweekly Announcement safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Write Biweekly Announcement use?

Write Biweekly Announcement is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Write Biweekly Announcement use?

About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Write Biweekly Announcement?

Skills that share tags, products or a category with Write Biweekly Announcement: Git Release (wesammustafa/opencode-primer, 398 stars), Changelog (ratel-ai/ratel, 469 stars), Stable Release Notes (vaadin/web-components, 582 stars) and Release Notes (no-human-ai/no_human, 332 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Write Biweekly Announcement?

razorpay (a GitHub organization) maintains it in razorpay/blade, which has 656 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 9, 2026.

Source: razorpay/blade on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Write Biweekly Announcement

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Bi-Weekly Announcement Rule

Purpose

Instructions

1. Data Collection

2. Content Structure

3. Content Guidelines

Highlights Section

Version Updates Section

4. Analysis Process

5. Quality Checks

6. Example Output Format

7. Tools to Use

8. Special Considerations

Files

Compare with similar skills

Similar skills

More from razorpay/blade

Related

Questions about Write Biweekly Announcement