Workflow·Sales & CRM

Social Listening with TinyFish

Name: Social Listening with TinyFish
Author: tinyfish-io

Monitor brand mentions, sentiment, and industry chatter across the web using TinyFish Search and Fetch.

You say

Buy it · $45 Read it before you buy $45 Written by tinyfish-io · unverified publisher

Context cost: 7.7k tokensestimated from the bundle, loaded when it triggers
Bundle: 3 files · 30.9 kB1 script among them — read before you run
Licence: MITpaid listing
Last change: —no release on file
Servers it uses: Noneruns standalone

What it does

Monitor brand mentions, sentiment, and industry chatter across the web using TinyFish Search and Fetch. Use when a user asks to track what people are saying about a brand, product, or topic, run social listening, or get a pulse on public perception. If the user already named the target, proceed directly. Default time window is last 7 days. Always link every claim to its source URL.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Workflow

Runs a procedure end to end.

social media

Filed under

Sales & CRM

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md21.8 kB · 292 lines

--- name: tinyfish-social-listening description: Monitor brand mentions, sentiment, and industry chatter across the web using TinyFish Search and Fetch. Use when a user asks to track what people are saying about a brand, product, or topic, run social listening, or get a pulse on public perception. If the user already named the target, proceed directly. Default time window is last 7 days. Always link every claim to its source URL. ---

6# Social Listening with TinyFish

8Track brand mentions, sentiment, and industry chatter across the live web — forums, blogs, news, social platforms, and developer communities — using TinyFish Search and Fetch.

10**First step:** If the user already named the brand/topic, proceed directly. Otherwise, ask.

11**Default time window:** Last 7 days.

12**Always link every claim to its source URL.**

14## When To Use

16- User wants to know what people are saying about a brand, product, person, or topic.

17- User asks to monitor competitors or compare share of voice.

18- User wants sentiment analysis on a launch, feature, controversy, or trend.

19- User says "social listening," "brand monitoring," "reputation check," "buzz check," or "what's the internet saying about X."

20- User wants a recurring pulse on public perception (pair with a cron job).

22## Pre-flight Check (REQUIRED)

24```bash

25# 1. TinyFish CLI installed?

26which tinyfish && tinyfish --version || echo "TINYFISH_CLI_NOT_INSTALLED"

28# 2. Authenticated?

29tinyfish auth status

30```

32If CLI is not available, fall back to the TinyFish API with TINYFISH_API_KEY:

34```bash

35test -n "$TINYFISH_API_KEY" && echo "API_KEY_AVAILABLE" || echo "NO_TINYFISH_ACCESS"

36```

38If neither works, stop and tell the user to install or authenticate.

40---

42## Core Workflow

44### Step 1 — Identify the target

46If the user already named the brand/topic, skip asking and proceed. Otherwise, ask what brand, product, or topic they want to research. Then set:

48- **Target entity:** Whatever the user specifies.

49- **Time focus:** Last 7 days. All search queries MUST include date constraints.

50- **Channels:** Reddit, Hacker News, Twitter/X, LinkedIn, blogs, news, GitHub, forums, YouTube.

51- **Sentiment lens:** General pulse.

53**⚠️ CRITICAL: STRICT 7-DAY ENFORCEMENT ⚠️**

54Search engines regularly return results older than 7 days regardless of date constraints in queries. You MUST:

551. Check the published_date field on every fetched result

562. Check date indicators in Reddit posts (e.g., "7d ago", "2mo ago") and other platforms

573. **DISCARD any result older than 7 days from today** — do NOT include it in the report, do NOT quote it, do NOT use it for sentiment classification

584. If most results are older than 7 days, say so honestly: "Limited discussion found in the last 7 days"

595. NEVER silently widen the window — if the 7-day window is thin, report that it's thin

606. In the final report, every source MUST have its date stated. Any source without a verifiable date within the last 7 days gets excluded.

62### Step 1.5 — Resolve X/Twitter handle (MANDATORY before any searches)

64**⛔ Do NOT guess the X handle. Do NOT skip this step.**

66Run a single search to find the brand's verified X handle:

68```bash

69tinyfish search query "{brand} site:x.com"

70```

72Look at the profile URLs that come back (e.g., x.com/Tiny_Fish, x.com/sudheenair). Extract the **primary brand handle** — this is the one you'll use in all X queries below. Also note any key people handles (CEO, founders) for additional queries.

74**Store the result:** VERIFIED_HANDLE={handle} — use this variable mentally for all X queries. If no profile URL comes back, note that X coverage will be limited.

76### Step 2 — Run multi-angle searches

78Run **parallel searches** across different angles. For most platforms, include date strings (e.g., {current month year}) to help narrow results. **⛔ EXCEPTION: X/Twitter queries MUST NOT include date strings** — tweets don't contain "2026" or "May 2026" in their text, so adding date strings causes the search engine to filter out real tweets before they reach you. Use snowflake decoding to date-gate X results AFTER they come back. This is the #1 cause of missing X coverage — the agent adds year/month to every query, search engines match on page text, and tweets silently disappear from results.

80#### 2a — X/Twitter searches (MANDATORY — all 3 patterns REQUIRED)

82**⛔ This is a separate mandatory block, not optional. All 3 query patterns below MUST run. The agent has historically skipped these and missed 80%+ of X activity as a result.**

84Generic site:x.com "{brand}" queries return mostly **profile page URLs** (undateable, useless). The following 3 patterns are specifically designed to return individual tweet URLs with /status/ IDs that can be snowflake-decoded:

86```bash

87# PATTERN 1: Brand's own tweets (returns /status/ URLs)

88# ⛔ NO date strings — tweets don't contain "2026" in text. Snowflake-decode dates after.

89tinyfish search query "x.com/{VERIFIED_HANDLE}/status"

90tinyfish search query "site:x.com/{VERIFIED_HANDLE}/status"

92# PATTERN 2: Anyone tagging the brand (returns /status/ URLs from other users)

93tinyfish search query "\"@{VERIFIED_HANDLE}\" site:x.com"

94tinyfish search query "@{VERIFIED_HANDLE} site:x.com"

96# PATTERN 3: Organic mentions by name without tagging (people discussing the brand in tweet text)

97tinyfish search query "site:x.com \"{brand}\""

98tinyfish search query "site:x.com \"{brand}.ai\""

100# PATTERN 4: Product-specific keywords (mine earlier snippets for these)

101tinyfish search query "site:x.com {brand} {product_keyword}"

102```

103

104**Verification gate:** After running all 3 patterns, count how many unique /status/ URLs you got. If fewer than 5, run additional queries using product-specific keywords found in the brand's recent announcements or from earlier search snippets (e.g., product names, feature launches, event names). Profile-page snippets from generic searches often contain recent tweet text — mine those for keywords to construct targeted follow-up queries.

105

106Also run queries for any key people handles identified in Step 1.5:

107```bash

108# ⛔ NO date strings for X — same rule applies to people handles

109tinyfish search query "x.com/{person_handle}/status {brand}"

110tinyfish search query "site:x.com/{person_handle}/status"

111```

112

113#### 2b — All other platform searches

114

115```bash

116# Direct brand mentions (last 7 days)

117tinyfish search query "{brand} {YYYY-MM-DD range, e.g. 'May 2026'}"

118

119# Reddit / forum discussions

120tinyfish search query "site:reddit.com {brand} {current month year}"

121

122# Hacker News discussions

123tinyfish search query "site:news.ycombinator.com {brand} {current month year}"

124

125# News coverage

126tinyfish search query "{brand} news {current month year}"

127

128# Developer community

129tinyfish search query "{brand} developer API feedback {current month year}"

130

131# Negative sentiment

132tinyfish search query "{brand} problems issues complaints {current month year}"

133

134# Positive sentiment

135tinyfish search query "{brand} love amazing best {current month year}"

136

137# LinkedIn

138tinyfish search query "site:linkedin.com {brand} {current month year}"

139

140# YouTube

141tinyfish search query "site:youtube.com {brand} {current month year}"

142```

143

144Replace {brand} with the user's target and use the current month/year for date context.

145

146Adapt queries to the domain:

147- **B2B SaaS**: add "pricing", "migration", "enterprise", "support experience"

148- **Consumer**: add "worth it", "alternatives", "honest review"

149- **Open source**: add "site:github.com", "contributing", "maintainer"

150- **Personal brand**: add "talk", "keynote", "interview", "thread"

151

152Run at least 4 search queries. Run up to 10 for comprehensive briefs.

153

154**⚡ EFFICIENCY: Run ALL searches + date gating + date verification in ONE execute_code block.** Use from hermes_tools import terminal to call TinyFish search from Python, then immediately dedup, date-gate, and verify YouTube dates (via curl) in the same block. Do NOT spread searches across multiple tool calls — the user sees each call as latency. One block, one wait. **Use scripts/social_listening_sweep.py as the template** — it handles all search queries, dedup, relevance filtering, X snowflake decoding, LinkedIn prefix heuristic, YouTube curl date-check, and Reddit snippet dates in a single block. Copy it, edit the CONFIG section, and run.

155

156### Step 3 — DATE GATE ON SEARCH RESULTS (mandatory BEFORE any fetching)

157

158**⛔ HARD STOP. Do NOT fetch ANY URLs until this gate is passed.**

159

160**THIS IS THE MOST IMPORTANT STEP IN THE ENTIRE SKILL. The agent has failed this gate 9 out of 11 times. The failure mode is ALWAYS the same: the agent sees rich older content in search snippets, feels a thin report is "wrong," and rationalizes widening the window. A thin report IS the correct output. You MUST resist this.**

161

162**COMMON FAILURE: fetching "to check the date."** The agent often fetches URLs before applying the date gate, rationalizing that it needs to verify dates via the published_date field. This is WRONG. The gate runs on SNIPPET data — dates visible in snippet text, URL paths, titles, and LinkedIn activity IDs. If the snippet doesn't show a date within the last 7 days, the URL is OUT. Do NOT fetch it "to be sure." Fetching is expensive (timeouts, rate limits) and defeats the purpose of the gate.

163

164**LinkedIn activity ID date trick:** LinkedIn post URLs contain an activity ID (e.g., activity-7460146798280507392). **Do NOT use the Twitter snowflake formula** ((id >> 22) + 1288834974657) — it produces garbage dates (2066+) for LinkedIn IDs. Instead, use the **prefix heuristic**: the first 5 digits of the activity ID correlate roughly with calendar dates. Calibration points (as of mid-2026): 74572 ≈ May 4, 74601 ≈ May 13. Extrapolate at ~3.2 units/day. If the prefix is clearly weeks below today's expected value, it's OUT without fetching.

165

166**⚠️ LinkedIn snippet "Xd ago" trap:** LinkedIn search snippets often include a sidebar of OTHER posts by the same author (e.g., "TinyFish 4d · We Shipped an MCP Server"). The "4d" label belongs to a *different post*, NOT the one in the URL. Always date-gate by the activity ID in the URL, never by relative-time labels in the snippet — they are almost always from adjacent feed items.

167

168For every search result from Step 2:

1691. **Check the snippet for a date.** Look for dates in the snippet text, URL path, or title.

1702. **Classify as IN or OUT.** A source is IN only if its date falls within the last 7 days from today's date. No date visible = OUT. Ambiguous date = OUT. **Exception for X tweets and YouTube:** these have reliable programmatic date extraction (snowflake IDs for tweets, publishDate in YouTube HTML) — use those techniques in the same execute_code block rather than discarding as "no date."

1713. **Drop every OUT source NOW.** Do not fetch it. Do not save it for "context." It does not exist.

1724. **Count what's left.** If 0 sources remain, SKIP Steps 4-5 entirely. The report is: "No verifiable discussion found in the last 7 days." Full stop. Do not pad the report with older material.

1735. **State ONE line** before proceeding: "📅 7-day filter: N of M sources passed." Do NOT show the full table.

174

175**NO EXCEPTIONS. NO RATIONALIZING. NO "expanded slightly to capture X." NO "context from older sources." NO "fetching to verify the date." If it's older than 7 days, it's DEAD. A 2-line report saying "nothing found this week" is infinitely better than a 50-line report full of stale data.**

176

177### Step 4 — Fetch ONLY the sources that passed the date gate

178

179Fetch 5–15 URLs from the IN list only. Prioritize:

1801. Active discussion threads (Reddit, HN, forums) — these have real opinions

1812. Recent news articles — for factual context

1823. Review/comparison posts — for structured sentiment

1834. LinkedIn posts — try fetching, fall back to snippets if auth wall

1845. **Skip X/Twitter URLs** — use search snippets directly (X blocks non-JS fetches)

185

186```bash

187tinyfish fetch content get --format markdown \

188 "https://reddit.com/r/..." \

189 "https://news.ycombinator.com/item?id=..." \

190 "https://techcrunch.com/..."

191```

192

193**Second date verification during fetch:** Check the published_date field in every fetch response. If it's older than 7 days, DISCARD the result immediately even if it passed the snippet gate — snippets can have misleading dates. For Reddit, also check the relative date in the post content (e.g., "7d ago", "2mo ago").

194

195### Step 5 — Synthesize the listening report

196

197Structure the output as a **Social Listening Report**:

198

199```markdown

200# Social Listening Report: {Brand/Topic}

201**Period:** {date range} · **Sources:** {count} across {channel types}

202

203## Sentiment

204{One-paragraph executive summary: positive/negative/mixed ratio, trending direction, key theme}

205

206## Key Discussions

2071. **[{Thread/article title}](url)** — {platform}, {date} — {summary + sentiment + standout quote if any}

2082. ...

209

210Embed praise, criticism, and notable quotes INSIDE each discussion entry rather than repeating them in separate sections. Each discussion should cover what was said (positive and negative) in one place.

211

212## Emerging Themes

213- {Pattern spotted across multiple sources}

214

215## Competitor Mentions (if relevant)

216- {Competitor}: {how they were mentioned} — [source](url)

217

218## Gaps & Caveats

219- {Platforms not covered, auth walls, thin data}

220```

221

222**Report style rules:**

223- Do NOT create separate "What People Love" / "What People Criticize" / "Notable Quotes" sections — fold those into Key Discussions to avoid repeating the same sources and quotes across multiple sections.

224- Each source should appear ONCE in the report. If a Reddit thread contains both praise and criticism, cover both under that thread's Key Discussion entry.

225- Adapt depth to the user's request — a quick "buzz check" gets a shorter summary, a comprehensive audit gets the full template.

226

227---

228

229## Recurring Monitoring

230

231If the user wants ongoing tracking, suggest a cron job:

232

233```

234Run this social listening report for {brand} every {Monday morning / daily / weekly}.

235Compare against previous results and highlight what changed.

236```

237

238For recurring runs, focus the report on **deltas**:

239- New mentions since last check

240- Sentiment shifts

241- New discussion threads

242- Emerging complaints or praise patterns

243

244---

245

246## Sentiment Classification Rules

247

248Classify each source into sentiment buckets using these signals:

249

250- **Positive**: praise words, recommendations, "switched to X and love it", high ratings, "best in class"

251- **Negative**: complaints, "disappointed", "switched away", bug reports, "overpriced", "broken"

252- **Neutral**: factual mentions, news coverage without opinion, documentation references

253- **Mixed**: threads with both praise and complaints, "great product but..."

254

255Count sources per bucket to give an overall sentiment ratio (e.g., "60% positive, 25% negative, 15% neutral").

256

257Do NOT use ML sentiment analysis — classify manually from the actual text. It's more accurate for this use case.

258

259---

260

261## Gotchas

262

263- **X/Twitter: snippets ONLY — no fetching, no browser** — X requires JavaScript rendering and blocks non-JS requests. tinyfish fetch will return empty "enable JavaScript" pages. Instead, use the **search result snippets** from tinyfish search query "site:x.com {brand}" as your X data source. Snippets contain the tweet text, author, and enough context for sentiment classification. Do NOT waste time trying to fetch X URLs — it will always fail. **⛔ Do NOT fall back to browser tools (browser_navigate, browser_vision, etc.) for X either.** The skill workflow is tinyfish search → snippets → report. If search snippets are thin, run MORE search query patterns with different keywords — do not switch tools. The browser requires login, is slow, and is not part of this workflow. State in the report that X coverage is snippet-based.

264- **X/Twitter date gating via tweet ID decoding** — Tweet URLs contain a status ID (e.g., x.com/user/status/2057955663125623243). You can decode the exact date using the Twitter snowflake formula: datetime.utcfromtimestamp(((int(tweet_id) >> 22) + 1288834974657) / 1000). This is the ONLY reliable way to date-gate X results — snippets rarely contain dates. Extract the status ID with regex r'x\.com/\w+/status/(\d+)', decode, and drop anything outside the 7-day window. Profile page URLs (no /status/) are undateable — discard them.

265- **X/Twitter search requires MULTIPLE query patterns** — A single site:x.com "brand" query returns mostly profile pages (x.com/username) and search pages, NOT individual tweets. The 3 mandatory patterns in Step 2a are specifically designed to return /status/ URLs. If you skip Step 2a or use generic site:x.com queries instead, you WILL miss 80%+ of X activity. This has happened repeatedly. The handle MUST be resolved first in Step 1.5 — do NOT guess it.

266- **LinkedIn posts are partially fetchable**

267- **Search engines ignore date constraints** — This is the #1 pitfall. Queries like "brand today" or "brand 2026-05-25" will still return results from months or years ago. You MUST verify dates independently via published_date in fetch results, or date indicators in the content itself (e.g., "7d ago" on Reddit). Never trust search recency — always verify.

268- **Brand name collisions in QUERIES, not filters** — common words as brand names (e.g., "Apple", "Mercury") will return irrelevant results. Add product-specific terms to **search queries** to disambiguate: "Mercury bank" NOT "mercury planet". Note: "TinyFish" itself is collision-prone — Reddit searches return watercolor paintings, aquarium fish, and fishing games. Add AI OR agent OR web OR scraping or use tinyfish.ai in quotes **in the query itself**. However, once results come back, the **relevance filter must only check two things**: (1) does the result mention the brand name? (2) is it within the 7-day window? Do NOT apply a secondary quality/signal-word gate (e.g., requiring "AI", "agent", "API" in the snippet). That over-filters and drops legitimate mentions — someone tweeting about TinyFish without using the word "agent" is still a valid mention. Disambiguation belongs in search queries, not in post-search filtering.

269- **YouTube fetch returns empty content** — tinyfish fetch on YouTube URLs returns only boilerplate (About/Press/Copyright). For date verification, use curl -s "URL" | grep -o '"publishDate":"[^"]*"' which reliably extracts the ISO date from YouTube's embedded JSON-LD. For video descriptions, use curl -s "URL" | grep -o '"shortDescription":"[^"]*"' and unescape \\n. For channel name, use grep -o '"ownerChannelName":"[^"]*"'. **macOS note:** Do NOT use grep -P (PCRE) — macOS grep doesn't support it. Use grep -o with basic or extended (-E) regex only.

270- **tinyfish fetch + piped parsing timeouts** — LinkedIn fetches via tinyfish fetch ... | python3 -c "..." in terminal() frequently time out (>30s). The reliable pattern is to use execute_code with from hermes_tools import terminal — this gives you a Python environment where you can call terminal and parse the JSON result without pipe overhead. Alternatively, fetch WITHOUT --format markdown to reduce latency.

271- **Reddit date verification is unreliable** — Multiple approaches fail: tinyfish fetch times out (>30s), curl to old.reddit.com returns no datetime= tags (likely bot-blocked), and Reddit's .json API returns empty responses. The only working heuristic is relative dates in search snippets ("7d ago", "2mo ago", "3 hours ago") — but these are often absent. If a Reddit thread has no dateable signal in the snippet, it's OUT. Do NOT waste time trying to fetch Reddit just to verify the date.

272- **Reddit rate limits** — TinyFish handles the fetching, but very long threads may be truncated. Fetch the top 2–3 threads rather than trying to get all of them.

273- **Recency bias** — search results skew toward recent and popular content. Explicitly note if you're missing older context.

274- **Platform gaps** — TinyFish Search covers the indexed web. Private Slack groups, Discord servers, and locked social posts won't appear. Note this limitation in the report.

275- **Sarcasm and context** — read full context before classifying sentiment. A quote like "great, another outage" is negative.

276- **Owned vs. earned media** — filter out the brand's own blog posts, press releases, and marketing pages unless the user explicitly wants to audit owned media presence.

277- **Don't hallucinate sentiment** — if search results are thin, say so. "Limited public discussion found" is better than fabricating a narrative.

278

279## Important Rules

280

281- **Use tinyfish search, NOT tinyfish agent** — search is fast and cheap. Agent is for interactive browser automation and is overkill for listening sweeps.

282- **Fetch real pages** — always fetch and read sources before classifying sentiment. Don't rely solely on snippets.

283- **ALWAYS link to sources** — every single claim, quote, data point, or sentiment observation in the report MUST include a clickable URL to the specific source. No exceptions. If you can't link it, don't include it. Use inline markdown links: [source](url). For quotes, link the platform and thread. For discussions, link the exact thread URL. For news, link the article. The reader should be able to click through and verify every statement in the report.

284- **Show the ratio** — always include a sentiment breakdown (positive/negative/neutral count or percentage).

285- **Be honest about gaps** — note which channels you couldn't cover and what might be missing.

286

287## References

288

289- https://docs.tinyfish.ai/search-api

290- https://docs.tinyfish.ai/fetch-api

291- https://docs.tinyfish.ai/for-coding-agents

292

In the file

SKILL.md3,311 words

Files3

LicenceMIT

Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈110

always loaded

The name and description, so the model knows the skill exists and when to reach for it.

7,615

on trigger

The instruction body and 2 supporting files, read only when the skill fires.

3.9%

of a 200k window

Ten skills this size would take about 39% of the window before you open a file.

050k100k150k200k context window

7.7k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption

Installsnone yet

Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for

Writes filesno

Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

If this is not it

26 other skills in Sales & CRM

What is in the bundle

3 files, 30.9 kB on disk. Mostly text — the instructions the model reads — with 1 script in it that your client would run only if the instructions tell it to.

README.md2.6 kB
SKILL.md21.8 kB
scripts/social_listening_sweep.py6.5 kB

What is not in it

A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 1 script beside the text, so the bundle is 3 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$45 once

Social Listening with TinyFish · MIT · tinyfish-io

one-time

Price$45 once

LicenceMIT — the author’s, unchanged by this purchase

Paid throughStripe, once, on the card you add at the checkout

Keeps workingfor good — the files are yours once they are on disk

Updatesevery update its author ships, delivered through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/

Claude Desktop

ChatGPT

Cursor.cursor/skills/

VS Code.github/skills/

Codex CLI.agents/skills/

Gemini CLI.gemini/skills/

Grok.grok/skills/

Zed.agents/skills/

Windsurf.windsurf/skills/

Agent SDK.claude/skills/

HTTP / API

This release

Versionnot versioned

Publishedno release date on file

Price$45

Referencetinyfish-io/social-listening-with-tinyfish

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

No earlier releases have been published to the marketplace.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Who wrote it

tinyfish-io

Publishes on mcprush.

0 servers listed1 skill listednot claimed

Profile

Publisher

Servers0