Layerkit Deletion First
Deletion-first change discipline for Layerkit work. Use before adding code, files, exports, docs, tests, or abstractions; during heal/integration updates; and whenever Codex should prefer modifying or deleting existing code over additive implementation.
Install
$ agentstack add skill-hariharapanigrahy-layerkit-layerkit-deletion-first ✓ 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-hariharapanigrahy-layerkit-layerkit-deletion-first) 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
layerkit-deletion-first
Use this skill before implementation work, especially before layerkit-source-edit-client edits production datalayer code.
Before adding code, identify existing code, docs, tests, fixtures, and package surfaces that can be removed or rewritten.
Before a large deletion/rewrite or strategic redirect, prove the new direction with one small passing gate: an eval, end-to-end QA check, contract-heal case, or before/after acceptance test.
Protocol
- Identify existing code, docs, tests, fixtures, scripts, exports, commands, and shims that can be removed or rewritten.
- Prefer modifying or deleting existing code over adding files.
- Do not add a new abstraction until the existing abstraction has been inspected and cannot reasonably change.
- For every new file, function, export, command, fixture, or skill, state what it replaces.
- If it replaces nothing, justify why the expansion is necessary.
- Target net-negative or near-neutral LOC unless functionality truly expands.
- Before a strategic redirect or large deletion/rewrite, define what must pass, the proof artifact, and the fallback if validation fails; record the proof step before continuing.
- Keep tests proportional to the implementation size; release hardening must cover client-package edit paths, mapping semantics, deletion-first behavior, and CI/eval gates touched by the change.
Deletion Pass
Check these surfaces before adding:
- stale demos, design notes, launch scripts, sample-only assets
- legacy wrappers and compatibility aliases not required by public API
- tests for removed behavior
- duplicated command paths or old workflow names
- unused exports, fixtures, scripts, generated output, and package contents
- docs that describe non-current product paths
For heal/integration work, preserve only the spine:
API spec/doc -> contract drift -> map/proposal update -> privacy/checker -> production datalayer integration -> client package verification
Move required examples into evals/fixtures; delete demo/docs packaging around them.
Final Report
Report:
- lines added/deleted and net delta
- files deleted
- new files/functions/exports and what each replaces
- legacy surfaces intentionally kept and why
- outcome checkpoints: what passed, proof artifact, fallback used or available
- tests/gates run, including any package-level fixture, judge, release checklist, or before/after behavior used as proof
- proof step for any strategic redirect
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: hariharapanigrahy
- Source: hariharapanigrahy/layerkit
- 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.