incremental-implementation@r1
VERIFIED· install onlyPublisher claims: "Delivers changes incrementally in thin, verifiable slices. Use when implementing any feature or change that touches more than one file, or when picking up the next task from a plan. Use when rolling a change out behind a feature flag, when you're about to write a large amount of code at once, or when a task feels too big to land in one step." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
Is incremental-implementation@r1 safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-12 and scored it 91/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
### Rule 4: Safe DefaultsFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.- [ ] Type checking passes, where the stack has one (`npx tsc --noEmit`, `mypy`, ...)Fix: Pin versions and sources; vendor anything fetched at install time.### Rule 0: Simplicity FirstFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.### Rule 2: Keep It CompilableFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.### Rule 3: Feature Flags for Incomplete FeaturesFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.### Rule 1: One Thing at a TimeFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.