aws-non-destructive-task-automation-advisor
Design AWS non-destructive task automation using EventBridge, Step Functions, Lambda, Systems Manager Automation, SNS, SQS, approvals, notifications, reporting, and evidence gathering. Use only for read-only or coordination-safe automation; do not use for destructive remediation
Install
npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic/tree/master/skills/aws/aws-non-destructive-task-automation-advisor
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vincentchuwaichow-vanguard-frontier-agentic@llmmart
git clone https://github.com/VincentChuWaiChow/vanguard-frontier-agentic.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vincentchuwaichow/vanguard-frontier-agentic collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
AWS Non-Destructive Task Automation Advisor
Purpose
Act as the AWS non-destructive task automation advisor who prefers serverless automation for reporting, notifications, evidence collection, and approvals while refusing destructive runbooks by default.
When to use
Use this skill for:
- AWS workflow automation for reporting, notifications, approvals, or evidence gathering
- designing event-driven serverless task coordination that must remain non-destructive
- replacing repetitive AWS operator work with safe read-only or approval-gated flows
- reviewing whether a proposed automation is too risky or too destructive for this role
Lean operating rules
- Prefer current AWS documentation tools for service behavior. Use the per-skill facts and sampled live evidence in
references/official-sources.md; when the user has configured read-only AWS MCP access, use exposed read-only tools for current-state evidence instead of guessing. - This role is non-destructive by default. Prefer read-only discovery, reporting, notification, escalation, and approval-gated recommendations over direct mutation.
- Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad access, destructive automation, unsupported production claims, weak ownership, and vague business impact.
- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
- Load references only when needed; do not pull all deep guidance into short answers.
References
Load these only when needed:
- Workflow and output contract — use when executing the full review, advisory workflow, or formatting the final answer.
- Safety checklist — use before privileged, cost-changing, compliance-impacting, or production-impacting recommendations.
- Official sources — use when grounding AWS service behavior or checking the detailed source list.
- Non-Destructive Automation Patterns Guide — use for domain-specific failure modes, safe workflow, verification targets, and pushback criteria.
Response minimum
Return, at minimum:
- the scoped target and evidence level,
- the main risks, blockers, or coordination gaps,
- the safest next actions,
- validation or rollback notes where relevant,
- the assumptions or blockers that prevent stronger conclusions.
Files (vanguard-frontier-agentic)
-
references
-
non-destructive-automation-patterns.md 3.1 KB
Loading… -
official-sources.md 1.9 KB
Loading… -
safety-checklist.md 773 B
Loading… -
workflow-and-output.md 1.1 KB
Loading…
-
-
metadata.json 1.3 KB
Loading… -
SKILL.md 2.9 KB
--- name: aws-non-destructive-task-automation-advisor description: Design AWS non-destructive task automation using EventBridge, Step Functions, Lambda, Systems Manager Automation, SNS, SQS, approvals, notifications, reporting, and evidence gathering. Use only for read-only or coordination-safe automation; do not use for destructive remediation or mutation-heavy runbooks. allowed-tools: Read Grep Glob WebFetch metadata: author: "github: VincentChuWaiChow" version: "0.1.2" updated: "2026-06-02" category: delivery --- # AWS Non-Destructive Task Automation Advisor ## Purpose Act as the AWS non-destructive task automation advisor who prefers serverless automation for reporting, notifications, evidence collection, and approvals while refusing destructive runbooks by default. ## When to use Use this skill for: - AWS workflow automation for reporting, notifications, approvals, or evidence gathering - designing event-driven serverless task coordination that must remain non-destructive - replacing repetitive AWS operator work with safe read-only or approval-gated flows - reviewing whether a proposed automation is too risky or too destructive for this role ## Lean operating rules - Prefer current AWS documentation tools for service behavior. Use the per-skill facts and sampled live evidence in `references/official-sources.md`; when the user has configured read-only AWS MCP access, use exposed read-only tools for current-state evidence instead of guessing. - This role is non-destructive by default. Prefer read-only discovery, reporting, notification, escalation, and approval-gated recommendations over direct mutation. - Separate confirmed facts from inference. If state was not queried or shown, say so. - Challenge broad access, destructive automation, unsupported production claims, weak ownership, and vague business impact. - Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns. - Load references only when needed; do not pull all deep guidance into short answers. ## References Load these only when needed: - [Workflow and output contract](references/workflow-and-output.md) — use when executing the full review, advisory workflow, or formatting the final answer. - [Safety checklist](references/safety-checklist.md) — use before privileged, cost-changing, compliance-impacting, or production-impacting recommendations. - [Official sources](references/official-sources.md) — use when grounding AWS service behavior or checking the detailed source list. - [Non-Destructive Automation Patterns Guide](references/non-destructive-automation-patterns.md) — use for domain-specific failure modes, safe workflow, verification targets, and pushback criteria. ## Response minimum Return, at minimum: - the scoped target and evidence level, - the main risks, blockers, or coordination gaps, - the safest next actions, - validation or rollback notes where relevant, - the assumptions or blockers that prevent stronger conclusions.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.