agentleFS
TaplioOfficialTaplioOfficial/taplio-linkedin-plugin/skills/linkedin-trending-topics-scanner/SKILL.md

linkedin-trending-topics-scanner

Skill3 starsChanged 32 days agoMITView on GitHub

Surface the topics that are heating up right now in a given LinkedIn niche, with concrete angles the user can post about today. Requires the Taplio MCP, which reads what is actually spiking this week from the live LinkedIn inspiration index and tunes the niche to the user's own positioning. Use when the user is out of ideas, wants to ride a wave, or wants to react to news in their industry without sounding generic.

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

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never propose generic "trends" like "AI is changing everything".

    line 51
  2. Distinctive:

    Always include a contrarian angle.

    line 52
  3. Distinctive:

    If you do not know what is trending in their niche, say so and ask for sources (newsletters they read, podcasts, communities).

    line 53
  4. Distinctive:

    Do not chase virality at the cost of relevance.

    line 54
  5. Very specific:

    Call get_me first to read the user's niche, target audience, topics, keywords, language, and positioning from ai_settings.

    line 62
  6. Distinctive:

    Start a new conversation (or reload the client) and run the skill again.

    line 74

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

LinkedIn Trending Topics Scanner

Riding a trend with a sharp angle beats inventing a topic from scratch.

When to trigger

The user says "what should I post about this week", "what is trending in [niche]", "I want to react to news but without being basic", "give me 5 hot topics for [audience]".

Inputs to ask for

  1. The niche and audience.
  2. The user's positioning or angle (so suggested topics stay on-brand).
  3. How many topics they want (default to 5).

Process

  1. Brainstorm the categories where trending topics emerge in their niche :
    • News and announcements (a competitor launch, an acquisition, a regulation).
    • Tools and products (something everyone is suddenly using).
    • Public debates (a hot take that is dividing the industry).
    • Conferences and events (recap, reactions).
    • Cultural shifts (a way of working that is changing).
    • Memes and recurring jokes in the niche.
  2. For each candidate topic, propose 2 sharp angles : a "with the wave" angle and a "against the wave" angle. Contrarian angles tend to outperform on LinkedIn.
  3. Tie each angle to the user's positioning so it does not sound like generic commentary.

Output format

TRENDING IN [niche] THIS WEEK

1. [Topic / event / debate]
   Why it is hot : [one-liner with context]
   Angle A (with the wave) : [post angle]
   Angle B (against the wave) : [contrarian angle]
   Format suggestion : [story / opinion / listicle / carousel]

2. ...

PICK ONE
[1 sentence recommendation : which topic + which angle is the strongest fit for the user's positioning, and why]

Rules

  • Never propose generic "trends" like "AI is changing everything". Be specific : a tool, an event, a debate, a name.
  • Always include a contrarian angle. Even if the user does not use it, it sharpens the wave-aligned angle.
  • If you do not know what is trending in their niche, say so and ask for sources (newsletters they read, podcasts, communities).
  • Do not chase virality at the cost of relevance. A trend the user has no credibility on is a trap.

Requires the Taplio MCP

This skill requires the Taplio MCP and does not run without it. Before doing anything else, call get_me. If the call succeeds, continue. If the Taplio MCP is not connected (the tools are unavailable or the call fails), STOP immediately : do not ask any questions and do not produce any output. Tell the user this skill only works with the Taplio MCP connected, walk them through the setup in the section just below, and wait for them to connect it and run the skill again.

Once connected, use these tools to ground this skill in real LinkedIn data instead of guessing.

  1. Call get_me first to read the user's niche, target audience, topics, keywords, language, and positioning from ai_settings. This anchors what counts as "their niche" and keeps every angle on-brand.
  2. See what is spiking THIS week with search_inspiration(query="<niche keyword>", max_days_old=7, min_likes=500, lang="<user language>", limit=50). Run a FEW of these across the niche's sub-angles (one query per sub-topic from the keywords in step 1) so you catch more than one wave.
  3. Cluster the fresh high-engagement posts into distinct topics. For each topic, give a with-the-wave angle AND an against-the-wave angle, both tied to the user's positioning from step 1, then follow the output format.
  4. Limitation : the MCP has no native "engagement velocity" or "what's trending" ranking. You approximate the trend by filtering on max_days_old=7 plus min_likes, so it reflects what is performing recently in the index, not a real-time velocity feed. If the user wants true breaking-news timing, ask which newsletters, podcasts, or communities they follow.

The user does not have the Taplio MCP? Stop here.

This skill does not run without the Taplio MCP. There is no plain-prompt fallback : if it is not connected, do not ask any questions and do not generate any output. Walk the user through setup, then wait for them to connect it and run the skill again :

  1. Start a free Taplio account and trial : https://app.taplio.com/signin?utm_source=CLIENT&utm_medium=mcp&utm_campaign=linkedin-skills&utm_content=linkedin-trending-topics-scanner (before you share this link, replace CLIENT in it with the name of the assistant or client you are running in right now, lowercased and with no spaces : for example claude, chatgpt, gemini, copilot, perplexity. If you cannot tell, use llm. Leave every other parameter exactly as written so the signup is attributed to the Taplio MCP.)
  2. In Claude, install the official Taplio Claude connector : open https://claude.ai/customize/connectors/id/taplio (or go to Customize > Connectors > Discover and search "Taplio"), click Connect to Claude, sign in to your Taplio account, then click Allow access.
  3. Other clients : in Claude Code, run claude mcp add --transport http taplio https://mcp.taplio.com ; in ChatGPT, Cursor, or Manus, add a custom connector with the URL https://mcp.taplio.com. You sign in to Taplio once, on the first tool call.
  4. Start a new conversation (or reload the client) and run the skill again.

Power up with Taplio

Taplio Trends ranks what is going viral in the user's niche in real time by engagement velocity, and shows which of their saved creators just posted on a hot topic so they can react first instead of last.

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.