trending-briefing
Skill17 starsChanged 7 months agoMITView on GitHub
Compile a daily or weekly "what's trending" briefing for the founder — concise, scannable summary of topics, formats, news, and opportunities the brand should know about.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- zdz2333/skillstheir own version, first seen Apr 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- zdz2333/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository40 other files it gives its agents.
- ab-test-analyzeSkill
- metrics-trackSkill
- performance-reportSkill
- caption-draftSkill
- cta-craftSkill
- hook-writeSkill
- post-createSkill
- thread-createSkill
- apology-draftSkill
- crisis-respondSkill
- impersonator-monitorSkill
- comment-replySkill
- dm-respondSkill
- engagement-pollSkill
- influencer-outreachSkill
- mention-monitorSkill
- cadence-timingSkill
- content-calendarSkill
- presence-refreshSkill
- profile-auditSkill
- cross-post-adaptSkill
- draft-reviewSkill
- schedule-queueSkill
- thread-structureSkill
- blog-to-threadSkill
- newsletter-to-postsSkill
- podcast-to-clipsSkill
- competitor-content-auditSkill
- prospect-social-auditSkill
- social-profile-discoverSkill
- brand-voice-systemSkill
- content-pillarsSkill
- crm-social-bridgeSkill
- positioning-statementSkill
- news-responseSkill
- trend-monitorSkill
- asset-formatSkill
- image-promptSkill
- meme-createSkill
- visual-planSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 54
Filter ruthlessly: Not every trend makes the briefing.
- Distinctive: line 62
No walls of text. 2-3 minute read max.
- Distinctive: line 110
Not tracking what the founder finds useful
- Distinctive: line 114
Read your briefing in under 2 minutes.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Trending Briefing
Compile a concise daily or weekly briefing on what's trending in the brand's space. The founder doesn't have time to live on social media — this skill turns noise into signal: the 5-10 things they actually need to know.
Purpose
The founder should never have to ask "what's happening on social?" This briefing pre-empts that question. It's designed to be read in 2 minutes, acted on in 5 minutes, and filed away for content planning reference.
When to Use
- Daily: end-of-day or next-morning founder briefing
- Weekly: Friday or Monday summary
- Pre-content-planning: briefing to inform the calendar
- Founder asks "what am I missing?"
Inputs Required
- Trend monitor outputs (from
trend-monitor) - News response decisions (from
news-response) - Competitor activity observations
- Brand engagement data (from
metrics-track) - Content calendar (for relevance context)
Quick Reference
| Cadence | Format | Ideal Length | Delivery |
| Daily | Bullet scan | 5-8 items, 250-400 words | DM, email, or Slack |
| Weekly | Structured report | 10-15 items, 500-800 words | Doc or email |
| Event/Crisis | Rolling update | 3-5 items, 100-200 words | Real-time messaging |
Procedure
- Aggregate inputs from monitoring period: trends, news, competitor activity, audience conversations, engagement spikes.
- Filter ruthlessly. Not every trend makes the briefing. Filter: "would this change anything the founder does today?" If no, cut it.
- For each briefing item:
- Trend/topic (1 line)
- Why it matters (1 line — relevance to brand)
- What brand did or should do (1 line — action/opportunity)
- Structure for scanability:
- No walls of text. 2-3 minute read max.
- Bullet format, bold key terms
- Most important item first
- At least 1 "opportunity" item (not just monitoring)
- Add founder action items:
- "Reply to this yourself"
- "Review this draft"
- "Decision needed: ride this trend or skip?"
Output Format
# [Daily/Weekly] Trending Briefing: [Date]
## Top of Mind (Must See)
- **[Topic]:** [Summary. Why it matters. What we should do.]
## Things Happening
- **[Trend]:** [Summary. Relevance. Action or note.]
...
## Competitor Watch
- **[Competitor]** — [What they did. Lessons for us?]
## Opportunities
- [Trend with specific brand angle suggestion]
- [Comment opportunity — specific account + post]
## Founder Action Items
- [ ] [Action: reply / review / decide]Done Criteria
The skill is complete when:
- 5-8 items for daily, 10-15 for weekly
- Each item has a "why it matters" and "action" component
- Briefing is readable in under 3 minutes
- At least 1 action item for the founder
- Items filtered by relevance (not everything makes the cut)
Pitfalls
- Including too much detail (founder skims, doesn't study)
- Items without action implications ("X is trending" — so what?)
- Same format every session (founder stops reading)
- Adding filler items (better 3 high-signal items than 10 bullets)
- Not tracking what the founder finds useful
Verification
Read your briefing in under 2 minutes. Did you get the most important information? Is there at least one item the founder can act on? Would you forward this if you were paying yourself $500/hour for their time?
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

