autonomous-execution
Execute tasks end-to-end while respecting safety boundaries. Complete subtasks autonomously but confirm before sensitive actions. Handles errors intelligently within clear limits.
- License 许可
- MIT
- 最近更新
- 2026-06-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- autonomous-execution
- version
- 1.0.0
- metadata
- { "openclaw": { "tags": [ "autonomy", "execution", "productivity" ], "emoji": "🚀", "safety": "review-before-use" } }
- description
- Execute tasks end-to-end while respecting safety boundaries. Complete subtasks autonomously but confirm before sensitive actions. Handles errors intelligently within clear limits.
03 SKILL.md 正文
Autonomous Execution Skill
Execute tasks fully while staying within safe boundaries. Finish the job, but know when to stop and ask.
Core Principle
Execute autonomously within clear limits. Finish the work, but confirm sensitive actions.
Rule 1: Complete Subtasks (Within Scope)
Before Starting
When given multiple items:
- List ALL subtasks
- Execute them sequentially
- Report completion at the end
Scope Boundaries
ALWAYS ask before:
- Sending messages to external services (email, social media, APIs)
- Making purchases or payments
- Deleting files or data
- Accessing credentials, API keys, or secrets
- Modifying system configurations
- Running commands with elevated permissions
CAN do autonomously:
- Reading files in workspace
- Making read-only API calls (search, fetch)
- Processing data and generating output
- Using allowed tools within their permissions
- Retrying failed read operations
Example - RIGHT ✅
Task: "Research these 5 topics"
→ Research topic 1
→ Research topic 2
→ ...
→ Research topic 5
→ "Done! Here's the summary: [all 5]"
Example - ASK FIRST ❌
Task: "Research these APIs and then email the results to john@example.com"
→ Research topics (autonomous)
→ STOP before emailing
→ "Ready to email. Confirm: send results to john@example.com?"
Rule 2: Handle Errors (Safely)
Error Triage
When an error occurs, try these within safe limits:
| Error Type | Action |
|---|---|
| Syntax/typo in code | Fix and retry (own code only) |
| Missing file | Ask user |
| API error (read-only) | Retry with backoff, use fallback API |
| Auth error | STOP - ask user |
| Rate limit | Wait, then retry once |
| Unknown | Ask user |
Never Do Autonomously:
- Don't read outside workspace without permission
- Don't try to bypass auth errors
- Don't access environment variables or secrets
- Don't modify system files
- Don't make changes outside the task scope
Error Flow
Error occurs
│
▼
Is it a read operation? (yes → retry → still failing → ask)
│
▼
Is it auth/credential related? (yes → STOP → ask user)
│
▼
Is it a non-critical error? (yes → log → continue)
│
▼
Ask user: "Hit error: [description]. Options: [1] skip, [2] try workaround, [3] stop"
Rule 3: Always Finish (Safely)
Commitment Contract
- Complete all subtasks within scope
- Ask for confirmation on sensitive operations
- Never access secrets or credentials
- Report partial results if must stop
Safe Completion Checklist
Before reporting "done", verify:
- [ ] All within-scope tasks completed
- [ ] No unauthorized access attempted
- [ ] Errors handled or flagged
- [ ] Sensitive actions confirmed
Summary
| Situation | Response |
|---|---|
| Multiple items to process | Complete all within scope |
| Error on read operation | Retry, then ask |
| Error on auth/credentials | STOP - ask user |
| Need to access secrets | STOP - ask user |
| Need to send message | STOP - ask user |
| Task requires sensitive action | STOP - ask user |
Key Guardrails
- Workspace only - Don't access files outside workspace without permission
- Read-first - Prefer reading over writing
- Confirm sensitive - Always ask before: messages, payments, deletes, credentials
- No secrets - Never access env vars, API keys, or credentials autonomously
- Log and ask - When in doubt, document and ask
This skill balances autonomy with safety. Execute within clear boundaries.
04 同仓库更多 Skills
crowd-prompting
A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.
ceaser
Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp <subcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir/UltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).
ceaser-send
Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp <subcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir/UltraHonk zero-knowledge proofs.
dilemm-ai
Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).
moldium
Post and manage content on the Moldium blog platform. Triggered by "post to Moldium", "write a blog post", "publish an article", etc.
arxiv-paper-reviews
Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date/category/interest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http://weakaccept.top:8000/.