CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lore

Curating cross-agent knowledge and institutional memory: extracts patterns from agent journals into METAPATTERNS.md, detects knowledge decay, propagates best practices. Use for memory curation.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/lore/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 a well-sequenced, highly concrete instruction set with clear phase gating and quantified rules, though it carries duplicated summary blocks and citation padding that dilute token efficiency. Its most serious defect is that all seven reference/*.md files and all _common/*.md files it instructs the agent to read are absent from the bundle, leaving the progressive-disclosure structure nominally good but functionally broken.

Suggestions

Ship the referenced files: add the missing references/ bundle (knowledge-synthesis.md, pattern-taxonomy.md, propagation-protocol.md, decay-detection.md, official-pattern-taxonomy.md, autorun-schema.md) or inline the critical tables/formats (LORE_INSIGHT format, authoritative TTL table) that the body currently delegates to them.

Remove the ~30-line HTML CAPABILITIES_SUMMARY comment and the Output Routing table that duplicates the Recipes/Trigger Guidance sections to reclaim token budget.

Specify how similarity percentages are computed (e.g. an embedding/keyword heuristic or checklist) so the '>= 80% cluster / 50-79% variant' rules are executable rather than abstract.

Trim research-justification citations (Zalando, Google SRE, MIT Sloan, Ebbinghaus) to one-line pointers or move them into a reference file — they cost context without changing behavior.

DimensionReasoningScore

Conciseness

The operational rules are dense and mostly non-redundant (e.g. "Similarity >= 80% → cluster", "STALE > 180 days"), but there is notable padding: the ~30-line HTML CAPABILITIES_SUMMARY comment duplicates the Trigger Guidance and Collaboration sections, the Output Routing table largely repeats the Recipes table, and research justifications ("Zalando's 2-year postmortem analysis", "MIT Sloan: old knowledge prohibits absorption", "Ebbinghaus curve") add tokens without operational value. This fits anchor 3 — mostly efficient but includes unnecessary material that could be tightened — rather than 2, since no basic concepts Claude already knows are explained.

3 / 5

Actionability

Highly concrete for an instruction-only skill: exact thresholds ("1 = Anecdote, 2 = Emerging, 3-5 = Pattern..."), TTL multipliers ("SECURITY 0.5× → stale after 90 days"), ID format ("[DOMAIN]-[TYPE]-[NNN]"), and journal format ("## YYYY-MM-DD - [Discovery/Insight]"). Not 5 because key executable mechanics are missing or dangling: no method for computing the "Similarity >= 80%" score, and the LORE_INSIGHT/LORE_ALERT formats are delegated to reference files that are not present in the bundle.

4 / 5

Workflow Clarity

The "HARVEST → SYNTHESIZE → CATALOG → PROPAGATE → AUDIT" pipeline is clearly sequenced with a per-phase table of required actions, key rules, and read references, and checkpoints are embedded ("Check for contradictions before registration or promotion", "Promotion requires a new context, no active contradiction, and last evidence within 90 days", the AUDIT phase itself). Not 5 because validation gates are stated as rules rather than explicit gate/feedback-loop steps, and the decay phase's "decide on archival" lacks a decision sequence; comfortably above anchor 3's 'checkpoints missing or implicit'.

4 / 5

Progressive Disclosure

The in-body structure is good — clear sections plus a Reference Map table ("reference/decay-detection.md | You are evaluating freshness...") with one-level-deep, clearly signaled references — but none of the referenced files exist in the bundle: there is no references/ directory, and every cited path (reference/knowledge-synthesis.md, reference/pattern-taxonomy.md, reference/propagation-protocol.md, reference/decay-detection.md, reference/official-pattern-taxonomy.md, reference/autorun-schema.md, and all _common/*.md files) is absent. The disclosure chain is broken in practice, so the bulk of operational detail the body defers to is unreachable; this sits between anchors 3 and 4, and the missing files are more than a minor organization gap.

3 / 5

Total

14

/

20

Passed

Description

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

The description answers both what and when with concrete actions and a specific artifact (METAPATTERNS.md). Its main weakness is the thin trigger clause "Use for memory curation" — a single generic phrase that omits the natural synonyms and user utterances that would reliably route requests to this skill.

Suggestions

Expand the trigger clause beyond 'Use for memory curation' to concrete user utterances, e.g. 'Use when the user asks about lessons learned, postmortem patterns, institutional memory, knowledge decay, or maintaining METAPATTERNS.md'.

Add one or two more concrete capabilities to the what-clause (e.g. 'mines blameless postmortems for incident patterns, detects contradictions between agent learnings') to improve both coverage and distinctiveness.

Include file-extension or artifact-name triggers users would actually mention (e.g. '.agents/*.md journals', 'METAPATTERNS.md') so routing fires on concrete nouns rather than the generic 'memory curation'.

DimensionReasoningScore

Specificity

Quotes: "extracts patterns from agent journals into METAPATTERNS.md, detects knowledge decay, propagates best practices" — three concrete actions plus a named artifact. Not 5 because coverage is incomplete: capabilities like contradiction detection, postmortem mining, and freshness scoring from the body are absent; not 3 because it goes beyond 1-2 actions with a specific destination artifact.

4 / 5

Completeness

Both what and when are present: the what is concrete ("extracts patterns... detects knowledge decay, propagates best practices") and the when is explicit ("Use for memory curation"). Not 5 because the when-clause is a single terse trigger without concrete trigger phrases or common user utterances; clearly above anchor 3 where 'when' is only weakly implied.

4 / 5

Trigger Term Quality

Quotes: "Use for memory curation" as the sole trigger phrase, with "agent journals", "knowledge decay", "best practices", "institutional memory" embedded in the what-clause. Some relevant keywords exist but common variations users would naturally say ("lessons learned", "postmortem patterns", "pattern library", "knowledge management") are missing, matching anchor 3 rather than 4's 'good coverage with a few missing'.

3 / 5

Distinctiveness Conflict Risk

Quotes: "cross-agent knowledge", "agent journals", "METAPATTERNS.md" — a clear niche with distinct triggers. Not 5 because the generic closing phrase "memory curation" and "best practices" could overlap with general memory or knowledge-management skills; mostly distinct with minor overlap risk.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

simota/agent-skills

Path

.agents/skills/lore/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.