/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
$ npx -y skills add hyhmrright/logic-lens --skill sync-skill-cache --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/sync-skill-cache
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
sync-skill-cache.SKILL.mdname: sync-skill-cache
description: 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").
disable-model-invocation: truesync-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
1. **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.
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 .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.
Read more
name: sync-skill-cache
description: 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").
disable-model-invocation: truesync-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
1. **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.
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 .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.
Logic-first AI code review via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy). Catches behavioral bugs, type-contract breaches & async hazards that linters miss. Six skills · Claude Code · Codex CLI · Gemini CLI.
Repo: hyhmrright/logic-lens
Other skills on logic-lens.
- /bump-version
Bump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README badge), then validate. Use when cutting a release or when `npm run validate` reports a version mismatch.
Open skill - /iterate-skill
Run the Logic-Lens skill-improvement loop end to end — baseline → diagnose failures → edit → sync cache → re-eval → verify net gain → iterate until clean. Use whenever the goal is to RAISE a skill's eval score or fix a failing eval mode: "improve logic-review", "the format
Open skill - /new-skill
Scaffold a new logic-* skill in the Logic-Lens repo and wire it into every place a skill must be registered, so no step is missed. Use when adding a seventh (or later) skill to Logic-Lens.
Open skill - /run-iteration-eval
Run the Logic-Lens content-eval pipeline for one iteration and produce a scored summary.json — use to measure a skill change. Wraps scripts/run-content-evals.sh (runner, costs tokens) and scripts/grade-iteration.py (grader, free, re-runnable). ALWAYS sync the plugin cache first.
Open skill - /logic-diff
Compare two code versions for semantic equivalence via semi-formal tracing of both versions side-by-side. Trigger when the user shares a refactor, rewrite, migration, or A/B implementation and wants to confirm behavior is unchanged — "did I break anything", "is this equivalent",
Open skill - /logic-explain
Explain what a specific piece of code actually does for a given input by producing a step-by-step execution trace (interprocedural, with name resolution and type transitions). Trigger when the user is confused about behavior or asks why code produces X instead of Y — "walk me
Open skill

