modbender 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.