How do I install the Sync Skill Cache skill?

Run npx skillmds@latest add hyhmrright/sync-skill-cache in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sync Skill Cache safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sync Skill Cache?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sync Skill Cache free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sync Skill Cache?

hyhmrright (@hyhmrright) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sync Skill Cache by hyhmrright — Agent Skill

Name: Sync Skill Cache
Rating: 4.666666666666667 (3 reviews)
Author: hyhmrright

Sync Skill Cache

Sync the Logic-Lens working-copy skills/ into the installed plugin cache so content-evals test the EDITED skill, not the last published one. ALWAYS run this after editing any skills/**/SKILL.md or guide/_shared file and BEFORE running content-evals — otherwise the eval silently grades stale content and every token is wasted. Also use to verify the cache is in sync ("is the cache fresh?", "did my edit take effect in evals?", "check skill cache drift").

hyhmrright e996c2d 2 files · 4.4 KB Updated Sep 10, 2026

File contents

sync-skill-cache

content-evals invoke each skill through Claude Code's plugin mechanism, which loads from ~/.claude/plugins/cache/logic-lens-marketplace/logic-lens/<version>/skills/ — not the repo's skills/. Editing skills/ changes nothing the eval sees until you copy it into the cache. This is the single most expensive footgun in the iteration loop: skip it and you grade the previous skill while believing you tested your change.

Steps

Sync + verify from the repo root:
```
bash .claude/skills/sync-skill-cache/scripts/sync-cache.sh
```
The script reads the active version from package.json, rsyncs skills/ into the matching cache dir (--delete, so removed files are removed in the cache too), then diffs the two to confirm they are byte-identical. It prints OK … on success.
If it prints DRIFT or a missing-cache error: do not run evals. The two common causes:
- The cache dir for the current package.json version doesn't exist (plugin not installed at this version) — reinstall/refresh the plugin, or check you didn't just bump the version without refreshing the cache.
- rsync was blocked — rerun and read the diff list it prints.

Verify-only mode (no copy) to answer "is the cache fresh?":

bash .claude/skills/sync-skill-cache/scripts/sync-cache.sh --check

This skill is the mandatory gate between editing a skill and grading it. The iterate-skill orchestrator calls it automatically; run it by hand whenever you edit a skill outside that loop.

---name: sync-skill-cachedescription: Sync the Logic-Lens working-copy skills/ into the installed plugin cache so content-evals test the EDITED skill, not the last published one. ALWAYS run this after editing any skills/**/SKILL.md or guide/_shared file and BEFORE running content-evals — otherwise the eval silently grades stale content and every token is wasted. Also use to verify the cache is in sync ("is the cache fresh?", "did my edit take effect in evals?", "check skill cache drift").---# sync-skill-cachecontent-evals invoke each skill through Claude Code's plugin mechanism, which loads from`~/.claude/plugins/cache/logic-lens-marketplace/logic-lens/<version>/skills/` — **not** therepo's `skills/`. Editing `skills/` changes nothing the eval sees until you copy it into thecache. This is the single most expensive footgun in the iteration loop: skip it and you gradethe previous skill while believing you tested your change.## Steps1. **Sync + verify** from the repo root: ```bash bash .claude/skills/sync-skill-cache/scripts/sync-cache.sh ``` The script reads the active version from `package.json`, rsyncs `skills/` into the matching cache dir (`--delete`, so removed files are removed in the cache too), then diffs the two to confirm they are byte-identical. It prints `OK …` on success.2. **If it prints `DRIFT` or a missing-cache error:** do not run evals. The two common causes: - The cache dir for the current `package.json` version doesn't exist (plugin not installed at this version) — reinstall/refresh the plugin, or check you didn't just bump the version without refreshing the cache. - rsync was blocked — rerun and read the diff list it prints.3. **Verify-only mode** (no copy) to answer "is the cache fresh?": ```bash bash .claude/skills/sync-skill-cache/scripts/sync-cache.sh --check ```This skill is the mandatory gate between editing a skill and grading it. The `iterate-skill`orchestrator calls it automatically; run it by hand whenever you edit a skill outside that loop.

Frequently asked questions