document-processing-xlsx

I took a look at your document-processing-xlsx skill and wanted to share some thoughts.

Links:

• GitHub
• Your skill in the SkillzWave marketplace

TL;DR

You're at 51/100 – that's F territory, which means this needs some real work before it's ready. This is based on Anthropic's skill best practices around architecture, usability, and utility.

Your strongest area is Spec Compliance (12/15) – the frontmatter is clean and the name format is solid. The biggest gaps are Progressive Disclosure Architecture (10/30) and Ease of Use (14/25). You're losing a lot of points on structure and workflow clarity.

What's Working Well

• Clean metadata – Your YAML frontmatter is valid with required fields, and the hyphen-case naming is correct
• Good trigger discovery – You've packed the description with relevant terms (Excel, xlsx, import, export, reports) that make the skill findable
• Realistic scope – The skill tackles a genuine problem that developers actually need solved

The Big One: Duplicate Sections & No Architecture

Here's what's holding you back the most: you've got two identical "When to use this skill" sections taking up lines 8-29, and the entire skill lives in one flat 42-line file with zero reference documents.

Why it matters: This wastes tokens and signals that the skill isn't organized for progressive disclosure. More critically, it tells users "here's everything you need" upfront, which violates how agentic skills should layer information.

The fix:

1. Merge the duplicate sections into one consolidated "When to use this skill" section
2. Create a references/ directory with:
   • references/library-comparison.md – Compare xlsx v...