manus-execution-default

Execute tasks autonomously with a decision framework and reporting protocol.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/easttxkravmaga/Claude --skill manus-execution-default
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manus-execution-default
Source: https://github.com/easttxkravmaga/Claude/tree/main/archive/manus-execution-default
Command: npx skills add https://github.com/easttxkravmaga/Claude --skill manus-execution-default

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manus execution management often stalls progress because requests for permission or confirmation interrupt flow. This Skill enforces an action-first posture so Manus completes tasks when possible, only asking for input when absolutely necessary.

Core Features & Use Cases

  • Decision framework: if Manus can complete a step without Nate, it does so and reports results; otherwise it pivots or asks one targeted question.
  • Stall protocol: when blocked, Manus seeks the next best path and avoids stopping.
  • Guardrails: requires credentials for sensitive actions, flags destructive changes, and prompts for strategic judgments only when required.
  • Reporting: consistent completion summaries and flags for open items.

Quick Start

Load this skill at the start of every session to enable action-first execution across all tasks.

Frequently Asked Questions about manus-execution-default

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

FAQPage Schema
How do I stop AI workflow execution from constantly pausing for permission?

An action-first execution framework prevents permission fatigue by enabling autonomous task completion across deployment and automation workflows, only pausing for required credentials, destructive changes, or strategic judgments.

What is the stall protocol when an autonomous workflow gets blocked?

A stall protocol prevents workflow execution from halting when blocked by automatically seeking the next best alternative path to maintain progress, only requesting user input when no autonomous options remain available.

How do I set up guardrails for autonomous task execution?

Set up guardrails by enforcing confirmation gates that require credentials for sensitive actions, flag destructive changes, and prompt for strategic judgments, ensuring autonomous execution only happens within established safe boundaries.

When do I need manual confirmation during automated workflow execution?

Manual confirmation is required during workflow execution only when a step needs specific credentials, involves destructive changes, or requires strategic human judgments that fall outside autonomous action boundaries.

Does autonomous execution work for CRM and content management tasks?

Yes, autonomous execution works for CRM and content management tasks by applying a decision framework to complete steps independently, reporting consistent summaries, and flagging open items for review.

What are the limitations of action-first execution frameworks?

Limitations of action-first execution include the inability to autonomously process actions requiring missing credentials, perform destructive changes, or make strategic judgments without hitting confirmation gates and requesting user input.