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.
Scanned 5/27/2026
Install via CLI
openskills install closedloop-ai/claude-plugins---
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.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.