New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Acceptance Orchestrator

by sickn33 in sickn33/agentic-awesome-skills

A skill your agent uses when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.

MITAuto-check passedAgent Workflows

Install Acceptance Orchestrator

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill acceptance-orchestrator -a claude-code

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

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills acceptance-orchestrator --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/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/acceptance-orchestrator .claude/skills/acceptance-orchestrator && 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/

Facts

Skill name
acceptance-orchestrator
GitHub stars
47k
Used in
2 other repos
Token cost
~943 tokens
SKILL.md length
434 words
Files
1
Skills in repo
1,493
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.

  • Works in 6 steps: Intake → Issue gate → Execute → …
  • A coding task should be driven end-to-end from issue intake through implementation
  • SKILL.md covers Overview, When to Use, Required Sub-Skills and Inputs, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Acceptance Orchestrator is an agent skill from sickn33/agentic-awesome-skills. Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.

Its SKILL.md is about 940 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 Agent Workflows. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • A coding task should be driven end-to-end from issue intake through implementation
  • Acceptance verification with minimal human re-intervention

Example prompts

  • “/acceptance-orchestrator”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Intake
  2. Issue gate
  3. Execute
  4. Review loop
  5. Deploy and runtime verification
  6. Completion gate

What it can do on your machine

Read from SKILL.md and the folder at commit 680176d. 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

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    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

Acceptance Orchestrator loads about 943 tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 434 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~50
When it runs · the whole SKILL.md, loaded when a task matches
~943

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 sickn33/agentic-awesome-skills at commit 680176d, republished under its MIT licence (© sickn33). 434 words, ~943 tokens.

Download SKILL.mdSave it as .claude/skills/acceptance-orchestrator/SKILL.md (or your agent's skills folder).
name
acceptance-orchestrator
description
Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
risk
safe
source
community
date_added
2026-03-12

Acceptance Orchestrator

Overview

Orchestrate coding work as a state machine that ends only when acceptance criteria are verified with evidence or the task is explicitly escalated.

Core rule: do not optimize for "code changed"; optimize for "DoD proven".

When to Use

  • The task already has an issue or clear acceptance criteria and should run end-to-end with minimal human re-intervention.
  • You need structured handoff across implementation, review, deployment, and final verification.
  • You want explicit stop conditions and escalation instead of silent partial completion.

Required Sub-Skills

  • create-issue-gate
  • closed-loop-delivery
  • verification-before-completion

Optional supporting skills:

  • deploy-dev
  • pr-watch
  • pr-review-autopilot
  • git-ship

Inputs

Require these inputs:

  • issue id or issue body
  • issue status
  • acceptance criteria (DoD)
  • target environment (dev default)

Fixed defaults:

  • max iteration rounds = 2
  • PR review polling = 3m -> 6m -> 10m

State Machine

  • intake
  • issue-gated
  • executing
  • review-loop
  • deploy-verify
  • accepted
  • escalated

Workflow

  1. Intake

    • Read issue and extract task goal + DoD.

  2. Issue gate

    • Use create-issue-gate logic.
    • If issue is not ready or execution gate is not allowed, stop immediately.
    • Do not implement anything while issue remains draft.

  3. Execute

    • Hand off to closed-loop-delivery for implementation and local verification.

  4. Review loop

    • If PR feedback is relevant, batch polling windows as:
      • wait 3m
      • then 6m
      • then 10m
    • After the 10m round, stop waiting and process all visible comments together.

  5. Deploy and runtime verification

    • If DoD depends on runtime behavior, deploy only to dev by default.
    • Verify with real logs/API/Lambda behavior, not assumptions.

  6. Completion gate

    • Before any claim of completion, require verification-before-completion.
    • No success claim without fresh evidence.
Show full SKILL.md (183 more words)Show less

Stop Conditions

Move to accepted only when every acceptance criterion has matching evidence.

Move to escalated when any of these happen:

  • DoD still fails after 2 full rounds
  • missing secrets/permissions/external dependency blocks progress
  • task needs production action or destructive operation approval
  • review instructions conflict and cannot both be satisfied

Human Gates

Always stop for human confirmation on:

  • prod/stage deploys beyond agreed scope
  • destructive git/data operations
  • billing or security posture changes
  • missing user-provided acceptance criteria

Output Contract

When reporting status, always include:

  • Status: intake / executing / accepted / escalated
  • Acceptance Criteria: pass/fail checklist
  • Evidence: commands, logs, API results, or runtime proof
  • Open Risks: anything still uncertain
  • Need Human Input: smallest next decision, if blocked

Do not report "done" unless status is accepted.

Example

User request:

Take this issue and its acceptance criteria through implementation, validation, review, and a final evidence-backed verdict.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/acceptance-orchestrator of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit 680176d

Used in 2 other repositories

We found 11 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Acceptance Orchestrator 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.

Acceptance Orchestrator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Acceptance Orchestrator this skillsickn33/agentic-awesome-skills47k2 repos~943Automated safety check: PassMIT
Agentic Workflow Designerdotnet/Open-XML-SDK4.6k2 repos~3.5kAutomated safety check: PassMIT
Apex Context Managementjonathan-vella/apex217—~1.8kAutomated safety check: PassMIT
Files Memory SystemLeoYeAI/openclaw-master-skills2.2k—~3.8kAutomated safety check: PassMIT
Knowledge FeedbackStanshy/AgentHub202—~549Automated safety check: NotesMIT
Spek Planjumppad-labs/jumppad263—~2.4kAutomated safety check: PassMPL-2.0

Similar skills

  • Agentic Workflow Designer

    dotnet/Open-XML-SDK

    Official

    Interviews you one question at a time about goal, trigger, permissions and data needs, then drafts a single agentic workflow markdown file.

    4.6k GitHub starsUsed in 2 repos~3.5k tokens
    Agent WorkflowsAuto-check passed

  • Apex Context Management

    jonathan-vella/apex

    UTILITY SKILL — Two-mode context-window management. An agent skill from jonathan-vella/apex.

    217 GitHub stars~1.8k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Files Memory System

    LeoYeAI/openclaw-master-skills

    Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Agent WorkflowsAuto-check passed

  • Knowledge Feedback

    Stanshy/AgentHub

    Scan child projects for pitfalls and propose company standard updates

    202 GitHub stars~549 tokensUpdated 6 mo ago
    Agent WorkflowsAuto-check: notes

  • Spek Plan

    jumppad-labs/jumppad

    Create a new Plan from an approved Specification. An agent skill from jumppad-labs/jumppad.

    263 GitHub stars~2.4k tokensUpdated 8 days ago
    Agent WorkflowsAuto-check passed

  • Harness Engineering

    guanyang/open-agent-hub

    This skill should be used when designing autonomous agent harnesses: research loops, evaluation scaffolds, locked and editable surfaces, durable logs, novelty gates, pruning, rollback, PR…

    977 GitHub starsUsed in 1 repo~2.9k tokens
    Agent WorkflowsAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,493 skills in this repo

  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed

  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed

  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Categories

Questions about Acceptance Orchestrator

What does Acceptance Orchestrator do?

A skill your agent uses when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention. Acceptance Orchestrator is an agent skill from sickn33/agentic-awesome-skills. Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.

When should I use Acceptance Orchestrator?

Acceptance Orchestrator fits situations like: A coding task should be driven end-to-end from issue intake through implementation; acceptance verification with minimal human re-intervention.

How do I install Acceptance Orchestrator in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill acceptance-orchestrator -a claude-code`. Or copy the skill folder (skills/acceptance-orchestrator in sickn33/agentic-awesome-skills) into .claude/skills/acceptance-orchestrator in your project. Claude Code loads it when a task matches its description.

How do I install Acceptance Orchestrator in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill acceptance-orchestrator -a codex`. Or copy the skill folder (skills/acceptance-orchestrator in sickn33/agentic-awesome-skills) into .agents/skills/acceptance-orchestrator in your project. Codex loads it when a task matches its description.

Can I use Acceptance Orchestrator 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 sickn33/agentic-awesome-skills --skill acceptance-orchestrator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/acceptance-orchestrator, .gemini/skills/acceptance-orchestrator, .github/skills/acceptance-orchestrator and .opencode/skills/acceptance-orchestrator in your project.

What does Acceptance Orchestrator need to run?

SKILL.md names no scripts, command-line tools or credentials: Acceptance Orchestrator is instructions for the agent only.

Does Acceptance Orchestrator access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Acceptance Orchestrator 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 Acceptance Orchestrator use?

Acceptance Orchestrator 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 Acceptance Orchestrator use?

About 943 tokens (SKILL.md is roughly 3.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 Acceptance Orchestrator?

Skills that share tags, products or a category with Acceptance Orchestrator: Agentic Workflow Designer (dotnet/Open-XML-SDK, 4.6k stars), Apex Context Management (jonathan-vella/apex, 217 stars), Files Memory System (LeoYeAI/openclaw-master-skills, 2.2k stars) and Knowledge Feedback (Stanshy/AgentHub, 202 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Acceptance Orchestrator?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,379 GitHub stars. The repository holds 1,493 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.