CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

memory-literary-analysis

Analyze a complete literary work into a structured Basic Memory knowledge graph: schema design, entity seeding, chapter-by-chapter processing, cross-referencing, and validation.

Quality

75%

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 ./skills/memory-literary-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a highly actionable, well-sequenced pipeline skill with exemplary validation and error-recovery guidance — the coverage-check and paging material is the strongest part. Its costs are length-driven: duplicated explanations of the same tool gotchas and a monolithic single-file layout that inlines schema templates and edge-case deep-dives that belong in references. Splitting the schemas and grep/pagination deep-dives into reference files and deduplicating the repeated warnings would raise both conciseness and progressive disclosure without losing any substance.

Suggestions

Move the six schema definitions to a references/ file (e.g. references/schemas.md) and keep one representative example plus a table of per-type field differences inline in SKILL.md.

State each tool gotcha once: the '--page-size 10' default and the '--name'/'--meta' mutual exclusion are each explained twice at length (Tools section vs. Phase 3/Phase 4) — keep the first full explanation and reference it later in one line.

Extract the grep deep-dive (content_truncated, case-insensitivity, notes-not-source scope) and the multi-page jq loops into a references/coverage-and-search.md, leaving the pipeline phases with just the commands they need.

DimensionReasoningScore

Conciseness

Most content is high-value, non-obvious operational knowledge (paging caps, .txt line-number fidelity, grep searching notes not source), but three key facts are each explained at length twice — the '--page-size 10' default and the '--name'/'--meta' mutual exclusion with positional-path directory-boundary matching both appear near-verbatim in the Tools section and again in Phase 4 — and the six schema blocks are structurally near-identical, so the body could be meaningfully tightened.

3 / 5

Actionability

Fully executable throughout: complete bm_write calls with real metadata shapes, a copy-paste bash+jq paging loop producing a four-key completeness report, and exact commands such as 'bm reindex --search -p moby-dick' and 'bm orphans' — the common cases are covered with ready-to-run examples.

5 / 5

Workflow Clarity

The six phases (Setup through Explore) are explicitly sequenced with an overview map, the per-chapter workflow is numbered, and Phase 4 provides explicit validation checkpoints with pass criteria ('unnumbered: [], missing: [], duplicates: [], and out_of_range: [] together'), error-recovery loops, and a validate-after-each-batch rule — model feedback loops for a batch operation.

5 / 5

Progressive Disclosure

The body is well-sectioned and navigable, but there are no bundle files at all: the six near-identical schema definitions (~170 lines) and the grep/pagination edge-case deep-dives are inlined in a ~780-line SKILL.md where they clearly belong in one-level-deep reference files.

3 / 5

Total

16

/

20

Passed

Description

63%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 is specific and comprehensive about what the skill does, laying out the full pipeline in concrete terms. Its weaknesses are the complete absence of any 'when to use' trigger guidance and sparse natural trigger vocabulary — users would say 'novel' or 'book' far more often than 'literary work'. Adding a 'Use when...' clause naming common literary forms would lift both completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when analyzing a novel, play, poem, or non-fiction book end-to-end, building a study companion or book-club knowledge base, or stress-testing Basic Memory at scale.'

Include the natural synonyms users would actually say — novel, book, play, poem, character analysis, Basic Memory — rather than only the formal term 'literary work'.

Name the output artifact in user terms (e.g. 'searchable, traversable notes about characters, themes, and chapters') so the description doubles as a what-you-get statement.

DimensionReasoningScore

Specificity

The description names the transformation ('Analyze a complete literary work into a structured Basic Memory knowledge graph') and enumerates five concrete pipeline actions ('schema design, entity seeding, chapter-by-chapter processing, cross-referencing, and validation'), matching the comprehensive-coverage anchor.

5 / 5

Completeness

The 'what' is clear and staged in detail, but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which the rubric caps at 3.

3 / 5

Trigger Term Quality

'literary work' and 'knowledge graph' are relevant natural terms, but the everyday phrasings a user would actually say — 'novel', 'book', 'play', 'poem', or the tool name 'Basic Memory' — are missing, so common synonyms and variations are uncovered.

3 / 5

Distinctiveness Conflict Risk

The 'Basic Memory knowledge graph' plus literary-analysis niche is distinct with clear triggers, but the skill sits in a cluster of closely related memory-* skills (memory-schema, memory-notes, memory-ingest) that share 'knowledge graph' and 'schema' triggers, creating minor overlap risk.

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

skill_md_line_count

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

Warning

Total

15

/

16

Passed

Repository

basicmachines-co/basic-memory

Path

skills/memory-literary-analysis/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.