Amadeus performance validation

Skill amadeus-dlc/amadeus/dist/kimi/.kimi-code/skills/amadeus-performance-validation

Agent skills, templates, examples, validators, and docs for operating Amadeus DLC, a lifecycle contract for AI driven software development.

Install

npx -y skills add amadeus-dlc/amadeus --skill amadeus-performance-validation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Run the AI-DLC `performance-validation` stage (operation phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage performance-validation --single`: the engine emits one run-stage directive for performance-validation and its gate, the conductor runs it, then the single-stage run commits a synthetic-id pair and stops. The main workflow's Current Stage is never touched.

SKILL.md

1.7 KB, 282 tokens by cl100k_base, as published. Nobody here has run it

AI-DLC Stage Runner — performance-validation

Run the performance-validation stage on its own. This is opt-in packaging over /amadeus --stage performance-validation --single; the same stage is always reachable via that flag without this skill.

Steps

Ask the engine for the single-stage directive:
```
bun .kimi-code/tools/amadeus-orchestrate.ts next --stage performance-validation --single
```
The engine emits one run-stage directive for performance-validation (carrying the lead agent, the resolved consumes/produces paths, the rules and sensors in context, and — on this first directive — the conductor persona). Run the stage exactly as the directive describes; do not load the conductor persona by hand, the engine delivers it.
When the stage's work is done, commit the single-stage record:
```
bun .kimi-code/tools/amadeus-orchestrate.ts report --single --stage performance-validation --result completed
```
This records a STAGE_STARTED / STAGE_COMPLETED pair under a synthetic workflow id and stops. It NEVER writes the main workflow's Current Stage — a single-stage run is isolated by design (the tool refuses to advance the main workflow).

Gives 0 of the 12 instructions most quality gates skills give in 282 tokens

Counted across 1,195 of the 2,094 authors here whose files we hold, read 2026-08-07

Read the output and check the exit codein 54 of 1195, across 14 files
Verify requirements using a line-by-line checklistin 53 of 1195, across 12 files
Identify the verification command proving the claimin 51 of 1195, across 12 files
Run the full verification commandin 50 of 1195, across 11 files
Verify output confirms the claimin 49 of 1195, across 12 files
Check version control diff after agent delegationin 46 of 1195, across 6 files
State claim with evidencein 44 of 1195, across 4 files
Run the test suitein 33 of 1195, across 26 files
Keep state in memory by defaultin 27 of 1195, across 6 files
Make prototype runnable with one commandin 26 of 1195, across 5 files
Produce a verification reportin 25 of 1195, across 14 files
Detect the package manager from lockfilesin 24 of 1195, across 5 files

Said here and by no other author read

ask the engine for the single-stage directive
run the stage exactly as the directive describes
commit the single-stage record when work is done

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.