From sacco-skills
Structured evaluation framework for cloud architecture and infrastructure decisions. Use when choosing between technical approaches, evaluating build-vs-buy, designing cross-service integrations, selecting distribution mechanisms, or any decision involving trade-offs between security, ownership, coupling, portability, and switching costs. Triggers: "how should we...", "what's the right approach for...", "evaluate options for...", architectural proposals, infrastructure design, vendor/tool selection.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sacco-skills:sacco-architecture-evaluationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. **Gather facts** — Query APIs, read configs, check plans, inspect repo structures. Never assume org plan, runner setup, repo visibility, or existing tooling. Verify with actual data.
Problem identified
→ Gather ALL relevant facts (API calls, file reads, web searches)
→ Identify candidate approaches
→ For EACH candidate, evaluate: security | ownership | coupling | portability | switching cost
→ Eliminate candidates that violate hard constraints
→ Present remaining options with trade-offs
→ Wait for direction — do NOT start implementing
When evaluating any tool or service:
Open standards (OCI, HTTP, SQL, S3-compatible) are preferred over vendor-specific features (GitHub internal visibility, AWS-only services) unless the vendor feature solves a problem the standard cannot.
npx claudepluginhub adrien-sacco/sacco-skills --plugin sacco-skillsGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.