agentsclimarketplace

Grill

Skill Aquish-Lee/agent-handrails/skills/grill

Explicit, claim-scaled engineering handrails for AI coding agents.

Install
npx -y skills add Aquish-Lee/agent-handrails --skill grill

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

2 things to look at

  • 25 days oldThe repository was created 25 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 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

Interrogate consequential uncertainty when a user explicitly asks for rigorous clarification or a non-trivial task has unresolved goals, constraints, tradeoffs, or acceptance signals. Skip settled work and low-cost micro-decisions.

SKILL.md

2.2 KB, 402 tokens by cl100k_base, as published. Nobody here has run it

Grill

Resolve only the uncertainty that could materially change the outcome, architecture, authorization, or verification strategy.

<!-- handrails-contract contract: usable-loop/v2 role: outcome-aligner reference: references/usable-loop-v2.md runtime: none -->

Read the local v2 contract for the full Alignment Snapshot and Outcome Reference shapes.

Calibrate the questioning

Do not question for ceremony. Skip or stop when the task is already decision-complete. Focus on uncertainties with high consequence and low reversibility:

  • what result must be true for the user;
  • who or what has authority to define that result;
  • constraints, non-goals, compatibility, and safety boundaries;
  • the tradeoff between plausible approaches;
  • observable acceptance and failure signals.

Ask one compact cluster at a time. Explain why an answer changes the design when that is not obvious. Use repository evidence for discoverable facts instead of asking the user to repeat them.

Authority handling

A current request is authoritative when the user owns its scope and no source or permission conflict exists. Agent-created options and interpretations remain provisional until selected. Do not let a saved spec, plan, Capsule, or previous answer silently override the current designated authority.

Converge

When the consequential questions are settled, return a compact Alignment Snapshot:

  • Outcome Reference;
  • task shape and goal;
  • non-goals;
  • chosen direction and rejected consequential alternatives;
  • key constraints and decisions;
  • open risks or unknowns;
  • verification signals;
  • an optional suggested next handrail.

A suggestion is not an invocation. Do not create a spec or plan unless the user asked for one. For a micro-task, a short conversational alignment is enough.

Direct result

Lead with the resolved decision, then remaining material uncertainty and its impact. Expand a full Checkpoint only for a continuity trigger.

What ships with it: 2 files

2.9 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 328,083. 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.