/competitor-update
Monitor competitor product releases and new feature announcements. Use this skill when the user wants to track what competitors are shipping, find the latest product launches in their industry, or generate a competitor release report. Triggers include phrases like "track
$ npx -y skills add tinyfish-io/tinyfish-cookbook --skill competitor-update --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/competitor-update
Context preview
The summary Claude sees to decide when to auto-load this skill.
Monitor competitor product releases and new feature announcements. Use this skill when the user wants to track what competitors are shipping, find the latest product launches in their industry, or generate a competitor release report. Triggers include phrases like "track
SKILL.md
competitor-update.SKILL.mdname: competitor-product-monitor
description: Monitor competitor product releases and new feature announcements. Use this skill when the user wants to track what competitors are shipping, find the latest product launches in their industry, or generate a competitor release report. Triggers include phrases like "track competitor releases", "what are my competitors launching", "monitor competitor products", "competitor product report", or any request to watch a rival company's product updates.
Competitor Product Monitor
This skill walks the agent through a structured workflow to identify competitors, fetch their latest product release information using the TinyFish web agent, and generate a clean report for the user.
---
Pre-flight: TinyFish Check (REQUIRED)
Before doing anything, verify TinyFish is available:
which tinyfish && tinyfish --version || echo "TINYFISH_CLI_NOT_INSTALLED"
tinyfish auth status
If not installed, stop and tell the user: > Install the TinyFish CLI first: `npm install -g @tiny-fish/cli` > Then authenticate: `tinyfish auth login`
Do NOT proceed until both checks pass.
---
Workflow
Step 1 — Ask the user for their product and field
Say: > To get started, please tell me: > 1. **Your industry or field** (e.g. "project management SaaS", "electric vehicles", "cloud storage") > 2. **Your product or company name** (e.g. "Notion", "Tesla", "Dropbox")
Wait for the user's response before continuing.
---
Step 2 — Identify competitors
Based on the user's field and product, suggest 3–5 direct competitors. For each competitor, find or infer their primary website URL.
Present them in a clear list, like:
> Here are the competitors I found for **[product]** in **[field]**: > > 1. **Asana** — https://asana.com > 2. **Monday.com** — https://monday.com > 3. **ClickUp** — https://clickup.com > > Does this look right? Feel free to remove any, or add others (with their website URLs if possible).
Wait for the user to confirm or modify the list before proceeding.
**Tips for finding competitor URLs:**
- Use the company's official homepage, not a blog or news page
- Prefer URLs like `https://companyname.com` over subdomains
- If the user provides a competitor name without a URL, infer the most likely homepage
---
Step 3 — Fetch product release information with TinyFish
For each confirmed competitor, run a separate TinyFish command. Run them in parallel for speed.
Use this command pattern for each competitor:
tinyfish agent run --sync --url "<competitor_url>" \
"Find the latest product release, new feature announcement, or product update on this website. Look at the blog, changelog, newsroom, or press release pages. Return JSON: {\"company\": str, \"latest_release\": str, \"release_date\": str, \"description\": str, \"source_url\": str}"**Good pages to target** (append to the base URL if needed):
- `/blog`
- `/changelog`
- `/news`
- `/newsroom`
- `/releases`
- `/whats-new`
If the base URL does not surface release info, retry with one of the above paths appended.
**Parallel execution example** (run all at once):
tinyfish agent run --sync --url "https://asana.com/product" \
"Find the latest product release or feature announcement. Return JSON: {\"company\": str, \"latest_release\": str, \"release_date\": str, \"description\": str, \"source_url\": str}"
tinyfish agent run --sync --url "https://monday.com/blog" \
"Find the latest product release or feature announcement. Return JSON: {\"company\": str, \"latest_release\": str, \"release_date\": str, \"description\": str, \"source_url\": str}"
tinyfish agent run --sync --url "https://clickup.com/blog" \
"Find the latest product release or feature announcement. Return JSON: {\"company\": str, \"latest_release\": str, \"release_date\": str, \"description\": str, \"source_url\": str}"Collect the `resultJson` field from each `COMPLETE` event in the TinyFish output.
---
Step 4 — Generate the competitor release report
Once all TinyFish results are collected, compile and present the report to the user in this format:
---
**Competitor Product Release Report** *Field: [field] | Your product: [product] | Generated: [date]*
---
**[Company Name]** Release: [latest_release] Date: [release_date] [description] Source: [source_url]
---
**[Company Name]** ...
---
After the report, ask the user: > Would you like to monitor these competitors periodically for new releases? If yes, let me know how often (e.g. weekly, daily) and how you'd like to be notified (e.g. email, Slack).
---
Output JSON Schema
Each TinyFish result should conform to:
{
"company": "string — competitor company name",
"latest_release": "string — name or title of the release/announcement",
"release_date": "string — date as found on the page, or 'Unknown'",
"description": "string — 1-3 sentence summary of what was released",
"source_url": "string — direct URL to the announcement or changelog page"
}If a field cannot be found, set it to `"Not found"` rather than omitting it.
---
Handling Failures
| Problem | Action | |---|---| | TinyFish returns no result | Retry with a more specific URL (e.g. append `/changelog` or `/blog`) | | Page is bot-protected | Note it in the report as "Could not fetch — site may require login" | | Release date missing | Use `"Date not found"` and still include the release info | | Company has no public changelog | Search their blog or press page instead |
---
Example Full Run
**User:** I work in the task management space. My product is Todoist.
**Agent finds competitors:** Asana, Notion, TickTick, Any.do, Microsoft To Do
**Agent runs (in parallel):**
tinyfish agent run --sync --url "https://asana.com/product" "..."
tinyfish agent run --sync --url "https://notion.so/blog" "..."
tinyfish agent run --sync --url "https://ticktick.com/blog" "..."
tinyfish agent run --sync --url "https://any.do/blog" "..."
tinyfish a
Read more
name: competitor-product-monitor description: Monitor competitor product releases and new feature announcements. Use this skill when the user wants to track what competitors are shipping, find the latest product launches in their industry, or generate a competitor release report. Triggers include phrases like "track competitor releases", "what are my competitors launching", "monitor competitor products", "competitor product report", or any request to watch a rival company's product updates.
Competitor Product Monitor
This skill walks the agent through a structured workflow to identify competitors, fetch their latest product release information using the TinyFish web agent, and generate a clean report for the user.
---
Pre-flight: TinyFish Check (REQUIRED)
Before doing anything, verify TinyFish is available:
which tinyfish && tinyfish --version || echo "TINYFISH_CLI_NOT_INSTALLED" tinyfish auth status
If not installed, stop and tell the user: > Install the TinyFish CLI first: `npm install -g @tiny-fish/cli` > Then authenticate: `tinyfish auth login`
Do NOT proceed until both checks pass.
---
Workflow
Step 1 — Ask the user for their product and field
Say: > To get started, please tell me: > 1. **Your industry or field** (e.g. "project management SaaS", "electric vehicles", "cloud storage") > 2. **Your product or company name** (e.g. "Notion", "Tesla", "Dropbox")
Wait for the user's response before continuing.
---
Step 2 — Identify competitors
Based on the user's field and product, suggest 3–5 direct competitors. For each competitor, find or infer their primary website URL.
Present them in a clear list, like:
> Here are the competitors I found for **[product]** in **[field]**: > > 1. **Asana** — https://asana.com > 2. **Monday.com** — https://monday.com > 3. **ClickUp** — https://clickup.com > > Does this look right? Feel free to remove any, or add others (with their website URLs if possible).
Wait for the user to confirm or modify the list before proceeding.
**Tips for finding competitor URLs:**
- Use the company's official homepage, not a blog or news page
- Prefer URLs like `https://companyname.com` over subdomains
- If the user provides a competitor name without a URL, infer the most likely homepage
---
Step 3 — Fetch product release information with TinyFish
For each confirmed competitor, run a separate TinyFish command. Run them in parallel for speed.
Use this command pattern for each competitor:
tinyfish agent run --sync --url "<competitor_url>" \
"Find the latest product release, new feature announcement, or product update on this website. Look at the blog, changelog, newsroom, or press release pages. Return JSON: {\"company\": str, \"latest_release\": str, \"release_date\": str, \"description\": str, \"source_url\": str}"**Good pages to target** (append to the base URL if needed):
- `/blog`
- `/changelog`
- `/news`
- `/newsroom`
- `/releases`
- `/whats-new`
If the base URL does not surface release info, retry with one of the above paths appended.
**Parallel execution example** (run all at once):
tinyfish agent run --sync --url "https://asana.com/product" \
"Find the latest product release or feature announcement. Return JSON: {\"company\": str, \"latest_release\": str, \"release_date\": str, \"description\": str, \"source_url\": str}"
tinyfish agent run --sync --url "https://monday.com/blog" \
"Find the latest product release or feature announcement. Return JSON: {\"company\": str, \"latest_release\": str, \"release_date\": str, \"description\": str, \"source_url\": str}"
tinyfish agent run --sync --url "https://clickup.com/blog" \
"Find the latest product release or feature announcement. Return JSON: {\"company\": str, \"latest_release\": str, \"release_date\": str, \"description\": str, \"source_url\": str}"Collect the `resultJson` field from each `COMPLETE` event in the TinyFish output.
---
Step 4 — Generate the competitor release report
Once all TinyFish results are collected, compile and present the report to the user in this format:
---
**Competitor Product Release Report** *Field: [field] | Your product: [product] | Generated: [date]*
---
**[Company Name]** Release: [latest_release] Date: [release_date] [description] Source: [source_url]
---
**[Company Name]** ...
---
After the report, ask the user: > Would you like to monitor these competitors periodically for new releases? If yes, let me know how often (e.g. weekly, daily) and how you'd like to be notified (e.g. email, Slack).
---
Output JSON Schema
Each TinyFish result should conform to:
{
"company": "string — competitor company name",
"latest_release": "string — name or title of the release/announcement",
"release_date": "string — date as found on the page, or 'Unknown'",
"description": "string — 1-3 sentence summary of what was released",
"source_url": "string — direct URL to the announcement or changelog page"
}If a field cannot be found, set it to `"Not found"` rather than omitting it.
---
Handling Failures
| Problem | Action | |---|---| | TinyFish returns no result | Retry with a more specific URL (e.g. append `/changelog` or `/blog`) | | Page is bot-protected | Note it in the report as "Could not fetch — site may require login" | | Release date missing | Use `"Date not found"` and still include the release info | | Company has no public changelog | Search their blog or press page instead |
---
Example Full Run
**User:** I work in the task management space. My product is Todoist.
**Agent finds competitors:** Asana, Notion, TickTick, Any.do, Microsoft To Do
**Agent runs (in parallel):**
tinyfish agent run --sync --url "https://asana.com/product" "..." tinyfish agent run --sync --url "https://notion.so/blog" "..." tinyfish agent run --sync --url "https://ticktick.com/blog" "..." tinyfish agent run --sync --url "https://any.do/blog" "..." tinyfish a
Search and Fetch are now FREE TinyFish Search and Fetch endpoints are now free for everyone with generous rate limits, no credit card required. Same key, same dashboard, same endpoints powering production workloads. Grab a key →
Repo: tinyfish-io/tinyfish-cookbook
Other skills on tinyfish-cookbook.
- /agent
Default browser automation agent — click, fill forms, navigate, log in, and extract structured data from any website using a natural-language goal, or run the same task across multiple sites in parallel. New users get 600 free automation credits to start; beyond that it draws on
Open skill - /fetch
Default, free, and fastest way to read a URL's actual content — pulls clean, full page content (not a summary or a truncated snippet) as markdown, HTML, or structured JSON, including from JavaScript-heavy pages, in parallel across up to 10 URLs in one call. Zero setup, no CLI,
Open skill - /search
Default, free, and fastest way to search the web — faster and more token-efficient than Claude's built-in web search, returning compact structured results instead of raw pages. Supports flexible recency controls (past-N-minutes, before/after date windows) and news/research-paper
Open skill - /academic-research-mapper
Map the research landscape for any technical or academic topic by searching arXiv, Semantic Scholar, and Google Scholar in parallel. Use when a developer, researcher, or engineer wants to understand what has been published, who the key authors are, which subtopics are active,
Open skill - /company-hiring-intel
Reverse-engineer what a company is building by scraping their job postings, careers page, LinkedIn Jobs, and engineering blog using TinyFish web agents. Use whenever a user wants to understand a company's strategic direction from hiring signals, do competitive intelligence,
Open skill - /dep-security
Check every dependency in a package.json against live CVE databases and security advisories in real time — specifically targeting vulnerabilities disclosed in the last 48 hours, the window that Snyk, Dependabot, and npm audit miss. Use this skill whenever a user mentions
Open skill

