Skip to content
Back to skills

Eval Cache

ASecurity

Check for a cached plan-evaluation.json result before launching the plan-evaluator agent. This skill should be used in Phase 1.3 (Simple Mode Evaluation) of the orchestrator prompt. Triggers on: entering Phase 1.3, checking simple mode, evaluating plan complexity. Returns EVAL_CACHE_HIT with cached values or EVAL_CACHE_MISS signaling re-evaluation is needed.

  • 121 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 26, 2026
ai-agentsbash

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned May 27, 2026

npx -y skills add closedloop-ai/claude-plugins --skill eval-cache --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Eval Cache?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Eval Cache
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/closedloop-ai-eval-cache/badge)](https://www.skillsdirectory.com/skills/closedloop-ai-eval-cache)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: eval-cache
description: |
  Check for a cached plan-evaluation.json result before launching the plan-evaluator agent.
  This skill should be used in Phase 1.3 (Simple Mode Evaluation) of the orchestrator prompt.
  Triggers on: entering Phase 1.3, checking simple mode, evaluating plan complexity.
  Returns EVAL_CACHE_HIT with cached values or EVAL_CACHE_MISS signaling re-evaluation is needed.
context: fork
allowed-tools: Bash
---

# Eval Cache

Check whether a prior simple-mode evaluation can be reused, avoiding a redundant plan-evaluator launch when the plan has not changed.

## When to Use

Activate this skill at the start of Phase 1.3 (Simple Mode Evaluation), **before** launching `@code:plan-evaluator`. If the cache is fresh, skip the evaluator entirely and use the cached result.

## Usage

Run the cache check script:

```bash
bash ${CLAUDE_SKILL_DIR}/scripts/check_eval_cache.sh <WORKDIR>
```

## Interpreting Output

The script prints one of two structured results to stdout:

### Cache Hit

```
EVAL_CACHE_HIT
simple_mode: true|false
selected_critics: [critic1, critic2, ...]
summary: <cached evaluation summary>
```

**Action:** Parse `simple_mode` and `selected_critics` from the output. Skip launching `@code:plan-evaluator` and proceed with the cached values as if the evaluator had just returned them.

### Cache Miss

```
EVAL_CACHE_MISS
reason: <why the cache is stale or missing>
```

**Action:** Launch `@code:plan-evaluator` as normal. The evaluator will write a fresh `plan-evaluation.json` that subsequent iterations can cache from.

## How Freshness Works

The script uses file modification timestamps:
- If `plan-evaluation.json` does not exist: **miss**
- If `plan.json` is newer than `plan-evaluation.json`: **miss** (plan was modified since last evaluation)
- If `plan-evaluation.json` is newer than `plan.json`: **hit** (evaluation is still valid)

This correctly handles the case where a user modifies the plan while the workflow is paused: editing `plan.json` updates its mtime, invalidating the cached evaluation.

Files in this skill

  • SKILL.md2 KB
  • scripts/check_eval_cache.sh1.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.