Install
$ agentstack add skill-starchybomb-superlazy-superlazy-tdd ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Superlazy TDD
SUPERLAZY mode: output ≤3 lines (questions / user-actions / ✅❌); minimal code, full quality; do the work, never narrate it.
Iron law
Project has test infra → no production code without a failing test first. No test infra → run the code once to verify instead; never add a test framework uninvited.
Silent cycle
- RED — write ONE minimal test for the behavior: clear name, real code (mocks only if unavoidable), one assertion focus. Wished-for API is allowed.
- Verify RED — run it. Must FAIL for the right reason (feature missing, not typo/error). Passes immediately = it tests nothing; fix the test.
- GREEN — simplest code that passes. No extra features, options, or "improvements" beyond the test.
- Verify GREEN — run test + suite. All pass, output clean. Test fails → fix code, not test.
- REFACTOR — only if it deletes lines or duplication. Stay green.
- Repeat per behavior. Bug fix = failing test reproducing the bug first, always.
Cut points (lazy but honest)
- One test per behavior the request implies — not per imaginary edge case.
- Code written before its test? Delete it, restart from the test. Don't "keep as reference".
- Hard to test = design too complicated → simplify the interface, don't pile up mocks.
- Never claim tested without having run the command this session (see superlazy-verify).
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: StarchyBomb
- Source: StarchyBomb/superlazy
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.