CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

inland-empire

Subconscious memory layer. Absorbs observations, surfaces associative memories as hypotheses, and builds context across sessions. Commands: remember, consult, surface, forget, stats.

Quality

75%

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 ./inland-empire/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 highly actionable command reference with real, copy-paste-ready invocations, sensible validation for the destructive operation, and clean sectioning. Its weaknesses are repetition of the evidence-vs-hypothesis framing, some decorative prose, and no use of progressive disclosure to move backend internals and full response schemas out of the main file.

Suggestions

State the consult-evidence / surface-hypothesis distinction once (in 'What It Is' or under the commands) and cut the repetitions in the consult section, 'Interpreting Associations', and 'When to Use'.

Move the full JSON response examples, storage architecture diagram, and backend internals into a references/ file (e.g. BACKENDS.md) and keep SKILL.md as a lean overview with one-level-deep links.

For the destructive `forget` command, make the checkpoint explicit: recommend running with --dry-run first and only executing the delete after reviewing the output.

DimensionReasoningScore

Conciseness

The body teaches no Claude-known concepts and most content is skill-specific, but it restates the consult-as-evidence / surface-as-hypothesis distinction three times (in 'What It Is', in the consult section, and again under 'Interpreting Associations'), the ASCII backend diagram duplicates the backend-detection bullets below it, and the epigraph/'filing cabinets' prose is padding. Anchor 3 (mostly efficient but could be tightened) fits: more than minor trimming needed for a 4, but far from the padded anchor-2 pattern.

3 / 5

Actionability

Every command has copy-paste-ready invocations ("python3 scripts/inland_empire.py remember ..." — path verified to exist), with flags (--depth, --type, --before, --dry-run) and example JSON responses covering the common cases. Fully executable with no gaps — anchor 5.

5 / 5

Workflow Clarity

Each command's usage is unambiguous and the destructive `forget` operation does document a validation mechanism (--dry-run), plus error/partial-flag semantics for recovery. It falls short of anchor 5 because the doc never explicitly recommends dry-run-before-delete as a step for destructive or batch forgets — a minor checkpoint gap characteristic of anchor 4.

4 / 5

Progressive Disclosure

Well-organized sections with a single referenced path (scripts/inland_empire.py) that is a real bundle file, and no nested or buried references. But it is a ~263-line monolith: response schemas, storage architecture, and backend internals are inlined rather than split into reference files (the bundle even ships mem0/memory_graph/memory_libsql docs that are never surfaced). Anchor 4 (good structure, minor organization gaps) rather than 5.

4 / 5

Total

16

/

20

Passed

Description

66%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 clear, concise 'what' with good command-level specificity, but the description omits any 'when to use' trigger guidance, which caps its completeness and limits its routing value. Adding an explicit 'Use when...' clause with natural trigger phrases would materially improve it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user says remember, recall, or forget; when starting a task where past sessions' observations matter; or when building persistent context across sessions.'

Include natural synonyms users would say — 'recall', 'notes', 'persist' — alongside the command verbs to broaden trigger coverage.

Consider one line on when NOT to use it (structured project data, version-controlled notes) to sharpen distinctiveness from file/config-based skills.

DimensionReasoningScore

Specificity

The description names the domain (memory) and several concrete actions ("Absorbs observations, surfaces associative memories as hypotheses, and builds context across sessions") plus all five command verbs (remember, consult, surface, forget, stats). It sits at anchor 4 — several specific actions with minor gaps — rather than 5 because the action verbs are somewhat abstract and command semantics are not detailed, and above 3 because coverage goes beyond 1-2 actions.

4 / 5

Completeness

The 'what' is clear (subconscious memory layer; absorbs/surfaces/builds context; five commands), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere — the judging guidelines explicitly cap completeness at 3 in that case. This matches anchor 3's example (clear what, when missing) exactly.

3 / 5

Trigger Term Quality

Natural user phrases are present: "memory", "remember", "consult", "forget", "builds context across sessions". Missing common synonyms and variations like "recall", "note", "persist", "store" — matching anchor 4 (good coverage, a few natural terms missing) rather than 5, and clearly richer than the thin keyword set of anchor 3.

4 / 5

Distinctiveness Conflict Risk

"Subconscious memory layer" with a distinct five-command surface carves a clear niche, though any memory-adjacent request (remember, recall) could overlap sibling memory skills. Anchor 4 (mostly distinct; minor overlap risk with closely related skills) fits better than 5 given the crowded memory-tool space.

4 / 5

Total

15

/

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

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository

Raudbjorn/cognitive-construct

Path

inland-empire/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.