memory-literary-analysis

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

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/memory-literary-analysis/SKILL.md

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is highly actionable with a clearly sequenced, validated pipeline and concrete API examples. It loses points on conciseness (repetitive inline schemas/tables) and progressive disclosure (everything inline, no reference files).

Suggestions

Move the six full schema definitions into a references/ file (e.g. SCHEMAS.md) and keep one representative schema inline with a pointer, reducing redundancy.

Consolidate the 'What to Capture Per Chapter' and 'Entity Enrichment Per Chapter' tables with the per-chapter code example to remove overlapping content.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete code and tables and no concept-explanation fluff, but six full inline schema code blocks plus the 'What to Capture Per Chapter' and 'Entity Enrichment Per Chapter' tables repeat information already present in the per-chapter workflow example and could be tightened.	2 / 3
Actionability	Provides executable Basic Memory API calls (create_memory_project, write_note, edit_note, schema_validate, schema_diff) with concrete placeholders, plus specific count/batch tables — copy-paste ready guidance throughout.	3 / 3
Workflow Clarity	The pipeline is explicitly phased (Phase 0–5) with a validate→fix→retry feedback loop ('Run schema_validate after each batch, not just at the end. Catch drift early'; 'Fix issues found — common fixes'), matching the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	Sections are well-organized by phase, but the file is monolithic with no bundle files present; the six schema definitions and genre-adaptation tables that could live in separate reference files are all inline.	2 / 3
	Total	10 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 distinctive, clearly stating what the skill does across six concrete actions. Its main weakness is the missing 'Use when...' trigger clause and sparse natural-language trigger terms.

Suggestions

Add an explicit 'Use when...' clause listing natural triggers, e.g. 'Use when analyzing a novel, play, poem, or non-fiction book into a study or research resource.'

Include common user-facing terms ('novel', 'book', 'play', 'poem', 'study guide') alongside the technical pipeline vocabulary to improve trigger matching.

Dimension	Reasoning	Score
Specificity	Lists six concrete actions — 'schema design, entity seeding, chapter-by-chapter processing, cross-referencing, validation, and visualization' — matching the 'lists multiple specific concrete actions' anchor rather than the domain-only level 2.	3 / 3
Completeness	Clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	'literary work' and 'knowledge graph' are natural terms, but common variations a user would say ('novel', 'book', 'play', 'poem') are absent and several terms ('entity seeding', 'cross-referencing') are technical jargon.	2 / 3
Distinctiveness Conflict Risk	The combination of 'complete literary work' and 'Basic Memory knowledge graph' carves a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (515 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: basicmachines-co/basic-memory
Path: skills/memory-literary-analysis/SKILL.md
Commit: cb95e59

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.