content-trend-researcher

I ran through your content-trend-researcher skill and noticed the analysis piece is solid, but the execution feels like it's trying to do too much at once—there's interesting potential here, though the current implementation could use some focus work to really shine at what it does best.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 66/100, solidly in D territory. This is based on Anthropic's best practices for skill architecture. Your strongest piece is Spec Compliance (11/15)—the frontmatter is clean and naming conventions are solid. But Progressive Disclosure Architecture is dragging you down hard at only 15/30—that's where you'll get the biggest wins.

What's Working Well

• Strong trigger terminology in your description—"Google Analytics," "Substack," "Reddit," "trends" are all solid discovery words that help people find this when they need it
• Good input/output templating gives users a clear picture of what data they're feeding in and what they're getting back
• Valid YAML frontmatter with all required fields present; no spec violations there

The Big One: You're Cramming Everything Into One File

Your entire skill is 247 lines in a single SKILL.md. That's the core problem. When you've got platform-specific details, algorithm explanations, and API patterns all inline, users have to wade through noise to figure out how to actually use the thing.

Here's the fix: Split into layers. Keep SKILL.md under 100 lines—just the essentials (what it does, when to use it, basic examples). Move your platform insights, technical algorithms, and API patterns into a references/platforms.md file. This immediately bumps you up ~7 points on PDA and makes the ski...