Amadeus observability setup

Skill amadeus-dlc/amadeus/dist/kiro/.kiro/skills/amadeus-observability-setup

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-observability-setup

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 `observability-setup` stage (operation phase) in isolation, without advancing the main workflow. Packages `/amadeus --stage observability-setup --single`: the engine emits one run-stage directive for observability-setup 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, as published. Nobody here has run it

AI-DLC Stage Runner — observability-setup

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

Steps

Ask the engine for the single-stage directive:
```
bun .kiro/tools/amadeus-orchestrate.ts next --stage observability-setup --single
```
The engine emits one run-stage directive for observability-setup (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 .kiro/tools/amadeus-orchestrate.ts report --single --stage observability-setup --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 project setup skills give

Counted across 999 of the 1,637 authors here whose files we hold, read 2026-08-06

ask one question at a timein 29 of 999, across 28 files
detect the package manager from lockfilesin 28 of 999, across 9 files
present findings to the userin 25 of 999, across 4 files
explore current repo statein 24 of 999, across 3 files
update the agent skills block in place if it existsin 24 of 999, across 3 files
install husky lint-staged and prettierin 23 of 999, across 4 files
create the lintstagedrc filein 22 of 999, across 3 files
commit all changed filesin 22 of 999, across 3 files
run lint-staged to verify it worksin 22 of 999, across 3 files
initialize huskyin 21 of 999, across 2 files
create the husky pre-commit filein 21 of 999, across 2 files
create a prettierrc file if missingin 21 of 999, across 2 files

Said here and by no other author read

ask the engine for the single-stage directive
run the stage as the directive describes
do not load the conductor persona by hand
commit the single-stage record

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.