agentsclimarketplace
Sign in

Amadeus build and test

Skill amadeus-dlc/amadeus/dist/codex/.agents/skills/amadeus-build-and-test

Run the AI-DLC `build-and-test` stage (construction phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage build-and-test --single`: the engine emits one run-stage directive for build-and-test 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.From its SKILL.md

Install
npx -y skills add amadeus-dlc/amadeus --skill amadeus-build-and-test

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.

SKILL.md

1.6 KB, 286 tokens by cl100k_base, as published. Nobody here has run it

AI-DLC Stage Runner — build-and-test

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

Steps

  1. Ask the engine for the single-stage directive:

    bun .codex/tools/amadeus-orchestrate.ts next --stage build-and-test --single

    The engine emits one run-stage directive for build-and-test (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.

  2. When the stage's work is done, commit the single-stage record:

    bun .codex/tools/amadeus-orchestrate.ts report --single --stage build-and-test --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 test skills give in 286 tokens

Counted across 964 of the 1,571 authors here whose files we hold, read 2026-08-07

  • Close the browser when donein 55 of 964, across 12 files
  • Wait for network idle statein 51 of 964, across 6 files
  • Launch Chromium in headless modein 49 of 964, across 6 files
  • Use descriptive selectors for elementsin 49 of 964, across 6 files
  • Run provided scripts with help flag firstin 49 of 964, across 6 files
  • Add appropriate explicit waitsin 48 of 964, across 5 files
  • Use bundled scripts as black boxesin 46 of 964, across 3 files
  • Do not read script source codein 46 of 964, across 3 files
  • Use sync playwright for scriptsin 46 of 964, across 3 files
  • Inspect dom before executing actionsin 46 of 964, across 3 files
  • Run the full test suitein 37 of 964
  • Write the failing test firstin 29 of 964, across 23 files

Said here and by no other author read

  • run the single-stage build-and-test directive
  • execute the stage exactly as the directive describes
  • commit the single-stage record after stage work

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.

Keep looking

Skills are one crate of 326,852. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.