Agent skill

SDK Release Checklist

Checklist for adding a new SDK or releasing a new SDK version.

MITAuto-check passedDevelopment

Install SDK Release Checklist

skills CLI

$ npx skills add macalbert/envilder --skill sdk-release-checklist -a claude-code

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

GitHub CLI

$ gh skill install macalbert/envilder sdk-release-checklist --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/macalbert/envilder.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/sdk-release-checklist .claude/skills/sdk-release-checklist && 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 "sdk-release-checklist" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/sdk-release-checklist into .claude/skills/sdk-release-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdk-release-checklist", 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/macalbert/envilder/tree/main/.github/skills/sdk-release-checklist

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 macalbert/envilder --skill sdk-release-checklist -a codex

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

GitHub CLI

$ gh skill install macalbert/envilder sdk-release-checklist --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/sdk-release-checklist .agents/skills/sdk-release-checklist && 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 "sdk-release-checklist" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/sdk-release-checklist into .agents/skills/sdk-release-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdk-release-checklist", 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 macalbert/envilder --skill sdk-release-checklist -a cursor

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

GitHub CLI

$ gh skill install macalbert/envilder sdk-release-checklist --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/sdk-release-checklist .cursor/skills/sdk-release-checklist && 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 "sdk-release-checklist" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/sdk-release-checklist into .cursor/skills/sdk-release-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdk-release-checklist", 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/macalbert/envilder.git --path .github/skills/sdk-release-checklist

--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 macalbert/envilder --skill sdk-release-checklist -a gemini-cli

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

GitHub CLI

$ gh skill install macalbert/envilder sdk-release-checklist --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/macalbert/envilder.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/sdk-release-checklist .gemini/skills/sdk-release-checklist && 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 "sdk-release-checklist" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/sdk-release-checklist into .gemini/skills/sdk-release-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdk-release-checklist", 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 macalbert/envilder sdk-release-checklist

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 macalbert/envilder --skill sdk-release-checklist -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/sdk-release-checklist .github/skills/sdk-release-checklist && 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 "sdk-release-checklist" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/sdk-release-checklist into .github/skills/sdk-release-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdk-release-checklist", 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 macalbert/envilder --skill sdk-release-checklist -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 macalbert/envilder sdk-release-checklist --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/macalbert/envilder.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/sdk-release-checklist .opencode/skills/sdk-release-checklist && 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 "sdk-release-checklist" agent skill from https://github.com/macalbert/envilder/tree/main/.github/skills/sdk-release-checklist into .opencode/skills/sdk-release-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdk-release-checklist", 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: sdk-release-checklist
GitHub stars: 138
Token cost: ~1.5k tokens
SKILL.md length: 534 words
Files: 1
Skills in repo: 30
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Checklist for adding a new SDK or releasing a new SDK version.

Works in 8 steps: Code & Tests → Version Source File → Website: Version Badge Wiring → …
Creating a new runtime SDK
SKILL.md covers When to Use, New SDK: Full Checklist, Existing SDK: Version Bump… and Validation, plus 1 more section
Calls pnpm, node and npm

What it does

SDK Release Checklist is an agent skill from macalbert/envilder. Checklist for adding a new SDK or releasing a new SDK version. Covers code, tests, website integration (docs page, version badge, changelog sidebar, i18n keys), and CI wiring. Use when creating a new runtime SDK, bumping an SDK version, or auditing that all integration points are connected.

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 Feature launches and release readiness, Changelog and release notes and Internationalization. It works with Node.js, Astro, Python and .NET. The repository describes itself as: One secret mapping for local dev, CI/CD, and runtime. Envilder resolves cloud secrets from your own vaults without SaaS middlemen, duplicated config, or .env drift. The licence is MIT.

When your agent uses it

Creating a new runtime SDK
Bumping an SDK version
Auditing that all integration points are connected

Example prompts

“/sdk-release-checklist”

Requirements

Python 3
Node.js

Workflow steps

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

Code & Tests
Version Source File
Website: Version Badge Wiring
Website: Documentation Page Section
Website: Changelog Integration
Website: SDK Cards Component
Copilot Instructions & Build Config
Documentation Cross-References

What it can do on your machine

Read from SKILL.md and the folder at commit b6a0327. 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:
- pnpm
- node
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm and npm, 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

SDK Release Checklist loads about 1.5k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 534 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~78
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 macalbert/envilder at commit b6a0327, republished under its MIT licence (© macalbert). 534 words, ~1,458 tokens.

Download SKILL.mdSave it as .claude/skills/sdk-release-checklist/SKILL.md (or your agent's skills folder).

name: sdk-release-checklist
description: Checklist for adding a new SDK or releasing a new SDK version. Covers code, tests, website integration (docs page, version badge, changelog sidebar, i18n keys), and CI wiring. Use when creating a new runtime SDK, bumping an SDK version, or auditing that all integration points are connected.

SDK Release Checklist

Mandatory steps when adding a new SDK or releasing a new version of an existing SDK. Prevents drift between code, website, changelogs, and CI.

When to Use

Creating a new runtime SDK (e.g., Go, Java, Ruby)
Releasing a new version of any existing SDK (.NET, Python, Node.js)
Auditing that an SDK is fully wired into the website and build system
After a version bump to verify all integration points are updated

New SDK: Full Checklist

When adding a brand-new SDK to the project, complete every item:

1. Code & Tests

SDK source under src/sdks/{runtime}/
Unit tests under tests/sdks/{runtime}/
Acceptance tests with LocalStack + Lowkey Vault containers (see sdk-acceptance-testing skill)
README.md in SDK root with install, quick start, and API reference

2. Version Source File

Every SDK must have a canonical version source read at build time:

Runtime	File	Field / Tag
.NET	`src/sdks/dotnet/Envilder.csproj`	`<Version>X.Y.Z</Version>`
Python	`src/sdks/python/pyproject.toml`	`version = "X.Y.Z"`
Node.js	`src/sdks/nodejs/package.json`	`"version": "X.Y.Z"`
Go	Git tag / `go.mod` convention	`vX.Y.Z` tag
Java	`pom.xml` or `build.gradle`	`<version>` / `version =`

3. Website: Version Badge Wiring

The website reads SDK versions at build time via astro.config.mjs:

Add version extraction in src/website/astro.config.mjs:
- For package.json: read + JSON.parse (see Node.js SDK pattern)
- For .csproj: use extractCsprojVersion() helper (regex on <Version>)
- For pyproject.toml: use extractPyprojectVersion() helper (regex)
Add Vite define global: __SDK_{RUNTIME}_VERSION__
Declare in src/website/src/env.d.ts: declare const __SDK_{RUNTIME}_VERSION__: string;
Use dynamic variable in DocsContent.astro badge (never hardcode versions)

4. Website: Documentation Page Section

Add SDK section in src/website/src/components/DocsContent.astro (install command, quick start code, badge, link to full docs)
Add i18n keys to src/website/src/i18n/types.ts for all new strings
Add translations to every locale file: en.ts, ca.ts, es.ts

5. Website: Changelog Integration

Create docs/changelogs/sdk-{runtime}.md with initial release entry
Read changelog in astro.config.mjs via readChangelog() helper
Add Vite define global: __CHANGELOG_SDK_{RUNTIME}__
Declare in env.d.ts: declare const __CHANGELOG_SDK_{RUNTIME}__: string;
Add product entry to products array in all 3 changelog pages:
- src/website/src/pages/changelog.astro
- src/website/src/pages/ca/changelog.astro
- src/website/src/pages/es/changelog.astro
Add sidebar nav block (button + version list) in the SDKs group for all 3 changelog pages: maintain correct parsed[N] indices
Add i18n key categorySdk{Runtime} to types.ts and all locale files
Add to mobile product selector dropdown (automatic if in products array)

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

6. Website: SDK Cards Component

Add card in src/website/src/components/Sdks.astro with install command and package manager link

7. Copilot Instructions & Build Config

Update .github/copilot-instructions.md with SDK architecture notes
Add to pnpm-workspace.yaml if TypeScript/Node-based
Add build/test commands to CI workflow

8. Documentation Cross-References

Add SDK to root README.md SDK section
Add SDK to ROADMAP.md if tracked there
Add to docs/changelogs/ index if one exists
Run doc-sync skill to verify alignment

Existing SDK: Version Bump Checklist

When releasing a new version of an already-wired SDK:

Bump version in the canonical source file (csproj / pyproject.toml / package.json)
Add changelog entry to docs/changelogs/sdk-{runtime}.md
Verify pnpm build in src/website/ picks up the new version automatically
No manual edits needed in DocsContent.astro (version is dynamic)

Validation

After completing the checklist:

bash

# Build website and verify all versions render
cd src/website && pnpm build

# Grep built HTML for version badges
node -e "const h=require('fs').readFileSync('dist/docs/index.html','utf-8'); \
  console.log(h.match(/NuGet v[\d.]+/)?.[0]); \
  console.log(h.match(/PyPI v[\d.]+/)?.[0]); \
  console.log(h.match(/npm v[\d.]+/)?.[0])"

# Verify changelog page includes all SDKs
node -e "const h=require('fs').readFileSync('dist/changelog/index.html','utf-8'); \
  console.log('dotnet:', h.includes('sdk-dotnet')); \
  console.log('python:', h.includes('sdk-python')); \
  console.log('nodejs:', h.includes('sdk-nodejs'))"

Common Pitfalls

Pitfall	Prevention
Hardcoded version in badge	Always use `__SDK_*_VERSION__` globals
Missing changelog sidebar entry	Check all 3 locale pages, not just `en`
Wrong `parsed[N]` index after adding SDK	Count products array entries carefully
Forgot i18n key in one locale	Add to `types.ts` first: TypeScript errors catch missing keys
Version not updating after bump	Restart dev server (Vite caches `define` values)

Files

Just SKILL.md in .github/skills/sdk-release-checklist of macalbert/envilder.

Open the folder on GitHubat commit b6a0327

Compare with similar skills

SDK Release Checklist 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.

SDK Release Checklist compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
SDK Release Checklist this skillmacalbert/envilder	138	—	~1.5k	Automated safety check: Pass	MIT	3 days ago
Release Skillsnexmoe/eve	421	3 repos	~3.3k	Automated safety check: Pass	None	6 mo ago
Generate Readmemicrosoft/Agent365-Samples	112	—	~2.6k	Automated safety check: Notes	MIT	7 days ago
Universal Project Release WorkflowJimLiu/baoyu-skills	26k	—	~4.9k	Automated safety check: Pass	MIT	28 days ago
Dt Obs ServicesDynatrace/dynatrace-for-ai	161	—	~3.3k	Automated safety check: Pass	Apache-2.0	7 days ago
Herdr Pre-Release Auditherdrdev/herdr	43k	—	~289	Automated safety check: Pass	Apache-2.0	today

Similar skills

Release Skills
nexmoe/eve
Universal release workflow. An agent skill from nexmoe/eve.
421 GitHub starsUsed in 3 repos~3.3k tokens
DevelopmentAuto-check passed
Generate Readme
microsoft/Agent365-Samples
Official
Generates or updates a README.md for an Agent 365 sample agent.
112 GitHub stars~2.6k tokensUpdated 7 days ago
DevelopmentAuto-check: notes
Universal Project Release Workflow
JimLiu/baoyu-skills
Detects a project's version file and changelog format, then runs a release: bumping the version, writing release notes and creating GitHub releases, including backfill.
26k GitHub stars~4.9k tokensUpdated 28 days ago
DevelopmentAuto-check passed
Dt Obs Services
Dynatrace/dynatrace-for-ai
Service performance monitoring with RED metrics (Rate, Errors, Duration) and runtime-specific telemetry for Java, .NET, Node.js, Python, PHP, and Go.
161 GitHub stars~3.3k tokensUpdated 7 days ago
DevOps & CloudAuto-check passed
Herdr Pre-Release Audit
herdrdev/herdr
Audit herdr release readiness by comparing commits since the base release against next-release changelog and docs. Use when asked to run or apply the repo's…
43k GitHub stars~289 tokensUpdated today
DevelopmentAuto-check passed
Megaphone Release
Kuberwastaken/megaphone
Prepare, validate, publish, and verify Megaphone releases. An agent skill from Kuberwastaken/megaphone.
169 GitHub stars~1.3k tokensUpdated 2 mo ago
DevelopmentAuto-check passed

Questions about SDK Release Checklist

What does SDK Release Checklist do?

Checklist for adding a new SDK or releasing a new SDK version. SDK Release Checklist is an agent skill from macalbert/envilder. Checklist for adding a new SDK or releasing a new SDK version.

When should I use SDK Release Checklist?

SDK Release Checklist fits situations like: creating a new runtime SDK; bumping an SDK version; auditing that all integration points are connected.

How do I install SDK Release Checklist in Claude Code?

Run `npx skills add macalbert/envilder --skill sdk-release-checklist -a claude-code`. Or copy the skill folder (.github/skills/sdk-release-checklist in macalbert/envilder) into .claude/skills/sdk-release-checklist in your project. Claude Code loads it when a task matches its description.

How do I install SDK Release Checklist in Codex?

Run `npx skills add macalbert/envilder --skill sdk-release-checklist -a codex`. Or copy the skill folder (.github/skills/sdk-release-checklist in macalbert/envilder) into .agents/skills/sdk-release-checklist in your project. Codex loads it when a task matches its description.

Can I use SDK Release Checklist 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 macalbert/envilder --skill sdk-release-checklist -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sdk-release-checklist, .gemini/skills/sdk-release-checklist, .github/skills/sdk-release-checklist and .opencode/skills/sdk-release-checklist in your project.

What does SDK Release Checklist need to run?

Going by SKILL.md and its folder, SDK Release Checklist needs the command-line tools its instructions call (pnpm, node and npm). Our summary lists: Python 3; Node.js.

Does SDK Release Checklist access the network?

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

Is SDK Release Checklist 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 SDK Release Checklist use?

SDK Release Checklist 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 SDK Release Checklist use?

About 1.5k tokens (SKILL.md is roughly 5.8k 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 SDK Release Checklist?

Skills that share tags, products or a category with SDK Release Checklist: Release Skills (nexmoe/eve, 421 stars), Generate Readme (microsoft/Agent365-Samples, 112 stars), Universal Project Release Workflow (JimLiu/baoyu-skills, 26k stars) and Dt Obs Services (Dynatrace/dynatrace-for-ai, 161 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains SDK Release Checklist?

macalbert (a GitHub user) maintains it in macalbert/envilder, which has 138 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 5, 2026.

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

Install SDK Release Checklist

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

SDK Release Checklist

When to Use

New SDK: Full Checklist

1. Code & Tests

2. Version Source File

3. Website: Version Badge Wiring

4. Website: Documentation Page Section

5. Website: Changelog Integration

6. Website: SDK Cards Component

7. Copilot Instructions & Build Config

8. Documentation Cross-References

Existing SDK: Version Bump Checklist

Validation

Common Pitfalls

Files

Compare with similar skills

Similar skills

More from macalbert/envilder

Related

Questions about SDK Release Checklist