How do I install the Promotion Gate skill?

Run npx skillmds@latest add kmshihab7878/promotion-gate in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Promotion Gate safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Promotion Gate?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Promotion Gate free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Promotion Gate?

kmshihab7878 (@kmshihab7878) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Promotion Gate by kmshihab7878 — Agent Skill

Name: Promotion Gate
Author: kmshihab7878

Promotion Gate

Enforce evidence-backed promotion criteria for candidate learnings. Use when the user runs /evolution promote <id>. Wraps bin/evolve-promote.sh and explains why each gate passed or failed. Never promotes on its own judgment — always runs the script.

kmshihab7878 Updated Sep 17, 2026

File contents

promotion-gate

When to use

/evolution promote <candidate-id> — user explicitly requests promotion.
Before manual editing of stable/global.md — to confirm a proposed edit would have passed the gate.

Protocol

Identify the candidate file: ~/.claude/evolution/candidates/<id>.yaml.
Run gate check: bash ~/.claude/evolution/bin/evolve-promote.sh --check <id>.
Show the user each gate result (pass/fail with the specific reason).
If all gates pass AND the user confirms, run: bash ~/.claude/evolution/bin/evolve-promote.sh <id>.
Show the resulting diff of stable/global.md (or stable/by-project/<slug>.md).
Record the promotion as an evidence event (type: adaptation).

Hard rules from `config.yaml`

evidence_count ≥ min_evidence (default 3).
Distinct session_ids.length ≥ min_distinct_sessions (default 2).
Distinct project_slugs.length ≥ min_distinct_projects (default 2) — unless scope: project-specific.
last_confirmed > last_failed.
Post-promotion stable-file size ≤ startup_budget_chars (default 4000).
No contradictions with existing stable rules.

What to do on gate failure

Explain each failed gate in plain English.
Suggest what would unblock it (more evidence, wait for cross-project confirmation, condense text).
Do NOT bypass the gate. Do NOT write to stable/ manually. If the user insists, document the bypass in reports/ with reason.

Output

Plain-text verdict per gate, followed by either (a) the diff of the promoted file or (b) the blocking reasons.

Frequently asked questions