Auto Refresh After New Plugin Sources
Trigger a plugin refresh cycle whenever reconciliation installs new marketplaces so plugin state stays in sync.
Install
$ agentstack add skill-ychampion-cskill-agents-auto-refresh-after-new-plugin-sources ✓ 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-auto-refresh-after-new-plugin-sources) 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: Auto Refresh After New Plugin Sources
Domain: tool-orchestration Trigger: Apply when background reconciliation installs at least one new marketplace and the agent must refresh plugin cache without explicit user action. Source Pattern: Distilled from reviewed post-install refresh and extension-cache invalidation implementations.
Core Method
After reconciliation reports at least one newly installed plugin source, clear both the source cache and the active plugin cache, then trigger a refresh of the live extension registry. Treat that refresh as best-effort but important: if it succeeds, the new tools become available immediately; if it fails, log the error and raise a manual-refresh flag so the user sees that recovery is required. Do this before treating downstream extension operations as ready, otherwise the product will keep resolving against stale code.
Key Rules
- Only trigger the refresh when new installs occurred; avoid redundant refresh cycles after mere updates.
- Clear both marketplace and plugin caches before refreshing to ensure stale data cannot leak into the newly loaded plugins.
- Catch refresh failures, log the error, and set a visible manual-refresh flag rather than silently failing.
- Keep analytics/logging tied to the install path so you know when an automatic refresh runs and whether it failed or succeeded.
Example Application
If a new marketplace is added via a curated list, automatic refresh ensures CLI commands that rely on that marketplace can resolve tools without forcing users to manually run a separate reload step.
Anti-Patterns (What NOT to do)
- Do not refresh plugin state when there are zero new installs; the extra cache clears slow startup without benefit.
- Do not swallow refresh errors; otherwise users never learn the auto recovery failed and manual action stays hidden.
- Do not reuse stale caches while refreshing; skip clearing caches then refresh and the agent continues pointing at old code.
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.