Skills Finder logo

Skills Finder

Community
wquguru
skills-finder

Find Agent Skills on skills.sh and adopt only the ones that pass a security audit. Use when the user wants to discover, search for, evaluate, or install a third-party skill ("find a skill for X", "is this skill safe to install", "search skills.sh", "what skill should I use for Y"). Always runs the skills.sh security audit before recommending or installing anything, and refuses to adopt skills that fail the audit.

Overview

Publisherwquguru
Repositoryskills
Skill nameskills-finder
Stars
94
Forks
7
Bundled files
3
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by wquguru on GitHub. Read the source before you install it.

Installation

Install the Skills Finder AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/wquguru/skills/tree/main/skills/skills-finder
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/wquguru/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/skills-finder .claude/skills/skills-finder
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Skills Finder in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Skills Finder on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Skills Finder is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Skills Finder

Discover skills on skills.sh and gate every candidate through a security audit before adopting it. The user's rule is firm: only adopt skills with no security problems. Never install a skill that has not cleared the audit.

Workflow

1. DISCOVER   npx skills find "<query>"          → candidate list
2. GATE       scripts/audit.py <candidate>...     → ADOPT / REVIEW / REJECT
3. DECIDE     adopt only ADOPT (or REVIEW after explicit user OK)
4. INSTALL    npx skills add <owner/repo@skill>   → only for approved skills

Step 1 — Discover (no token needed)

Use the skills CLI; it handles auth internally, so no Vercel token is required:

bash
npx -y skills@latest find "<query>"            # e.g. "pdf", "postgres backup"
npx -y skills@latest find "<query>" --owner <github-owner>   # scope to an owner

Output lines look like owner/repo@skill <N> installs plus a https://skills.sh/owner/repo/skill URL. Higher installs ≠ safer — still gate.

Other CLI verbs: npx skills list (installed), npx skills add <owner/repo@skill> (install), npx skills use <owner/repo@skill> (one-off prompt, no install).

Step 2 — Security gate (MANDATORY, no token needed)

Run every candidate through the audit script. The audit endpoint is public, so this always works:

bash
python3 scripts/audit.py <candidate> [<candidate> ...]   # human-readable
python3 scripts/audit.py <candidate> --json              # machine-readable

A <candidate> is any of: owner/repo@skill, owner/repo/skill, github/owner/repo@skill, or a full https://skills.sh/... URL — paste the identifier or URL straight from find output.

The script queries all providers (Gen Agent Trust Hub, Socket, Snyk, Runlayer, ZeroLeaks) and prints one verdict per skill. Process exit code = the worst verdict across all inputs.

Step 3 — Decide (the policy)

VerdictExitMeaningAction
ADOPT0Every provider pass; no risk above NONE/SAFESafe to install
REVIEW10No fail, but a warn or LOW/MEDIUM riskDo not auto-install — show the user the flagged provider + summary and ask before proceeding
REJECT20A provider returned fail, or risk is HIGH/CRITICALRefuse. Do not install. Report which provider failed and why
UNVERIFIED30No audits exist yet (404)Treat as not-yet-safe. Do not auto-install; offer to inspect the source first

Rules:

  • Default to safety. Only ADOPT installs without asking. REJECT and UNVERIFIED are never installed. REVIEW requires explicit user consent and you must surface the specific risk (provider, riskLevel, summary).
  • When recommending from a list, prefer ADOPT skills. If only REVIEW/REJECT skills exist, say so plainly rather than installing a borderline one.
  • Always tell the user the verdict and the deciding provider(s) — don't hide a warn/fail behind a recommendation.

Step 4 — Install approved skills

bash
npx -y skills@latest add <owner/repo@skill>          # project scope
npx -y skills@latest add <owner/repo@skill> --global # user scope

To inspect source before trusting a borderline (REVIEW/UNVERIFIED) skill without installing, use npx skills use <owner/repo@skill> or read the files via the detail endpoint (see references/api-reference.md — needs a Vercel token).

API details

For raw endpoints, response fields, identifier mapping, and how to obtain a Vercel OIDC token for the token-gated discovery endpoints, read references/api-reference.md. The everyday flow above needs no token.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Skills Finder AI skill do?

Find Agent Skills on skills.sh and adopt only the ones that pass a security audit. Use when the user wants to discover, search for, evaluate, or install a third-party skill ("find a skill for X", "is this skill safe to install", "search skills.sh", "what skill should I use for Y"). Always runs the skills.sh security audit before recommending or installing anything, and refuses to adopt skills that fail the audit.

Why use Skills Finder on TypingMind?

Because you install it once and use it with any model. Skills Finder is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Skills Finder in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/wquguru/skills/tree/main/skills/skills-finder. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Skills Finder?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Skills Finder?

As many as you like. As long as a model supports skills, you can use Skills Finder with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Skills Finder AI skill free?

It is published on GitHub by wquguru. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇