lea

Stumbled across your skill while looking at the latest submissions—the approach here is solid, scoring an 86. One thing I'm curious about: what made you structure it this way instead of going with the more conventional pattern most skills use?

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 86/100, solid B territory. This is based on Anthropic's skill best practices. Your strongest area by far is Writing Style (9/10)—clean, imperative tone throughout. The weakest spot is Spec Compliance (12/15) where you're missing some trigger phrase coverage, but that's a quick fix.

What's Working Well

• Layered structure is chef's kiss: SKILL.md stays lean with the heavy lifting delegated to references/syntax.md and references/architecture.md. That's exactly what Progressive Disclosure Architecture should look like.
• Writing is consistently solid: No marketing fluff, no second-person rambling. Every sentence does work. "Use when writing, modifying, debugging, or understanding Lea code" tells me exactly what this is for.
• Reference files are well-organized: Two reference files, one level deep, exactly the right depth. Shows you understand the layering principle.
• Utility is legit: This fills a real gap for a niche language. The syntax examples and quick start actually teach something.

The Big One

syntax.md is 361 lines with no table of contents. When someone drops into a reference file that long, they're lost. You've got sections for Comments, Bindings, Functions, etc., but they can't scan to find what they need.

Add a TOC right after the title:

# Lea Syntax Reference

## Contents

- [Comments](#comments)
- [Bindings](#bindings)
- [Functions](#functions)
- [Pipes](#pipes)
- [Decorators](#decorators)

This alone gets you +3 points. I...