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/knowledge pages are, wants to configure per-repo memory (disable, rename banks, git depth), or something memory-related looks broken.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

63%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 body is highly actionable and well-sectioned, with concrete commands, tools, and config examples throughout, but it is a monolithic configuration manual rather than an overview: extremely verbose, frequently redundant, and with all reference material inlined instead of split into bundle files. Workflow sections (store, correct, debug) are clear, with only minor gaps like the unspecified bank-deletion step.

Suggestions

Split the configuration Reference table and deep-dive sections (pages/customPages, manageBankConfig, observationScopes, H scheduling) into reference files under references/, keeping SKILL.md to an overview with clearly signaled one-level-deep links.

Deduplicate repeated material: autoUpdate is explained at full length in both the Install section and the Reference row, and the repo-carried-config prohibition appears twice within the Opt-in only section β€” state each once and cross-link.

Give the exact command or control-plane location for deleting a bank in 'Resetting a repo's memory', since 'Delete its bank on the server' is the one non-executable instruction in an otherwise copy-paste-ready skill.

DimensionReasoningScore

Conciseness

The ~740-line body includes paragraph-length table cells and clear redundancy β€” autoUpdate is fully explained both in the Install section and the Reference row, the repo-carried-config prohibition is stated twice within a few lines, and refresh-scheduling rationale repeats across sections. Not 1 because it never explains concepts Claude already knows; all content is plugin-specific but noticeably padded and repetitive.

2 / 5

Actionability

Fully executable throughout: copy-paste npx install/update/uninstall/stats commands, exact tool signatures (hindsight_ingest_document(title, content), hindsight_search_knowledge_pages(query)), complete JSON config examples with placeholders explained, exact log paths, env var names, and a structured correction-document format.

5 / 5

Workflow Clarity

Intent-to-tool mapping for storing, a 3-part correction procedure with explicit verification before fixing, and log-driven debugging with named events (session_start, deepen_started) are clearly sequenced. Minor gaps β€” e.g. 'Resetting a repo's memory: Delete its bank on the server' gives no command or location β€” keep it below the explicit-checkpoint anchor.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so a ~500-line configuration and API reference is inlined monolithically in SKILL.md. Section headers and internal anchor links give real structure, so above the minimal-structure anchor, but content that clearly belongs in separate reference files is inline and there are no external references at all.

3 / 5

Total

14

/

20

Passed

Description

83%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: third-person, concise, with an explicit 'Use when' clause containing concrete trigger phrases users would naturally say. The 'what' side leans toward what the skill is rather than an exhaustive capability list, which is the only notable gap.

DimensionReasoningScore

Specificity

Names the domain (Hindsight coding-agent memory) and several concrete capabilities β€” configure per-repo memory, disable, rename banks, set git depth, debug breakage. Not 5 because capabilities like retrieval tools and memory correction are unmentioned; not 3 since it goes well beyond 1-2 actions.

4 / 5

Completeness

Explicitly answers what ('How this machine's Hindsight coding-agent memory works β€” the plugin behind the 🧠 banner') and when ('Use when the user says...') with concrete trigger phrases. Not 4 because the when-clause is already explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

Quotes natural user phrasings ('store/remember this in hindsight', 'memory/knowledge pages', 'memory-related looks broken') plus config-specific terms. A few natural variants (e.g. recall, forget) are missing, so short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The distinctive product name and per-repo memory niche give a clear identity, but the broad trigger 'something memory-related looks broken' could overlap with other memory features. Not 5 due to that residual overlap; not 3 since the core triggers are product-specific.

4 / 5

Total

17

/

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.