Surgical Implementation
Make the smallest justified code or configuration change, surface material assumptions, avoid unrelated cleanup, and define verifiable success criteria. Use when implementing features, fixes, refactors, or configuration changes in an existing repository; do not use for read-only analysis or broad rewrites the user explicitly requested.
Install
$ agentstack add skill-26zl-universal-agent-skills-surgical-implementation ✓ 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.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-26zl-universal-agent-skills-surgical-implementation) 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
Surgical Implementation
Keep every changed line traceable to the requested outcome. Match the repository before introducing a new convention.
Workflow
- Read the relevant code, local instructions, and nearby tests before choosing an approach.
- State only assumptions that could materially change the implementation. Ask when guessing would create meaningful risk.
- Define a short success condition that can be checked after the change.
- Choose the smallest design that satisfies the request and existing contracts.
- Modify only the required files. Match local naming, structure, error handling, and style.
- Remove imports or helpers made obsolete by this change. Leave pre-existing cleanup alone unless requested.
- Run focused checks against the success condition, then inspect the final diff for unrelated edits.
Guardrails
- Do not add speculative features, abstraction layers, configuration, or fallback behavior.
- Do not silently choose among materially different interpretations.
- Do not refactor adjacent code merely because it could be cleaner.
- Do not rewrite comments or formatting outside the changed behavior.
- Report unrelated defects separately instead of folding them into the patch.
- Expand scope only when the requested behavior cannot be implemented safely without it; explain the dependency first.
Completion evidence
- the success condition and focused checks performed;
- any necessary scope expansion and why it was unavoidable;
- remaining uncertainty or checks that could not run.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: 26zl
- Source: 26zl/universal-agent-skills
- 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.