writer-memory

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

Quality

55%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/writer-memory/SKILL.md

Quality

Discovery

32%

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 identifies a clear domain (creative writing memory management) and lists trackable elements, but lacks explicit trigger guidance and misses common user vocabulary. The absence of a 'Use when...' clause significantly weakens its utility for skill selection among many options.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when writing fiction, managing story continuity, tracking character arcs, or working on novels/manuscripts'

Expand trigger terms to include natural user vocabulary: 'novel', 'story', 'plot', 'worldbuilding', 'fiction writing', 'manuscript', 'continuity'

Specify concrete actions beyond 'track' - e.g., 'create character profiles, map relationships, maintain plot continuity, organize scene timelines'

Dimension	Reasoning	Score
Specificity	Names the domain (writing/memory system) and lists some actions (track characters, relationships, scenes, themes), but doesn't describe concrete operations like 'create character profiles', 'visualize relationship maps', or 'maintain continuity checks'.	2 / 3
Completeness	Describes what it does (track writing elements) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant terms like 'characters', 'relationships', 'scenes', 'themes', and 'writers', but misses common variations users might say like 'novel', 'story', 'plot', 'worldbuilding', 'fiction', 'manuscript', or 'continuity'.	2 / 3
Distinctiveness Conflict Risk	The 'agentic memory system for writers' framing provides some distinction, but 'track characters, relationships, scenes' could overlap with general writing assistance or note-taking skills without clearer boundaries.	2 / 3
	Total	7 / 12 Passed

Implementation

77%

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

This is a well-crafted skill with excellent actionability and clear workflows for a specialized creative writing memory system. The Korean-first approach with bilingual field names serves its target audience well. However, the document is overly long for a SKILL.md overview—detailed schemas, full examples, and troubleshooting should be split into separate reference files to improve token efficiency and progressive disclosure.

Suggestions

Extract the detailed Storage Schema JSON and File Structure sections into a separate REFERENCE.md or SCHEMA.md file

Move the 'Full Workflow' and extended examples to an EXAMPLES.md file, keeping only a minimal quick-start example in SKILL.md

Consolidate the Memory Types section—field definitions appear both in tables and in examples, creating redundancy

Move Troubleshooting to a separate TROUBLESHOOTING.md file and link to it from the main skill

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but verbose for its purpose. While the Korean terminology and detailed tables add value for the target audience, there's significant repetition (e.g., field definitions appear in multiple places) and some sections could be consolidated. The 400+ lines could likely be reduced by 30-40% without losing essential information.	2 / 3
Actionability	Excellent actionability with concrete command examples throughout, complete JSON schema for storage, specific workflow examples, and copy-paste ready commands. The validation example showing input, output, and suggested alternatives is particularly strong.	3 / 3
Workflow Clarity	Clear multi-step workflows with explicit sequences. The 'Full Workflow' example demonstrates proper ordering (init -> characters -> relationships -> world -> themes -> scenes -> query -> validate -> synopsis). Auto-backup behavior provides implicit validation/recovery for destructive operations.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections and tables, but everything is in a single monolithic file. The detailed storage schema, full workflow examples, and troubleshooting could be split into separate reference files. References to integration with other systems (OMC Notepad, Architect Agent) are mentioned but not linked to external docs.	2 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: Yeachan-Heo/oh-my-claudecode
Commit: 48ffaac

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