project-memory

I took a look at your project-memory skill and wanted to share some thoughts.

Links:

• GitHub
• SkillzWave Marketplace

The TL;DR

You're at 92/100, solid A territory. This is based on Anthropic's skill best practices rubric. Your strongest area is Ease of Use (23/25)—the skill is genuinely discoverable and the four reference templates are well-structured. The weakest pillar is Spec Compliance (13/15), which is more of a technical formality than a real problem.

What's Working Well

• Templates hit the right level of detail. Your bugs_template.md, decisions_template.md, and others give concrete examples without being overwhelming. They're actually usable, not just theoretical.
• Trigger phrases are solid. Phrases like "set up project memory," "log a bug fix," and "document architectural decisions" make the skill discoverable. Someone could actually find this when they need it.
• The layered structure works. SKILL.md stays focused on the "why" and "what," while reference templates contain the actionable details. Good separation of concerns.
• Real problem being solved. Institutional knowledge loss across AI coding sessions is a genuine pain point that other skills don't address. Your positioning here is unique.

The Big One: Second-Person Voice in Workflows

This is holding you back about 1-2 points. Your example workflows use narrative style ("User: I'm getting a connection refused error") instead of imperative instructions. It reads more like documentation of a conversation than instructions for someone to actually follow.

Current approach:

User: "I'm getting a 'connection refused' error from the database"
-> Search docs/project_notes/bugs.md

Should be:

When encountering connection errors:
1. Search bugs.md: `grep -i 'connection' docs/project_notes/bugs.md`
2. Ap...