grounding-before-action

Enforce solo tool calls and echo-back before follow-on actions.

4|1|Updated Feb 4, 2024
One-click install
npx skills add https://github.com/Arx-Game/arxii --skill grounding-before-action
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grounding-before-action
Source: https://github.com/Arx-Game/arxii/tree/main/tools/skills/grounding-before-action
Command: npx skills add https://github.com/Arx-Game/arxii --skill grounding-before-action

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents AI confabulation by enforcing a solo tool call and waiting for the real results before composing any follow-on actions.

Core Features & Use Cases

  • Solo AskUserQuestion emissions to avoid bundling with tool results.
  • Post-result echo-back and validation before irreversible actions.
  • Clear guardrails for sequential reads and writes, and for verifying target references.

Quick Start

Always emit an AskUserQuestion in its own turn, then wait for the observed results before composing any further actions.

Frequently Asked Questions about grounding-before-action

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent AI confabulation when using tool results in a workflow?

To prevent AI confabulation, enforce a solo tool call and wait for the real observed results before composing any follow-on actions or statements about tool outputs. This ensures the AI relies on actual data.

What is the best way to emit AskUserQuestion without bundling it with tool results?

The best way to emit AskUserQuestion is in its own dedicated turn. By separating the question emission from other tool calls, you prevent context bundling and ensure clear user interaction before proceeding.

How do I verify targets before making irreversible mutations in an AI workflow?

To verify targets before irreversible mutations, enforce a post-result echo-back and validation step. The AI must echo back the observed results and verify target references before executing any sequential writes or edits.

Do I need to wait for tool outputs before composing follow-on actions?

Yes, you must wait for tool outputs before composing follow-on actions. The workflow requires sequential reads and writes, meaning all statements about tool outputs must come after actually observing those real results.

What guardrails are needed for sequential reads and writes in AI tool use?

Guardrails for sequential reads and writes require verifying target references and titles before any edits. This prevents premature mutations by enforcing post-result echo-back and validation after observing real tool outputs.

Why does my AI confabulate results when bundling multiple tool calls together?

AI confabulation occurs when tool calls are bundled because the AI attempts to compose follow-on actions without waiting for real observed results. Enforcing solo tool calls and sequential processing prevents this issue.