hyperflow-cache

Hyperflow memory manager. Use to view, search, add, edit, prune, or clear hyperflow project memory — "show memory", "search memory for X", "clear memory", "what does hyperflow remember about Y". CRUD over .hyperflow/memory/ only — never touches source code.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-structured instruction-only skill: concrete formats, explicit scope rules, and a confirmation gate on the only destructive operation. The main weaknesses are the undefined 'Follow the hyperflow doctrine' reference and slightly under-specified add/edit mechanics.

Suggestions

Replace or define 'Follow the hyperflow doctrine' — either inline its one or two operative rules or drop the reference, since no bundle file explains it.

For 'add', give a one-line rule for choosing among decisions / learnings / pitfalls / patterns (or an example entry per category) so category selection isn't left implicit.

Expand 'edit' slightly to state how to locate the target entry (e.g., search by heading first, then update in place) so the edit operation is as executable as the others.

Dimension	Reasoning	Score
Conciseness	The ~20-line body is lean with no over-explanation — every operation is one bullet, the entry format is stated inline as '## <topic>' then '- <fact> (recorded <YYYY-MM-DD>)', and nothing Claude already knows is explained.	5 / 5
Actionability	Guidance is mostly executable: concrete paths (.hyperflow/memory/{decisions,learnings,pitfalls,patterns}.md), a grep-based search showing 'matching entries with their file + heading', and a fixed entry format. Minor gaps: 'Follow the hyperflow doctrine' is undefined, and 'append a tagged entry to the right category file' leaves category selection implicit.	4 / 5
Workflow Clarity	Each operation is unambiguously specified for this simple single-purpose skill, and the destructive path has an explicit validation checkpoint ('Confirm via AskUserQuestion before a destructive clear (binary Yes/No)'), so the destructive-cap of 3 does not apply. 'edit <entry> — update an existing entry in place (don't duplicate)' lacks detail on locating or verifying the edit, keeping it below 5.	4 / 5
Progressive Disclosure	The skill is under 50 lines with no need for external references, and its two sections (Operations, Rules) are well-organized and easy to navigate, which the rubric's simple-skill guidance scores at 5.	5 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it enumerates all CRUD capabilities, scopes the skill precisely, and includes quoted natural-language trigger phrases that explicitly answer both 'what' and 'when'. The only gap is a few missing natural synonyms among the trigger terms.

Dimension	Reasoning	Score
Specificity	Quotes six concrete actions — 'view, search, add, edit, prune, or clear hyperflow project memory' — plus a scope constraint ('CRUD over .hyperflow/memory/ only'), giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers 'what' (Hyperflow memory manager, CRUD over .hyperflow/memory/) and 'when' via the 'Use to...' clause with concrete trigger phrases like 'show memory' and 'what does hyperflow remember about Y', matching the anchor requiring both with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases are quoted directly — 'show memory', 'search memory for X', 'clear memory', 'what does hyperflow remember about Y' — but a few natural variations (e.g., 'list memories', 'forget X', 'update memory') are missing, so it matches 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym coverage of the top anchor.	4 / 5
Distinctiveness Conflict Risk	A clear niche — hyperflow project memory under .hyperflow/memory/, with 'never touches source code' — makes it highly distinguishable from generic memory or file skills with minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jeremylongshore/tons-of-skills-marketplace
Path: plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-cache/SKILL.md
Commit: 88dcf65

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.