/tinyskill
Enables Hermes to create new reusable skills for itself by researching live web sources with TinyFish Search and Fetch, analyzing source coverage, writing SKILL.md files, and installing them into Hermes memory. Use when the user asks Hermes to learn, teach itself, upgrade
$ npx -y skills add tinyfish-io/tinyfish-cookbook --skill tinyskill --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
/tinyskill
Context preview
The summary Claude sees to decide when to auto-load this skill.
Enables Hermes to create new reusable skills for itself by researching live web sources with TinyFish Search and Fetch, analyzing source coverage, writing SKILL.md files, and installing them into Hermes memory. Use when the user asks Hermes to learn, teach itself, upgrade
SKILL.md
tinyskill.SKILL.mdname: self-improve-with-tinyfish
description: Enables Hermes to create new reusable skills for itself by researching live web sources with TinyFish Search and Fetch, analyzing source coverage, writing SKILL.md files, and installing them into Hermes memory. Use when the user asks Hermes to learn, teach itself, upgrade itself, or save a reusable capability.
Self-Improve With TinyFish
When To Use
Use this skill when the user asks Hermes to:
- Learn a new tool, API, framework, workflow, or domain for future tasks.
- Create, install, or improve a reusable Hermes skill.
- Research official docs and examples before writing procedural memory.
- "Teach yourself," "upgrade yourself," or "make a skill for this."
Do not use this skill for ordinary one-off answers unless the user explicitly wants a saved skill.
Pre-flight Check (REQUIRED)
Before making any TinyFish call, determine which mode to use.
**1. Check for CLI:**
which tinyfish && tinyfish --version || echo "TINYFISH_CLI_NOT_FOUND"
**2. If CLI is found, check auth:**
tinyfish auth status
If authenticated, use **CLI mode** for all searches and fetches below.
**3. If CLI is not found, check for API key:**
test -n "$TINYFISH_API_KEY" && echo "API_KEY_AVAILABLE" || echo "TINYFISH_API_KEY is not set"
If the API key is available, use **API mode** for all searches and fetches below.
**4. If neither CLI nor API key is available**, stop and tell the user: > Install the TinyFish CLI: `npm install -g @tiny-fish/cli` > Then authenticate: `tinyfish auth login` > > Or set `TINYFISH_API_KEY` in your environment. Get a key at: https://agent.tinyfish.ai/api-keys
Do NOT proceed until one mode is confirmed.
---
Core Workflow
1. Acknowledge the learning request.
- Send a short progress update: `I'll research this with TinyFish and create a reusable skill.`
- Extract a clean skill topic from the user request.
- Preserve constraints such as "check official docs," "cover all endpoints," "focus on errors," or "make it production-ready."
2. Search with TinyFish.
- Use the CLI or API (whichever passed pre-flight).
- Run multiple targeted searches.
- Prefer official docs and authoritative examples first.
- Do not invent URLs.
3. Analyze search results.
- Review titles, snippets, URLs, site names, and ranks.
- Decide if the current sources cover setup, main workflow, edge cases, and validation.
- If coverage is weak, run follow-up searches before fetching.
4. Fetch selected URLs.
- Use TinyFish Fetch for known URLs.
- Fetch 3-8 strong sources by default.
- Prefer markdown output.
- Continue if one URL fails; replace critical failed sources with another search result.
5. Write the new skill.
- Create a focused `SKILL.md`.
- Make it procedural and reusable.
- Include gotchas, defaults, validation, and references.
- Do not dump raw docs.
6. Install and verify.
- Save the generated skill using Hermes skill management.
- Verify with `skill_view` or `skills list`.
- Tell the user only the skill name and that it can be used going forward.
---
Search Pattern
Use TinyFish Search when you need ranked web results, snippets, and URLs.
CLI mode
tinyfish search query "{topic} official documentation" --prettyRun multiple searches:
tinyfish search query "{topic} official documentation"
tinyfish search query "{topic} API reference"
tinyfish search query "{topic} quickstart examples"
tinyfish search query "site:github.com {topic} examples issues"
tinyfish search query "{topic} common errors best practices"For API skills, add:
tinyfish search query "{topic} authentication"
tinyfish search query "{topic} SDK reference"
tinyfish search query "{topic} rate limits errors"For framework skills, add:
tinyfish search query "{topic} production best practices"
tinyfish search query "{topic} testing debugging deployment"API mode (fallback)
python3 - <<'PY'
import json
import os
import urllib.parse
import urllib.request
query = "Remotion official docs best practices"
api_key = os.environ["TINYFISH_API_KEY"]
url = "https://api.search.tinyfish.ai?query=" + urllib.parse.quote(query)
req = urllib.request.Request(url, headers={"X-API-Key": api_key})
with urllib.request.urlopen(req, timeout=15) as res:
data = json.load(res)
for r in data.get("results", [])[:10]:
print(json.dumps({
"position": r.get("position"),
"site_name": r.get("site_name"),
"title": r.get("title"),
"url": r.get("url"),
"snippet": r.get("snippet"),
}, ensure_ascii=False))
PYRun the same query variations listed in CLI mode above, substituting the `query` variable each time.
---
Search Analysis Loop
After each search pass, decide:
- Do I have at least one official source?
- Do I have setup or authentication covered?
- Do I have the main workflow covered?
- Do I have enough code or command examples?
- Do I have likely mistakes and validation checks?
- Are there duplicate or low-value sources I should ignore?
If no, send a short user update and run targeted follow-up searches.
Example update:
I found the official docs and examples. I'm checking for pitfalls and validation guidance before writing the skill.
---
Source Selection Rules
Prefer sources in this order:
1. Official docs, API references, quickstarts. 2. Official examples, cookbook repos, templates. 3. GitHub issues/discussions with concrete failure modes. 4. Stack Overflow answers for specific errors. 5. High-quality technical blog posts that fill real gaps.
Reject:
- Marketing pages without implementation detail.
- Duplicate docs pages.
- Outdated sources when official docs exist.
- Shallow posts that only repeat generic concepts.
Default to 3-8 fetched URLs total.
---
Fetch Pattern
Use TinyFish Fetch when you already know the URLs and need clean extracted content.
Read more
name: self-improve-with-tinyfish description: Enables Hermes to create new reusable skills for itself by researching live web sources with TinyFish Search and Fetch, analyzing source coverage, writing SKILL.md files, and installing them into Hermes memory. Use when the user asks Hermes to learn, teach itself, upgrade itself, or save a reusable capability.
Self-Improve With TinyFish
When To Use
Use this skill when the user asks Hermes to:
- Learn a new tool, API, framework, workflow, or domain for future tasks.
- Create, install, or improve a reusable Hermes skill.
- Research official docs and examples before writing procedural memory.
- "Teach yourself," "upgrade yourself," or "make a skill for this."
Do not use this skill for ordinary one-off answers unless the user explicitly wants a saved skill.
Pre-flight Check (REQUIRED)
Before making any TinyFish call, determine which mode to use.
**1. Check for CLI:**
which tinyfish && tinyfish --version || echo "TINYFISH_CLI_NOT_FOUND"
**2. If CLI is found, check auth:**
tinyfish auth status
If authenticated, use **CLI mode** for all searches and fetches below.
**3. If CLI is not found, check for API key:**
test -n "$TINYFISH_API_KEY" && echo "API_KEY_AVAILABLE" || echo "TINYFISH_API_KEY is not set"
If the API key is available, use **API mode** for all searches and fetches below.
**4. If neither CLI nor API key is available**, stop and tell the user: > Install the TinyFish CLI: `npm install -g @tiny-fish/cli` > Then authenticate: `tinyfish auth login` > > Or set `TINYFISH_API_KEY` in your environment. Get a key at: https://agent.tinyfish.ai/api-keys
Do NOT proceed until one mode is confirmed.
---
Core Workflow
1. Acknowledge the learning request.
- Send a short progress update: `I'll research this with TinyFish and create a reusable skill.`
- Extract a clean skill topic from the user request.
- Preserve constraints such as "check official docs," "cover all endpoints," "focus on errors," or "make it production-ready."
2. Search with TinyFish.
- Use the CLI or API (whichever passed pre-flight).
- Run multiple targeted searches.
- Prefer official docs and authoritative examples first.
- Do not invent URLs.
3. Analyze search results.
- Review titles, snippets, URLs, site names, and ranks.
- Decide if the current sources cover setup, main workflow, edge cases, and validation.
- If coverage is weak, run follow-up searches before fetching.
4. Fetch selected URLs.
- Use TinyFish Fetch for known URLs.
- Fetch 3-8 strong sources by default.
- Prefer markdown output.
- Continue if one URL fails; replace critical failed sources with another search result.
5. Write the new skill.
- Create a focused `SKILL.md`.
- Make it procedural and reusable.
- Include gotchas, defaults, validation, and references.
- Do not dump raw docs.
6. Install and verify.
- Save the generated skill using Hermes skill management.
- Verify with `skill_view` or `skills list`.
- Tell the user only the skill name and that it can be used going forward.
---
Search Pattern
Use TinyFish Search when you need ranked web results, snippets, and URLs.
CLI mode
tinyfish search query "{topic} official documentation" --prettyRun multiple searches:
tinyfish search query "{topic} official documentation"
tinyfish search query "{topic} API reference"
tinyfish search query "{topic} quickstart examples"
tinyfish search query "site:github.com {topic} examples issues"
tinyfish search query "{topic} common errors best practices"For API skills, add:
tinyfish search query "{topic} authentication"
tinyfish search query "{topic} SDK reference"
tinyfish search query "{topic} rate limits errors"For framework skills, add:
tinyfish search query "{topic} production best practices"
tinyfish search query "{topic} testing debugging deployment"API mode (fallback)
python3 - <<'PY'
import json
import os
import urllib.parse
import urllib.request
query = "Remotion official docs best practices"
api_key = os.environ["TINYFISH_API_KEY"]
url = "https://api.search.tinyfish.ai?query=" + urllib.parse.quote(query)
req = urllib.request.Request(url, headers={"X-API-Key": api_key})
with urllib.request.urlopen(req, timeout=15) as res:
data = json.load(res)
for r in data.get("results", [])[:10]:
print(json.dumps({
"position": r.get("position"),
"site_name": r.get("site_name"),
"title": r.get("title"),
"url": r.get("url"),
"snippet": r.get("snippet"),
}, ensure_ascii=False))
PYRun the same query variations listed in CLI mode above, substituting the `query` variable each time.
---
Search Analysis Loop
After each search pass, decide:
- Do I have at least one official source?
- Do I have setup or authentication covered?
- Do I have the main workflow covered?
- Do I have enough code or command examples?
- Do I have likely mistakes and validation checks?
- Are there duplicate or low-value sources I should ignore?
If no, send a short user update and run targeted follow-up searches.
Example update:
I found the official docs and examples. I'm checking for pitfalls and validation guidance before writing the skill.
---
Source Selection Rules
Prefer sources in this order:
1. Official docs, API references, quickstarts. 2. Official examples, cookbook repos, templates. 3. GitHub issues/discussions with concrete failure modes. 4. Stack Overflow answers for specific errors. 5. High-quality technical blog posts that fill real gaps.
Reject:
- Marketing pages without implementation detail.
- Duplicate docs pages.
- Outdated sources when official docs exist.
- Shallow posts that only repeat generic concepts.
Default to 3-8 fetched URLs total.
---
Fetch Pattern
Use TinyFish Fetch when you already know the URLs and need clean extracted content.
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 - /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
Open skill

