This skill should be used when the user asks to "rollout a feature", "complete feature release", "propagate SDK feature", "track feature support", "what's missing for feature X", or mentions checking CLI/GUI/docs/blog support for SDK features. Guides agents through the multi-repository feature release workflow from SDK to docs to marketing.
SkillScore73Maintained
Automatic
◆Product Management pack
Last verified 9/29/2026
What it changes
Passed 14 of 19 test cases with the skill, and 3 of 19 without it.
Without skill14%
With skill73%
Checks it passed that the model alone missed
The response asks the user for priority ordering.
The response asks the user which components to implement.
The response includes git clone for OpenHands/growth-utils.git.
and 20 more in the full report
13 fixed3 passed either way6 still failing0 broke
Pass-rate lift
+59 pp
Tokens
+44%
Agent turns
0%
Response time
-47%
Model gemini-3.6-flashMeasured 9/29/2026v116 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 13
Prompt
In Phase 4 of an OpenHands feature release rollout proposal, what specific three criteria items must be evaluated under the assessment section?
What was checked, without and with the skill
Checked
Without skill
With skill
The assessment section evaluates overall priority, effort estimates, and component dependencies.
Missed
Passed
case-16 · gemini-3.6-flash · 9/29/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md228 linessingle file
Feature Release Rollout
This skill guides the complete feature release workflow across the OpenHands ecosystem repositories.
Overview
When a feature is implemented in the SDK, it may need propagation through several repositories:
Blog (OpenHands/growth-utils blog-post/) — Marketing and announcements
Video — Tutorial content (using ElevenLabs + Remotion)
Workflow
Phase 1: Feature Discovery
First, identify what feature(s) to analyze. The user may specify:
A release tag (e.g., v1.9.0)
A specific feature name
A PR or commit reference
A comparison between versions
For release tags:
# Clone SDK if not present
git clone https://github.com/OpenHands/software-agent-sdk.git
# View release notes
cd software-agent-sdk
git log --oneline v1.8.0..v1.9.0 # Changes between versions
git show v1.9.0 --stat # What changed in this release
For specific features:
Search the SDK codebase, examples, and changelog to understand the feature scope.