Feedback on your content-trend-researcher skill

[RichardHightower]

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 skill way more scannable.

Other Things Worth Fixing

1. Add trigger phrases to your description — Right now it just says what the skill does. Add explicit "Use when asked to..." language. That's a quick 2-point gain and makes discoverability way better.

2. Cut the second-person voice — Phrases like "This skill acts as your content intelligence system" and "help you" feel marketing-y. Switch to imperative: "Analyzes trends across 10+ platforms to generate article outlines." More instructional, less sales pitch.

3. Merge redundant sections — Your "What This Skill Does" and "Capabilities" sections are basically saying the same thing twice. One consolidated section cuts bloat and saves ~30 lines.

4. Add a workflow section with numbered steps — Right now it jumps from "When to Use" straight to "Example Invocations." Add 1. Specify topic → 2. Run analysis → 3. Review insights → 4. Generate outlines. That's a solid 3-point bump on Ease of Use.

Quick Wins

• Move 140+ lines to references/platforms.md (+7 points, immediate PDA improvement)
• Add trigger phrases to frontmatter description (+2 points)
• Cut second-person voice throughout (+2 points)
• Merge What/Capabilities sections (+3 points token economy)

These four changes alone push you from 66 to ~80 with maybe 30 minutes of work.

---

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