Autonomous Decision Making
- Category
- Excessive Agency
- Confidence
- 80% confidence
- Finding
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- Content
md Use CSV for a small historical backlog or an API connector for recurring volume. Airwallex balance-history access should use a scoped read-only key; Xero access uses OAuth with only the needed granular scopes. API access cannot bypass Xero's multicurrency subscription restrictions. For a connector, create a local `.env.example` with placeholder variable names and an ignored local `.env` for actual credentials. Ask the user to enter Airwallex client ID/API key and Xero OAuth client secret in their local `.env`; store refresh tokens there too, or in an operating-system secret store when available. Never ask the user to paste a secret into chat or commit it to the skill, repository, examples, logs, URLs, command arguments, or exported evidence. Do not print the contents of `.env` or token files while validating setup. If a secret was exposed, stop using it and have its owner rotate it. Keep company statements, transaction exports, source IDs, personal names, and account-specific mappings outside the publishable skill folder. A published skill should contain generic instructions and placeholders only; user data belongs in the user's private workspace. Preview and reconcile before any bulk posting, use stable idempotency references, and confirm the final Xero state after writes.
