notion-uploader-downloader

I took a look at your notion-uploader-downloader skill and wanted to share some thoughts.

Links:

• GitHub
• SkillzWave Marketplace

The TL;DR

You're at 87/100, solidly in B territory. This is based on Anthropic's Claude Skills best practices. Your strongest area is Ease of Use (24/25) — the metadata, discoverability, and workflow clarity are really well done. The weakest spot is Spec Compliance (13/15), mostly because the description is missing trigger phrases that help the classifier understand when to invoke your skill.

What's Working Well

• Progressive Disclosure Architecture is tight — You've got a clean 3-tier structure with an orchestrator routing to on-demand guides and references. Token economy is excellent (9/10) with explicit counts for each tier.
• Discoverability is chef's kiss — Your decision tree in the trigger terms section is super clear with explicit keywords like "upload to Notion", "download from Notion", "recursive download". This makes it obvious when to use the skill.
• Your metadata frontmatter is complete — Name, version, allowed-tools, tier budgets, requirements — all there. This directly enables the ease-of-use score.
• Command examples everywhere — You've got input/output pairs for all workflows, plus the .env.notion template. That's the kind of friction-reduction that matters.

The Big One: Missing Trigger Phrases

Your description in SKILL.md is missing actual trigger phrases. Right now it's:

description: Bidirectional sync between Markdown and Notion. Upload .md files with images to Notion pages/databases...

This costs you 2 points on spec compliance. Rewrite it to include explicit triggers like:

description: Performs bidirectional Markdown-Notion synchronization. Use when asked to "upload markdown to Notion", "download from Notion", "sync Notion pages", "append to Notion", or "recursive Notion download".

This matters because the grading classifier uses those phrases to understand when your skill should be invoked. Without them, it has to guess.

Other Things Worth Fixing

1. Add TOC to configuration-guide.md — It's ~294 lines without a table of contents. Your error-resolution.md has a nice one; copy that pattern. Easy +1 point.

2. Trim IMPLEMENTATION_SUMMARY.md — Contains session notes like "What We Accomplished Today" that inflate tokens without adding technical value. Remove the developer diary stuff, keep the reference content. Small win on writing style.

3. Second-person voice in guides — Phrases like "User must provide" should be "Markdown file path required" or similar passive construction. Mostly in upload-workflow.md around line 45. Brings writing style to 9/10.

4. Flatten the penalties — You've got -4 modifiers (mostly from XML tags in metadata). Not a blocker, but worth reviewing if those are truly necessary.

Quick Wins

• Add trigger phrases to description (+2 points → 89/100)
• Add TOC to configuration-guide.md (+1 point)
• Trim implementation summary verbosity (+1 point)
• Clean up second-person voice in workflows (+1 point)
• These four changes alone get you to 90+, into A territory

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that installs skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.