trend-research

I was curious how trend research fits into the Claude Code ecosystem—looks like you're tackling something pretty niche. With a D-grade score though, there are some structural gaps we should dig into around how you're positioning this for developers.

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 69/100, solidly in D territory. This is based on Anthropic's Claude Skills best practices rubric. Your strongest area is Spec Compliance (12/15)—the YAML and naming are clean. But you're bleeding points on Progressive Disclosure Architecture (18/30) and Utility (13/20). The core problem: you've described what the skill does without showing how developers actually use it.

What's Working Well

• Spec compliance is tight. Valid YAML frontmatter, correct hyphen-case naming, required fields are there. No formatting complaints.
• Your research process has structure. The five numbered steps (daily scans, multi-platform coverage, filtering) give clear direction—that's solid.
• The use case is real. Social media teams do need trend monitoring; this addresses an actual problem.

The Big One: Missing Templates and Examples

Here's what's killing your score—you list four templates but provide zero actual examples:

- Trend bulletin (description, platform, example links, recommended angle).
- Approval checklist (brand, legal, partner).
- Creator shortlist with outreach status.
- "Trend viability" scoring sheet with fit/risk/shelf-life sliders.

But they don't exist. No reference files. No inline sample. A developer activating this skill has to reverse-engineer what a "viability scoring sheet" looks like.

Fix: Create a references/ folder with actual markdown templates:

• `references/trend-bulletin-temp...