- Home
- Skills
- DevOps & Cloud
- well-run-software
Well Run Software
Audit any repo or set up the practices that keep software shipping safely: CI, rulesets, hooks, strict lint, secrets, supply chain.
$9
Works with the AI Agents you already use
About this skill
One idea behind everything here: make the right thing the easy thing, and the wrong thing impossible. Prefer a control that tooling enforces over a rule people must remember.
| User wants | Mode |
|---|---|
| "Audit this repo", "what are we missing", "is this well run" | Audit |
| "Set up a new project", "add CI", "harden this repo" | Setup |
| A question about one practice ("how should we do code review?") | Advise: answer from references/playbook.md, the matching section only |
- Run the checker from the repo root:
It checks files, workflows and (ifbash <skill-dir>/scripts/audit.sh .ghis logged in) branch protection. It printsPASS/WARN/FAIL/SKIPlines and exits non-zero on anyFAIL. - The script covers only what a file scan can see. Then check by hand what it cannot, using
references/playbook.md:- Are tests real? Pick the riskiest check (auth, permissions) and break it on purpose. Does a test fail?
- Does anything log, print or ship a secret? Grep logging calls, and anything shipped to users (web bundles, mobile builds, binaries, published packages).
- Is deploy or release automated, and is rollback known?
- For running services: is there error tracking and uptime monitoring?
- Skip any practice that does not fit what this is (a library has no deploys, a CLI has no uptime). Say which you skipped.
- Report findings ranked by risk, not by section order. Use this priority:
- Secrets exposed (committed, logged, or shipped to users)
- Anyone can push to
mainunreviewed, or admins bypass protection - No CI gate, or CI not a required check
- Supply chain gaps: unpinned actions, no lockfile, no dependency updates
- Missing tests on security boundaries
- Everything else
- For each finding give: what is wrong, why it matters (one line), the exact fix. End with the 9-question self-audit from the playbook, answered for this repo where you can tell.
Do not change anything in Audit mode unless the user asks.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 27 days ago
- Software
Node.js
Pythonlint-staged