Install any skill in seconds. Free to start, no credit card required.
Get Started Free →avizmarlon/iac-first-commit
Infrastructure-as-Code from the first commit — every new project must be rebuildable from git clone + one command, with declarative state in code and idempotent execution.
Passed 21 of 22 test cases with the skill, and 16 of 22 without it.
and 11 more in the full report
5 fixed16 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are drafting the README.md for our new Go microservice. The team lead wants the very top section of the README to be a high-level marketing summary and history of the project, placing installation instructions at the bottom. What section must appear at the top of the README?
| Checked | Without skill | With skill |
|---|---|---|
| Mandates 'How to bootstrap from zero' as the top section in README.md. | Missed | Passed |
The instructions your model reads when the skill loads.
Core principle: Every new project, from its first commit, must be fully rebuildable from zero using only git clone + a single, documented bootstrap command. All infrastructure state is declarative, version-controlled, and reproducible without tribal knowledge or manual steps.
"If another person or an AI agent needed to rebuild this project from zero right now, would git clone <repo> && ./bootstrap.sh be sufficient? Or are there undocumented, manual steps?"
If the answer is "there are manual steps," the project lacks proper IaC coverage.
Use the IaC tool native to your infrastructure platform. There is no one-size-fits-all tool — the platform dictates the choice:
| Context | Native IaC Tool | Example |
|---|---|---|
| VPS / Linux server | Ansible (configuration) + Terraform (if cloud provisioning) | ansible-playbook site.yml |
| Frontend SaaS (Next.js, Vite, etc.) | Platform config-as-code + GitHub Actions | Vercel/Netlify/Cloudflare Pages deployment config |
| Serverless APIs (AWS Lambda, Cloudflare Workers) | SST / SAM / CDK / Wrangler | sst deploy or wrangler deploy |
| Mobile (iOS, Android, Expo) | Fastlane + EAS/Code Push config | fastlane build + eas build |
| Kubernetes | ArgoCD / Flux + Helm charts | GitOps with declarative manifests in git |
| ML / data pipelines | DVC + MLflow + Airflow DAGs | Reproducible training/inference pipelines |
| Browser extension / desktop app | Build manifest + bundler config + CI/CD | GitHub Actions release workflow |
| Static docs / sites | GitHub Actions + hosting provider config | Build → upload → serve, automated |
Key principle: Choose based on the infrastructure platform, not on what the team prefers. The tool should map 1:1 to the target platform's native declarative model.
Adapt this template to your context, but all elements should exist by first commit:
project-root/
test cases passed, vs 16 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.