Delist After Reconcile Enforcement
Run delist or blocklist enforcement after synchronization so removals update both metrics and downstream refresh signals.
Install
$ agentstack add skill-ychampion-cskill-agents-delist-after-reconcile-enforcement ✓ 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-ychampion-cskill-agents-delist-after-reconcile-enforcement) 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
SKILL: Delist-After-Reconcile Enforcement
Domain: extensions-mcp Trigger: Use when an extension or plugin system must enforce removals even if the install or update pass made no additions. Source Pattern: Distilled from reviewed post-sync extension policy enforcement flows.
Core Method
Apply delist or policy enforcement after synchronization finishes so removal decisions operate on the freshest materialized state. Treat removals as first-class changes that update metrics and propagate the same downstream refresh signal used for installs. This keeps policy enforcement visible and ensures callers reload when the live set changed through removal rather than addition.
Key Rules
- Run delist checks after synchronization, not before, so policy decisions see the latest installed state.
- Count removals explicitly and include them in change metrics.
- Let removals flip the same downstream changed flag or refresh contract used by installs and updates.
Example Application
If a headless bootstrap finds that one installed extension was later delisted, remove it after registry sync and return a changed signal so the command surface reloads.
Anti-Patterns (What NOT to do)
- Do not hide removals as silent cleanup.
- Do not skip delist enforcement when no new installs occurred.
- Do not keep separate refresh paths for installs and removals when both affect the live set.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ychampion
- Source: ychampion/cskill-agents
- License: MIT
- Homepage: https://x.com/YashasGunderia/status/2039990540016693692?s=20
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.