writer-memory

Agentic memory system for writers - track characters, relationships, scenes, and themes

Quality

63%

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/writer-memory/SKILL.md

Quality

Content

65%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 with concrete commands and examples, but it is a monolithic document over the 50-line simple-skill threshold with redundant examples and no external reference files. Adding inline validation checkpoints and splitting heavy reference material into bundled files would raise the score.

Suggestions

Add explicit validation checkpoints (e.g. run /status or /validate) between state-changing steps in the Full Workflow sequence to satisfy the destructive/batch-operation feedback-loop expectation.

Move the full storage JSON schema and Synopsis 5요소 detail into reference files (e.g. references/schema.md, references/synopsis.md) and link to them from SKILL.md.

De-duplicate the character-setup examples so the Memory Types section and Full Workflow do not repeat the same commands.

Dimension	Reasoning	Score
Conciseness	Largely avoids explaining concepts Claude already knows and uses tables efficiently, but repeats examples (character setup appears in both Memory Types and Full Workflow) and inlines a full storage JSON schema that restates the field tables.	3 / 5
Actionability	Provides copy-paste-ready slash commands, a complete end-to-end workflow, a concrete validate example with expected output, query examples, and a full storage schema covering the common cases.	5 / 5
Workflow Clarity	A clear sequenced workflow and backup behavior exist, but the main Full Workflow sequence lacks inline validation checkpoints after state-changing steps, so the destructive/batch-operation cap holds at 3.	3 / 5
Progressive Disclosure	No bundle files exist and all detail is inlined in a single ~440-line SKILL.md with good section headers, but content like the full storage schema and synopsis elements that could live in separate references is not split out.	3 / 5
	Total	14 / 20 Passed

Description

61%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 clearly conveys the skill's purpose and target domain with concrete tracked entities, but omits any explicit 'when to use' trigger guidance and relies on a single generic action verb. Adding a 'Use when...' clause with natural trigger phrases would lift completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when writing fiction, developing characters, tracking story continuity, or checking dialogue consistency.'

Replace the single generic verb 'track' with multiple concrete actions (e.g. 'add, update, query, and validate characters, relationships, scenes, and themes').

Add common synonyms users might say (novel, story, worldbuilding, dialogue voice) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and four concrete tracked objects (characters, relationships, scenes, themes) but only one generic action verb ('track'), so it is not comprehensive enough for a 4.	3 / 5
Completeness	Has a clear 'what' (agentic memory system that tracks writing entities) but no 'when'/'Use when' trigger guidance, which the rubric caps at 3.	3 / 5
Trigger Term Quality	Includes natural domain keywords a fiction writer would say (characters, relationships, scenes, themes, writers), but lacks a 'Use when' trigger phrase and common synonyms (novel, story, worldbuilding, dialogue).	4 / 5
Distinctiveness Conflict Risk	The creative-writing memory niche with character/scene/theme tracking is mostly distinct from other skills, with only minor overlap risk against generic notepad/memory skills.	4 / 5
	Total	14 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Yeachan-Heo/oh-my-claudecode
Path: skills/writer-memory/SKILL.md
Commit: 5aa678c

Reviewed: 8 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.