para-memory-files

Use a file-based PARA memory system to store, retrieve, and organize durable knowledge across sessions. Trigger on saving facts, daily notes, entity records, weekly synthesis, recall, tacit user patterns, or plan memory.

Quality

79%

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

Quality

Content

80%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 content is lean, well-organized, and uses progressive disclosure effectively with a real reference file. Its main weakness is workflow clarity: destructive and batch operations (superseding, archiving, weekly rewrites) lack explicit validation checkpoints.

Suggestions

Add explicit validation/verification steps before destructive or batch operations, e.g. confirm a fact is superseded correctly and the superseded_by link resolves before marking status: superseded.

Provide a copy-paste template or minimal items.yaml example inline for the entity lifecycle operations (create entity, supersede, archive) so they are executable rather than prose-only.

Add a checkpoint for the weekly summary.md rewrite (e.g. verify all Hot/Warm facts are included and Cold facts are intentionally omitted) to close the workflow_clarity gap.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, laying out PARA rules and qmd commands compactly with no padded explanations of what PARA or memory systems are; every section earns its place.	5 / 5
Actionability	Concrete paths, executable qmd commands, and a referenced YAML schema give mostly executable guidance, but entity lifecycle operations (supersede, archive, weekly rewrite) are described as prose instructions rather than copy-paste templates.	4 / 5
Workflow Clarity	Multi-step processes (heartbeat extraction, weekly synthesis, superseding) are sequenced, but destructive/batch operations like superseding facts and moving folders to archives lack explicit validation checkpoints, so per the rubric cap workflow_clarity cannot exceed 3.	3 / 5
Progressive Disclosure	The body is a clear overview with a single, well-signaled one-level-deep reference ("see references/schemas.md", a verified real file) for the YAML schema and decay rules, with content appropriately split.	5 / 5
	Total	17 / 20 Passed

Description

78%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 well-structured, answering both what and when with explicit trigger guidance and a clear niche. Trigger-term coverage is strong; the only weakness is that the named actions are somewhat generic verbs.

Dimension	Reasoning	Score
Specificity	Names the PARA memory domain plus three concrete actions ("store, retrieve, and organize"), but the verbs are generic and coverage is not comprehensive, fitting anchor 3 rather than the broader action list of anchor 4.	3 / 5
Completeness	Explicitly answers both what ("file-based PARA memory system to store, retrieve, and organize durable knowledge across sessions") and when ("Trigger on saving facts, daily notes..."), matching the anchor 5 example structure.	5 / 5
Trigger Term Quality	"Trigger on saving facts, daily notes, entity records, weekly synthesis, recall, tacit user patterns, or plan memory" offers good natural-phrase coverage a user would actually say, though a few synonyms/variations are missing.	4 / 5
Distinctiveness Conflict Risk	The PARA memory niche with specific triggers (entity records, weekly synthesis, tacit patterns, plan memory) is mostly distinct with only minor overlap risk against generic note-taking skills.	4 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: paperclipai/paperclip
Path: skills/para-memory-files/SKILL.md
Commit: 890ab9a

Reviewed: about 17 hours 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.