CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

memoir-dialectic

Multi-session memoir planning and (optionally) drafting via patient, iterative dialogue. Use whenever the user wants to plan, build, or write a memoir — full life, partial life, single milestone, professional thread, creative thread, or thematic slice. You interview the user across many sessions, accumulate plan documents in a project folder, and optionally synthesize a draft. Trigger on memoir-dialectic, "help me plan my memoir," "write my memoir with me," "memoir interview," "life story project," "autobiography help," or any long-horizon autobiographical writing collaboration.

Quality

93%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 a tight, actionable playbook: explicit sequencing, built-in checkpoints, concrete dialogue prompts, and a quick-reference file map, with no padding or explanations of known concepts. The one real defect is a stray trailing "enough-tooltip-text" metadata block after the Quick reference table, which costs both conciseness and structure.

Suggestions

Delete or relocate the stray trailing block ("---" followed by "enough-tooltip-text: \"…\"") after the Quick reference table — it is misplaced metadata, not body content, and is the main thing holding back both conciseness and progressive_disclosure.

If the tooltip text is genuinely needed, move it into the YAML frontmatter as a proper field so the body ends cleanly at the Quick reference table.

Tighten the intro's design flavor ("The folder is the memory; the user can disappear for weeks or years and pick up where they left off") to a single clause.

DimensionReasoningScore

Conciseness

The body is lean and imperative with no explanations of concepts Claude already knows, but minor extras — the design-flavor intro ("The folder is the memory; the user can disappear for weeks or years and pick up where they left off") and a stray trailing "enough-tooltip-text:" block after the Quick reference — keep it just below the every-token-earns-its-place anchor.

4 / 5

Actionability

Fully executable guidance for an instruction-only skill: the exact opening question ("Where is the project folder, or should I create one?"), concrete filenames and 10 KB caps, specific unsticking prompts ("a sensory pull — smell, sound, light, weather, what they were wearing"), and a worked revision-note example ("rev 2: tightened opening, removed Aunt Beth per user").

5 / 5

Workflow Clarity

Every phase is explicitly sequenced — session-start inventory with empty/non-empty branching, numbered intake, synthesis, and the optional draft pipeline — with real checkpoints: "Summarize where things stand in one or two sentences," "List gaps and contradictions for the user to resolve," and "Pause for review between draft files. Revise on request." No destructive or batch operations, so the workflow-clarity cap does not apply.

5 / 5

Progressive Disclosure

A self-contained, well-sectioned single-file skill with a Quick reference table and no external files needed; docked one point for the stray trailing "--- / enough-tooltip-text:" block — misplaced metadata in the body that breaks an otherwise clean structure (and at ~87 lines it falls outside the under-50-line simple-skill exception).

4 / 5

Total

18

/

20

Passed

Description

95%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 and explicitly states both what the skill does and when to use it, with natural user-voiced trigger phrases and a distinct niche. Its only flaw is second-person voice in the capability sentence ("You interview the user"), which the judging guidelines penalize on specificity.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "You interview the user across many sessions, accumulate plan documents in a project folder, and optionally synthesize a draft" — with comprehensive coverage of the planning and drafting loop, matching the 5 anchor; however, the second-person phrasing ("You interview the user") violates the third-person voice guideline, reducing the score by 1.

4 / 5

Completeness

Explicitly answers both what ("Multi-session memoir planning and (optionally) drafting via patient, iterative dialogue… accumulate plan documents… optionally synthesize a draft") and when ("Use whenever the user wants to plan, build, or write a memoir… Trigger on…"), with concrete trigger phrases as in the 5 anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases a user would actually say — "help me plan my memoir," "write my memoir with me," "memoir interview," "life story project," "autobiography help" — plus scope variants (full life, single milestone, professional thread) and synonyms (memoir/autobiography/life story).

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (long-horizon memoir/autobiography collaboration) with domain-specific triggers like "memoir interview" and "write my memoir with me"; minimal overlap risk with generic writing or document skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

0gsd/enough

Path

defaults/skills/memoir-dialectic/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.