Skills release-orchestrator

📦

release-orchestrator

Name: release-orchestrator
Author: yaojingang

Content revision r1 Safe ⚙️ External commands

Build Release Readiness Packets

Release teams often have scattered notes, unclear rollback criteria, and missing communication plans. This skill turns those inputs into a structured release packet with readiness gates and go/no-go guidance.

Supports: Claude Codex Code(CC)

🥈 82 Silver

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "release-orchestrator" from https://skillstore.io/skills/yaojingang-release-orchestrator.md and its manifest at https://skillstore.io/api/skills/yaojingang-release-orchestrator/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/yaojingang-release-orchestrator.md Signed manifest GET /api/skills/yaojingang-release-orchestrator/manifest Signed lockfile GET /api/skills/yaojingang-release-orchestrator/lockfile

Test it

Using "release-orchestrator". Scattered notes for a search service migration and staged rollout.

Expected outcome:

Scope summary for the search hardening release.
Risk block with high migration timing risk and medium latency risk.
Rollout, rollback, stakeholder messages, and GO WITH CONDITIONS decision.

Using "release-orchestrator". Release readiness review with missing rollback criteria.

Expected outcome:

The skill reports the missing rollback trigger as a blocker and recommends NO-GO until criteria are defined.

Using "release-orchestrator". Customer-facing feature release with support and leadership updates.

Expected outcome:

Audience-specific communication plan for support and leadership.
Release window, impact surface, escalation signal, and final decision summary.

Security Audit

Safe

v5 • 7/8/2026 Open versioned report

All ten static findings are markdown inline-code false positives in SKILL.md. They refer to local files, a local packet-rendering helper, or literal output labels; I found no prompt injection, command execution intent, network use, or secret access.

Files scanned

386

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (10)

SKILL.md:29 SKILL.md:30 SKILL.md:31 SKILL.md:51 SKILL.md:63 SKILL.md:64 SKILL.md:65 SKILL.md:66 SKILL.md:67 SKILL.md:68

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/yaojingang-release-orchestrator/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/yaojingang-release-orchestrator/security.svg)](https://skillstore.io/skills/yaojingang-release-orchestrator?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/yaojingang-release-orchestrator?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/yaojingang-release-orchestrator/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/yaojingang-release-orchestrator.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

yaojingang. (2026). release-orchestrator security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/yaojingang-release-orchestrator/audits/5

BibTeX citation

@techreport{yaojingang-yaojingang-release-orchestrator-2026,
  author = {yaojingang},
  title = {release-orchestrator security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/yaojingang-release-orchestrator/audits/5},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "release-orchestrator security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
  - name: "yaojingang"
date-released: "2026-07-08"
url: "https://skillstore.io/skills/yaojingang-release-orchestrator/audits/5"
identifiers:
  - type: other
    value: "skillstore:yaojingang-release-orchestrator:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Readiness Review

Turn scattered launch notes into one packet before an approval meeting.

Migration Launch Planning

Verify migration timing, rollback expectations, and operator warnings before traffic shift.

Stakeholder Alignment

Prepare audience-specific messages tied to release timing and risk.

Try These Prompts

Create Basic Packet

Prepare a release packet from these notes. Include scope, risks, migrations, rollout, rollback, stakeholder messages, and a final decision.

Check Readiness

Review this planned release for readiness. Flag missing inputs, unresolved risks, weak rollback criteria, and the recommended go or no-go decision.

Add Migration Detail

Build a release packet for this schema change. Include timing, rollback safety, owner warnings, and communication needs.

Coordinate Complex Rollout

Turn these service, migration, risk, rollout, rollback, and audience notes into a final release packet. Mark conditions required before approval.

Best Practices

Provide migration details, rollback thresholds, monitoring signals, and named owners before requesting a final decision.
Treat unresolved high or critical risks as blockers unless mitigations and gates are explicit.
Review the stakeholder communication block with each audience owner before release approval.

Avoid

Do not ask for a GO decision when rollback triggers or migration timing are unknown.
Do not use the skill for a single announcement without a release packet workflow.
Do not treat generated packets as a substitute for deployment checks or human approval.