Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Agent Framework Python Release · microsoft | DecimalAI

devopsby microsoft

Agent Framework Python Release

microsoft/agent-framework-py-release

Source microsoft/agent-framework ↗License MIT

Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle tiers (alpha, beta, rc, released) with CHANGELOG-driven selective bumps, floor bound checks, and post-bump validation.

SkillScore73Maintained

Automatic

DevOps & SRE pack

Last verified 8/29/2026

What it changes

Passed 14 of 19 test cases with the skill, and 3 of 19 without it.

Without skill18%

With skill73%

Checks it passed that the model alone missed

Rejects using git describe to find the compare base tag.
Rejects universal lockstep bumping across unchanged packages.
Prohibits renaming or overwriting existing CHANGELOG section headers.

and 18 more in the full report

12 fixed4 passed either way6 still failing0 broke

Pass-rate lift: +55 pp
Tokens: +275%
Agent turns: 0%
Response time: -49%

Model gemini-3.6-flashMeasured 8/29/2026v1 · latest is v316 of 22 cases passed with skill · 19 comparable

Tokens, turns and time describe resource use, not a dollar price.

This benchmark measured an earlier version of the skill.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/microsoft-agent-framework-py-release/SKILL.md https://app.decimal.ai/s/microsoft-agent-framework-py-release/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add microsoft-agent-framework-py-release, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/microsoft-agent-framework-py-release/ and pins it in .decimal/skills.lock

decimalai skills add microsoft-agent-framework-py-release

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/microsoft-agent-framework-py-release/SKILL.md https://app.decimal.ai/s/microsoft-agent-framework-py-release/SKILL.md

Raw file: /s/microsoft-agent-framework-py-release/SKILL.md ↗ · machine-readable summary at /s/microsoft-agent-framework-py-release.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 12

Prompt

We are cutting release 1.7.0 which advances from 1.6.0. How should the reference links at the bottom of python/CHANGELOG.md be modified?

What was checked, without and with the skill
Checked	Without skill	With skill
Specifies inserting a new link for version 1.7.0 comparing python-1.6.0 to python-1.7.0.	Missed	Passed
Requires updating the Unreleased compare link to compare python-1.7.0 to HEAD.	Missed	Passed

case-12 · gemini-3.6-flash · 8/29/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md402 linessingle file

Agent Framework Python Release

Cuts a Python release PR for the microsoft/agent-framework monorepo.

Core principle: CHANGELOG drives bumps

No more universal lockstep. A package only bumps if it has a CHANGELOG entry this cycle. Draft the CHANGELOG first, then derive the bump list from it.

Exceptions to selective bumping (these stay coupled regardless of per-package changes):

Root agent-framework is coupled to agent-framework-core via agent-framework-core[all]==X.Y.Z (exact pin in python/pyproject.toml). If core bumps, root bumps. Root may also bump independently for its own changes (docs/metadata/extras).
Beta-tier cohort bumps are still allowed when the user explicitly wants a fresh date stamp across all betas for cohort signaling — but this is a deliberate user decision per release, not a default.

If the user explicitly states which packages to bump (or hands over a PR list per package), treat that as authoritative.

Lifecycle tiers and version rules

Use python/.github/skills/python-package-management/SKILL.md as the source of truth for lifecycle version patterns, date-stamp cutoffs, classifier alignment, and internal dependency updates.

For release work, derive the live tier map at release time from python/PACKAGE_STATUS.md and the actual version = lines in each pyproject.toml. Do not hardcode counts — packages move between tiers.

Inputs to confirm before bumping

The changeset: explicit commits/PRs the release covers, OR derive from git log ${LAST_RELEASED_TAG}..${RELEASE_BASE} -- python/.
Per-package CHANGELOG entries: which packages will get a line in the new release section. This list IS the bump list.
Per-released-package semver bump: for each released-tier package that has a CHANGELOG entry, decide PATCH / MINOR / MAJOR.
Date stamp (only if any alpha/beta is being bumped): default from the python-package-management date-stamp rule.
Optional cohort bump?: ask if betas should all get a new date stamp regardless of per-package changes. Default: no.

If the user states target versions or a date explicitly, use exactly what they said — do not "correct" based on historical timezones.

Non-negotiable rules

Release workflow owns the CHANGELOG: individual feature/fix PRs do not edit python/CHANGELOG.md; this workflow creates the entries centrally from merged changes.
CHANGELOG-driven bumps: only packages mentioned in the new CHANGELOG section get version bumps. Exceptions: root follows core (==pin); user-opted cohort bump on betas.
Follow python-package-management for package lifecycle and versioning rules — do not duplicate those

Track record

Benchmark

14 / 19

test cases passed, vs 3 / 19 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v6 — 10/16/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

microsoft / agent-framework

python/.github/skills/agent-framework-py-release/SKILL.md

View on GitHub ↗

License MITImported 10/16/2026Version v3

More skills from the same source and nearby in the registry, with their headline benchmark lift.

Ready to supercharge your AI agents?

See it in action

What's inside

Agent Framework Python Release

Core principle: CHANGELOG drives bumps

Lifecycle tiers and version rules

Inputs to confirm before bumping

Non-negotiable rules

Track record

Benchmark

Adoption

SkillSafety

Source

Related skills