Install
$ agentstack add skill-amadeus-dlc-amadeus-amadeus-grilling ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Amadeus Grilling
Purpose
Interview the user relentlessly about every aspect of a plan, design, or decision space until agent and user reach a shared understanding — one question at a time, each with a recommended answer and its rationale.
The discipline is defined ONCE, in .codex/amadeus-common/protocols/grilling-protocol.md (§1 Dialogue Discipline, §2 The Grilling Loop, §3 Question Spec Templates). Read that file first and follow it exactly. This skill adds only the standalone-specific rules below — it does not re-define the discipline.
Classification
Read-only. This skill never advances the workflow stage pointer and never emits an audit event. It is safe to run at any point, with or without an active workflow. The workflow-only obligations in the protocol (questions file, decision/answer audit logging) do NOT apply here — everything happens in the conversation.
Standalone rules
- Subject comes from the argument: a file path or a topic. If a file
path, read it (and whatever it references) as the starting material for the Investigate step. If no argument was given, ask "What should I grill you about?" as the very first question.
- Discipline is the protocol's §1 and §2 in full: one question at a
time, recommended answer with rationale, facts self-researched with only decisions asked, estimates confirmed with a confidence level, hybrid termination ("done" at any time; continuation check at the depth guideline), and an explicitly confirmed agreement summary before closing.
- Output is terminal-only. Print the agreement summary (the full
question → decision table) to the terminal. Write it to a file ONLY when the user explicitly asks for it to be saved to a path (e.g. "save the summary to docs/plan-review.md") — the same explicit-request exception /amadeus-outcomes-pack uses. Never write anywhere unprompted.
- No enactment. Do not start implementing the plan under discussion.
The skill ends at the confirmed summary; acting on it is a separate, user-initiated step.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: amadeus-dlc
- Source: amadeus-dlc/amadeus
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.