personalization-logic

I found your personalization-logic skill while reviewing the latest batch—the approach to handling user preference trees is clever, but I'm seeing some gaps in how the spec translates into actual implementation that's dragging your score down to 68.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 68/100, which puts you in D territory—needs work but fixable. This is based on Anthropic's skill best practices rubric. Your strongest pillar is Spec Compliance (12/15), but you're getting dinged hard on Progressive Disclosure Architecture (18/30) and Utility (12/20). The gap between a solid framework and a usable skill is mostly missing concrete examples and templates.

What's Working Well

• Your framework is solid — the five-step flow (Segmentation Inputs → Content Blocks → Token Logic → Fallbacks → Testing) maps real personalization needs and shows you've thought through the domain.
• Spec compliance is tight — valid YAML frontmatter, correct naming convention (hyphen-case), and you're using consistent terminology throughout ("segment," "token," "module"). No conflicts there.
• Objectivity is clean — the tone stays instructional without marketing fluff, which is refreshing and appropriate for something this technical.

The Big One: Missing Templates and Examples

This is eating ~8 points and it's the easiest win. You mention three templates in your "Templates" section—personalization matrix, token dictionary, QA checklist—but they don't actually exist as reference files. You're telling people what to build without showing how.

Fix: Create three new files in a references/ directory:

• references/personalization-matrix-template.md — actual table showing segment vs. ...