agentleFS
gokulsvisiongokulsvision/Crewm8-Social-Media-Manager-Skill-Graph/skills/trends/trending-briefing/SKILL.md

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

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
  1. Distinctive:

    Filter ruthlessly: Not every trend makes the briefing.

    line 54
  2. Distinctive:

    No walls of text. 2-3 minute read max.

    line 62
  3. Distinctive:

    Not tracking what the founder finds useful

    line 110
  4. Distinctive:

    Read your briefing in under 2 minutes.

    line 114

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

CadenceFormatIdeal LengthDelivery
DailyBullet scan5-8 items, 250-400 wordsDM, email, or Slack
WeeklyStructured report10-15 items, 500-800 wordsDoc or email
Event/CrisisRolling update3-5 items, 100-200 wordsReal-time messaging

Procedure

  1. Aggregate inputs from monitoring period: trends, news, competitor activity, audience conversations, engagement spikes.
  2. Filter ruthlessly. Not every trend makes the briefing. Filter: "would this change anything the founder does today?" If no, cut it.
  3. 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)
  4. 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)
  5. 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:

  1. 5-8 items for daily, 10-15 for weekly
  2. Each item has a "why it matters" and "action" component
  3. Briefing is readable in under 3 minutes
  4. At least 1 action item for the founder
  5. 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?

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.