CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hindsight-coding-agent

How this machine's Hindsight coding-agent memory works β€” the plugin behind the 🧠 banner. Use when the user says "store/remember this in hindsight", asks what the memory/pages are, wants to configure per-repo memory (disable, rename banks, git depth), or something memory-related looks broken.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./hindsight-integrations/coding-agents/skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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.

The operational core is excellent β€” concrete tools, commands, config examples, and clear procedures for storing, retrieving, correcting, and debugging memory β€” but it is buried in an ~83KB monolith. The entire configuration reference and several policy deep-dives are inlined with no bundle files at all, and several topics are explained two or three times, making token cost the skill's dominant defect.

Suggestions

Move the full configuration reference table and the 'Spreading refreshes with H', observation-scopes, and manageBankConfig/defaultBankConfig deep-dives into a references/ file (e.g. references/config.md), keeping SKILL.md to the operational core: automatic behavior, storing, retrieving, correcting, install, and quick diagnostics.

State each fact once: install/autoUpdate behavior is covered in both the 'Install / update' section and the reference table row, and page-refresh policy appears in the table, the prose after it, and the 'Spreading refreshes' section β€” pick one location per topic and cross-link.

Replace multi-hundred-word table cells with one-line summaries that link to the detailed section or reference file, so the reference table serves as an index rather than an essay.

DimensionReasoningScore

Conciseness

The body is ~742 lines / ~83KB with config-table cells running to several hundred words each (e.g. the autoInject, recallOptions, and pages rows), and key topics are explained two or three times over (install/autoUpdate in both the 'Install / update' section and the reference table; page-refresh policy in the table, the prose after it, and the 'Spreading refreshes with H' section). It is noticeably verbose with padded sections, though it does not explain concepts Claude already knows, so it does not fall to anchor 1.

2 / 5

Actionability

Concrete, executable guidance throughout: tool signatures like hindsight_ingest_document(title, content) and hindsight_capture_initiative(title, summary), copy-paste npx commands for install/update/stats, copy-paste JSON config examples, a verbatim crediting format ('🧠 From Hindsight memory (<page>): …'), and a structured correction procedure specifying title and content layout. Minor gaps β€” tool usage is shown signature-style rather than as a worked invocation, and some tools (hindsight_diagnose, hindsight_sync_status) are named without usage detail β€” keep it below fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

The agent-facing workflows are clearly sequenced: 'Storing things deliberately' is a case-by-case decision list, 'Correcting wrong or stale memory' gives a fix-the-record procedure with an explicit verify-first precondition and required content structure, and 'When memory seems to be missing' points to specific diag events to check. Checkpoints are present for the risky operation (correcting memory only after verification; bank deletion consequences spelled out), with only minor gaps such as the config-edit application table being reference material rather than a workflow.

4 / 5

Progressive Disclosure

No bundle files exist at all (no references/, scripts/, or assets/), and roughly half the body β€” the full configuration reference table plus the deep dives on page-refresh cron hashing, observation scopes, and manageBankConfig/defaultBankConfig β€” is inlined in SKILL.md where it clearly belongs in one or more separate reference files. Section headers are good, which lifts it above unstructured anchor 2's example, but the total absence of reference files and the scale of inlining (~400+ lines of config reference) place it at anchor 2 rather than 3, whose example at least signals an external ADVANCED.md.

2 / 5

Total

12

/

20

Passed

Description

87%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 states what the skill covers, gives an explicit and concrete 'Use when' clause with natural quoted trigger phrases, and is tightly scoped to a named plugin on this machine. The only weakness is that the capability list omits retrieval/crediting behavior and a few natural trigger synonyms, which keeps specificity and trigger coverage just short of top marks.

DimensionReasoningScore

Specificity

Names the domain ('Hindsight coding-agent memory', 'the plugin behind the 🧠 banner') and several concrete actions β€” 'store/remember this in hindsight', 'configure per-repo memory (disable, rename banks, git depth)', 'something memory-related looks broken' β€” with minor gaps (retrieval and crediting tools are not mentioned). It lists several specific actions rather than only 1-2, but coverage is not comprehensive, so it sits at anchor 4 rather than 3 or 5.

4 / 5

Completeness

Explicitly answers both parts: the 'what' ('How this machine's Hindsight coding-agent memory works β€” the plugin behind the 🧠 banner') and an explicit 'Use when...' clause listing concrete trigger phrases. This matches the anchor-5 example structure exactly and is clearly above anchor 4, where the 'when' would be less specific.

5 / 5

Trigger Term Quality

Includes natural, quotable user phrases like "store/remember this in hindsight", "asks what the memory/pages are", and "memory-related looks broken", with the store/remember synonym pair covered. A few natural terms a user might say are missing (e.g. recall, forget/delete, reset memory), which keeps it below the comprehensive anchor 5 but above anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

The description is anchored to a named product (Hindsight), a machine-specific context, and a distinctive UI marker (the 🧠 banner), with triggers keyed to the product name. It occupies a clear niche with minimal conflict risk against generic memory or document skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation β€” 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (743 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

vectorize-io/hindsight

Path

hindsight-integrations/coding-agents/skill/SKILL.md

Reviewed

Table of Contents

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.