CtrlK
BlogDocsLog inGet started
Tessl Logo

acceptance-orchestrator

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.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is acceptance-orchestrator in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-engineered orchestration skill: lean, state-driven, with explicit validation gates, feedback loops, and a concrete output contract. Main improvement room is in making sub-skill handoffs more concretely invocable.

Suggestions

Show how to invoke each required sub-skill (e.g. a one-line call signature or entry condition) so the handoffs are copy-paste actionable rather than named-only.

Optionally externalize the state-machine / polling-default tables into a reference file once the body grows, to keep SKILL.md as a pure overview.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — every line is actionable (state names, polling windows, defaults, gates) with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Concrete, actionable guidance throughout — fixed defaults (2 rounds, 3m→6m→10m polling), an explicit output contract, and named sub-skill handoffs — with minor gaps in how sub-skills are concretely invoked.

4 / 5

Workflow Clarity

A numbered six-step workflow over an explicit state machine, with validation gates (issue gate, completion gate, verification-before-completion), a review feedback loop, and human gates covering destructive operations.

5 / 5

Progressive Disclosure

Well-organized into clear sections with one-level-deep sub-skill references clearly signaled (Required / Optional); content is self-contained and appropriately inline since no bundle files exist.

4 / 5

Total

18

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit trigger clause and a concrete enumeration of the orchestration lifecycle. It could be sharpened with more user-natural synonyms and a slightly tighter distinctiveness signal.

Suggestions

Add common synonyms users actually say, e.g. "ticket", "ship", "definition of done / DoD", alongside "issue intake" and "acceptance verification".

Tighten the distinctiveness signal by foregrounding the acceptance-evidence / DoD-proven framing that separates this from a generic delivery skill.

DimensionReasoningScore

Specificity

Enumerates multiple concrete lifecycle stages — "issue intake through implementation, review, deployment, and acceptance verification" — giving comprehensive coverage of the orchestration domain rather than vague abstraction.

5 / 5

Completeness

It explicitly answers both what (end-to-end orchestration across the listed stages) and when via a concrete "Use when a coding task should be driven end-to-end..." trigger clause.

5 / 5

Trigger Term Quality

Natural terms like "coding task", "issue intake", "review", "deployment", and "acceptance verification" are present, but common synonyms users say ("ticket", "ship", "definition of done", "DoD") are missing.

4 / 5

Distinctiveness Conflict Risk

The acceptance-verification-driven orchestration niche is mostly distinct with clear triggers, with only minor overlap risk against general delivery or "ship this" skills.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.