core-behavior

Enforce single-step agent actions with explicit user confirmation before changes.

14|6|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/jholhewres/devclaw --skill core-behavior
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: core-behavior
Source: https://github.com/jholhewres/devclaw/tree/main/pkg/devclaw/copilot/builtin/skills/core-behavior
Command: npx skills add https://github.com/jholhewres/devclaw --skill core-behavior

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides explicit rules and a decision flow to prevent agents from performing unrequested actions, executing multiple tasks at once, using incorrect tools, or making significant changes without confirmation, reducing mistakes and unwanted side effects.

Core Features & Use Cases

  • Single-action execution: Force agents to complete one explicit task before starting another to avoid multi-step surprises.
  • Confirmation for significant actions: Require explicit user consent before creating, deleting, or modifying schedules, files, data, or configurations.
  • Tool selection validation: Map tasks to the correct tools (for example, spawn_subagent for subagents, scheduler for reminders, send_document for sending files) to avoid misuse.
  • Structured response pattern and checklist: Follow Understand → Identify → Execute → Confirm with a pre-action checklist and progress updates for long tasks.
  • Use Case: When asked to generate and deliver a PDF report, the agent will generate the file, confirm creation, send the document, and then confirm delivery rather than performing all steps implicitly.

Quick Start

Apply the core behavior guidelines by executing only the requested task, choosing the correct tool, performing one action at a time, and confirming before making changes.

Frequently Asked Questions about core-behavior

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

FAQPage Schema
How do I prevent AI agents from performing unrequested actions or multi-step side effects?

To prevent unrequested actions, you can enforce single-action execution and require explicit user confirmation before any creation, deletion, or modification. This ensures agents complete one explicit task before starting another.

How do I require explicit confirmation for file operations and scheduling in conversational AI?

You require explicit confirmation for file operations and scheduling by applying a structured decision flow that mandates user consent before creating, deleting, or modifying schedules, files, data, or configurations.

What is the best way to validate tool selection for subagent orchestration and document sending?

Validating tool selection for subagent orchestration involves mapping tasks to the correct tools, such as spawn_subagent for subagents and send_document for sending files, ensuring agents avoid tool misuse.

How does the understand, identify, execute, confirm pattern work for safe agent behavior?

The understand, identify, execute, confirm pattern works by following a structured response flow with a pre-action checklist and progress updates, ensuring predictable, single-step responses for long tasks.

Why does my AI agent execute multiple tasks at once instead of waiting for confirmation?

Your AI agent executes multiple tasks at once because it lacks single-action execution constraints. Forcing agents to complete one explicit task before starting another prevents multi-step surprises and unwanted side effects.

Can I use single-task enforcement for agents handling document sending and file modifications?

Yes, you can use single-task enforcement for agents handling document sending and file modifications. It requires explicit user confirmation for any creation, deletion, or modification to prevent unwanted side effects.