Dead Path Update Skipping
Skip update actions that point at missing local paths when a valid materialized entry already exists, preserving the working state instead of converting drift into a noisy failure.
Install
$ agentstack add skill-ychampion-cskill-agents-dead-path-update-skipping ✓ 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-dead-path-update-skipping) 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: Dead Path Update Skipping
Domain: extensions-mcp Trigger: Use when update candidates come from local paths that may disappear across checkouts, but existing materialized state should remain usable until a valid replacement exists. Source Pattern: Distilled from reviewed extension lifecycle and source-reconciliation patterns.
Core Method
Before running an update from a local path, verify that the declared path still exists. If the action is an update and the current materialized entry is still valid, skip the update rather than turning a transient path mismatch into a failed reinstall. This preserves the working materialized state in multi-checkout or ephemeral-path scenarios while still surfacing missing paths for truly absent entries.
Key Rules
- Only apply this skip to updates where a materialized entry already exists; missing entries should still surface real errors.
- Check path existence after normalization so you validate the exact path the reconciler would use.
- Record skipped updates distinctly from failures so operators know the existing entry was intentionally preserved.
- Limit the exception to local-path sources; remote sources need normal failure handling.
- Log the reason for the skip so future debugging can tell path drift from install breakage.
Example Application
If a developer switches away from a temporary worktree that contained a local marketplace path, keep the previously materialized marketplace entry instead of failing an update against the now-missing worktree path. The next valid local path or explicit reinstall can replace it later.
Anti-Patterns (What NOT to do)
- Do not attempt updates from dead local paths just to fail loudly; you destroy signal-to-noise while preserving nothing.
- Do not apply this rule to brand-new missing entries; if nothing working exists yet, the user needs the error.
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.