Skip to content
Development
Skill

/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

From plugin
logic-lens
2311 skills3 agents6 commands1 hook
Install
$ npx -y skills add hyhmrright/logic-lens --skill sync-skill-cache --agent claude-code

How 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.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • 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.md
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: true

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

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
Ships withlogic-lens

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.

Get the whole plugin

Other skills on logic-lens.