Daily Featured Skills Count
3,840 3,909 3,920 3,927 3,966 4,007 4,027
04/06 04/07 04/08 04/09 04/10 04/11 04/12
♾️ Free & Open Source 🛡️ Secure & Worry-Free

Import Skills

Composite Most Downloads Most Likes Most Comments Newest
SoulPass-AI SoulPass-AI
from GitHub Blockchain & Web3
  • 📁 references/
  • 📄 .gitignore
  • 📄 README.md
  • 📄 SKILL.md
agent trading solana

soulpass

Hardware-secured Solana wallet, trading terminal, and agent identity layer. Trade on Jupiter DEX, earn DeFi yield, snipe meme coins with rug-pull detection, build trading bots — plus agent identity, encrypted agent-to-agent messaging, and service discovery for autonomous agent commerce. All signed by Apple Secure Enclave (no .env private keys). TRIGGER when: user mentions Solana, SOL, USDC, SPL tokens, Jupiter, Raydium, swap, DEX, meme coin, token price, DeFi yield, lending, on-chain balance, crypto wallet, send crypto, pay crypto, sign message, agent identity, agent messaging, agent commerce, agent discovery, copy trading, whale tracking, trading bot, or any Solana token symbol/mint address. Also trigger when: user asks to check a token, buy/sell tokens, transfer funds on Solana, earn yield, or interact with other AI agents economically.

⬇0 ❤6 8 days ago · Uploaded Detail →
Wh1isper Wh1isper
from GitHub Tools & Productivity
  • 📁 .github/
  • 📁 .vscode/
  • 📁 docs/
  • 📄 .env.example
  • 📄 .gitattributes
  • 📄 .gitignore
automation agents agent

agent-builder

Build AI agents using ya-agent-sdk with Pydantic AI. Covers agent creation via create_agent(), toolset configuration, session persistence with ResumableState, subagent hierarchies, and browser automation. Use when creating agent applications, configuring custom tools, managing multi-turn sessions, setting up hierarchical agents, or implementing HITL approval flows.

⬇0 ❤7 12 days ago · Uploaded Detail →
dadwadw233 dadwadw233
from GitHub Tools & Productivity
  • 📁 agents/
  • 📁 references/
  • 📄 LICENSE.txt
  • 📄 SKILL.md
automation strategy agent

agent-design-coach

Help developers design or review useful, controllable, extensible agentic systems and products. Use when the user is designing an agent architecture, harness, tool system, memory strategy, permission model, interaction loop, recovery plan, or evaluation strategy, or when they want to turn a vague vibe-coded agent idea into a disciplined product plan. Do not use for simple code generation, generic brainstorming, or purely cosmetic UI critique.

⬇0 ❤5 6 days ago · Uploaded Detail →
PRDicta PRDicta
from GitHub Tools & Productivity
  • 📁 assets/
  • 📁 hooks/
  • 📁 references/
  • 📄 GETTING_STARTED.md
  • 📄 SKILL.md
automation session agent

solitaire

Persistent memory and evolving identity for AI agents. Gives your agent a knowledge graph, session continuity, persona management, and adaptive retrieval that survives across sessions. Boot at session start, ingest every turn. Your agent remembers everything.

⬇0 ❤5 6 days ago · Uploaded Detail →
ScientiaCapital ScientiaCapital
from GitHub Tools & Productivity
  • 📁 reference/
  • 📄 config.json
  • 📄 SKILL.md
agent task automation

agent-capability-matrix

Map task types to the best agent, skill, model, and fallback. Route any task to the right tool. Use when: which agent, route task, agent for this, best agent, capability matrix.

⬇0 ❤6 9 days ago · Uploaded Detail →
blaizew blaizew
from GitHub Tools & Productivity
  • 📁 .claude-plugin/
  • 📁 commands/
  • 📁 lib/
  • 📄 .gitignore
  • 📄 .mcp.json
  • 📄 browse-multi-mcp.js
automation agent browse

browse-multi

Concurrent browser automation via persistent headless Chromium daemons with MCP interface. Each agent gets its own named instance (~200ms/command after first call). DEFAULT tool for all agent browsing. Every agent and sub-agent that needs to browse the web MUST use browse-multi, not Playwright MCP. Playwright MCP is reserved for the user's interactive use only (logging in, exporting session cookies). Use when an agent or sub-agent needs to browse the web, scrape a page, interact with a site, fill forms, take screenshots, or extract content. Triggers on: "browse this site," "scrape this page," "navigate to," "check this URL," "take a screenshot of," "fill out this form," "read this page," or any task requiring web access beyond WebFetch.

⬇0 ❤6 9 days ago · Uploaded Detail →
13luiz 13luiz
from GitHub Tools & Productivity
  • 📁 data/
  • 📁 evals/
  • 📁 examples/
  • 📄 README.md
  • 📄 README.zh.md
  • 📄 skill.json
harness agent audit

harness-engineering-guide

Audit, design, and implement AI agent harnesses for any codebase. A harness is the constraints, feedback loops, and verification systems surrounding AI coding agents — improving it is the highest-leverage way to improve AI code quality. Three modes: Audit (scorecard), Implement (set up components), Design (full strategy). Use whenever the user mentions harness engineering, agent guardrails, AI coding quality, AGENTS.md, CLAUDE.md setup, agent feedback loops, entropy management, AI code review, vibe coding quality, harness audit, harness score, AI slop, agent-first engineering. Also trigger when users want to understand why AI agents produce bad code, make their repo work better with AI agents, set up CI/CD for agent workflows, design verification systems, or scale AI-assisted development. Proactively suggest when discussing AI code drift or controlling AI-generated code quality. --- # Harness Engineering Guide You are a harness engineering consultant. Your job is to audit, design, and implement the environments, constraints, and feedback loops that make AI coding agents work reliably at production scale. **Core Insight**: Agent = Model + Harness. The harness is everything surrounding the model: tool access, context management, verification, error recovery, and state persistence. Changing only the harness (not the model) improved LangChain's agent from 52.8% to 66.5% on Terminal Bench 2.0. ## Pre-Assessment Gate Before running an audit, answer these 5 questions to determine the appropriate audit depth. 1. Is the project expected to live beyond 1 month? 2. Will AI agents modify this codebase going forward? 3. Does the project have (or plan to have) >500 LOC? 4. Has there been at least one instance of AI-generated code causing problems? 5. Is there more than one contributor (human or agent)? | "Yes" Count | Route | What You Get | |-------------|-------|--------------| | **4-5** | **Full Audit** | All 45 items scored across 8 dimensions. Detailed report with improvement

⬇0 ❤6 10 days ago · Uploaded Detail →
toejough toejough
from GitHub Tools & Productivity
  • 📄 SKILL.md
frontend automation agent

engram-agent

Use when acting as a reactive memory agent watching engram chat for agent intents. Surfaces relevant feedback AND facts against intended behaviors, learns new memories from user corrections, observed failures, and conversation observation. Requires use-engram-chat-as skill for coordination protocol.

⬇0 ❤5 6 days ago · Uploaded Detail →
OshanKHZ OshanKHZ
from GitHub Tools & Productivity
  • 📁 examples/
  • 📁 references/
  • 📁 scripts/
  • 📄 SKILL.md
agent frontmatter automation

agent-development

Generates Claude Code plugin agent .md files: writes YAML frontmatter (name, model, color, tools, hooks, disallowedTools), crafts system prompts, and creates triggering example blocks with context and commentary. Validates agent structure against naming, length, and format constraints. Use when the user asks to create an agent, add an agent, write a subagent, configure agent frontmatter, design agent system prompts, set agent tools or colors, build an autonomous agent, or add agent hooks. --- # Agent Development for Claude Code Plugins Agents are autonomous markdown files with YAML frontmatter that handle multi-step tasks independently. Agents are for autonomous work; commands are for user-initiated actions. ## Workflow 1. Define agent purpose and triggering conditions 2. Create `agents/agent-name.md` with frontmatter + system prompt body 3. Include 2-4 `<example>` blocks in description 4. Validate structure (see constraints below) 5. Test triggering with real scenarios 6. If validation fails: check error recovery table, fix, re-validate ## Agent File Template ```markdown ---

⬇0 ❤5 6 days ago · Uploaded Detail →
morph-l2 morph-l2
from GitHub Tools & Productivity
  • 📁 .claude-plugin/
  • 📁 .cursor-plugin/
  • 📁 contracts/
  • 📄 .gitignore
  • 📄 CHANGELOG.md
  • 📄 LICENSE
automation payment agent

morph-skill

AI Agent skill for Morph L2 — wallet, explorer, DEX swap, cross-chain bridge with order management, EIP-8004 agent identity & reputation, alt-fee gas payment, EIP-7702 delegation, and x402 payment protocol

⬇0 ❤6 10 days ago · Uploaded Detail →

Skill File Structure Sample (Reference)

skill-sample/
├─ SKILL.md              ⭐ Required: skill entry doc (purpose / usage / examples / deps)
├─ manifest.sample.json  ⭐ Recommended: machine-readable metadata (index / validation / autofill)
├─ LICENSE.sample        ⭐ Recommended: license & scope (open source / restriction / commercial)
├─ scripts/
│  └─ example-run.py     ✅ Runnable example script for quick verification
├─ assets/
│  ├─ example-formatting-guide.md  🧩 Output conventions: layout / structure / style
│  └─ example-template.tex         🧩 Templates: quickly generate standardized output
└─ references/           🧩 Knowledge base: methods / guides / best practices
   ├─ example-ref-structure.md     🧩 Structure reference
   ├─ example-ref-analysis.md      🧩 Analysis reference
   └─ example-ref-visuals.md       🧩 Visual reference

More Agent Skills specs Anthropic docs: https://agentskills.io/home

SKILL.md Requirements

├─ ⭐ Required: YAML Frontmatter (must be at top)
│  ├─ ⭐ name                 : unique skill name, follow naming convention
│  └─ ⭐ description          : include trigger keywords for matching
│
├─ ✅ Optional: Frontmatter extension fields
│  ├─ ✅ license              : license identifier
│  ├─ ✅ compatibility        : runtime constraints when needed
│  ├─ ✅ metadata             : key-value fields (author/version/source_url...)
│  └─ 🧩 allowed-tools        : tool whitelist (experimental)
│
└─ ✅ Recommended: Markdown body (progressive disclosure)
   ├─ ✅ Overview / Purpose
   ├─ ✅ When to use
   ├─ ✅ Step-by-step
   ├─ ✅ Inputs / Outputs
   ├─ ✅ Examples
   ├─ 🧩 Files & References
   ├─ 🧩 Edge cases
   ├─ 🧩 Troubleshooting
   └─ 🧩 Safety notes

Why SkillWink?

Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.

We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.

Keyword Search Version Updates Multi-Metric Ranking Open Standard Discussion

Quick Start:

Import/download skills (.zip/.skill), then place locally:

~/.claude/skills/ (Claude Code)

~/.codex/skills/ (Codex CLI)

One SKILL.md can be reused across tools.

FAQ

Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.

1. What are Agent Skills?

A skill is a reusable capability package, usually including SKILL.md (purpose/IO/how-to) and optional scripts/templates/examples.

Think of it as a plugin playbook + resource bundle for AI assistants/toolchains.

2. How do Skills work?

Skills use progressive disclosure: load brief metadata first, load full docs only when needed, then execute by guidance.

This keeps agents lightweight while preserving enough context for complex tasks.

3. How can I quickly find the right skill?

Use these three together:

  • Semantic search: describe your goal in natural language.
  • Multi-filtering: category/tag/author/language/license.
  • Sort by downloads/likes/comments/updated to find higher-quality skills.

4. Which import methods are supported?

  • Upload archive: .zip / .skill (recommended)
  • Upload skills folder
  • Import from GitHub repository

Note: file size for all methods should be within 10MB.

5. How to use in Claude / Codex?

Typical paths (may vary by local setup):

  • Claude Code：~/.claude/skills/
  • Codex CLI：~/.codex/skills/

One SKILL.md can usually be reused across tools.

6. Can one skill be shared across tools?

Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.

Example: retrieval + writing + automation scripts as one workflow.

7. Are these skills safe to use?

Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.

8. Why does it not work after import?

Most common reasons:

  • Wrong folder path or nested one level too deep
  • Invalid/incomplete SKILL.md fields or format
  • Dependencies missing (Python/Node/CLI)
  • Tool has not reloaded skills yet

9. Does SkillWink include duplicates/low-quality skills?

We try to avoid that. Use ranking + comments to surface better skills:

  • Duplicate skills: compare differences (speed/stability/focus)
  • Low quality skills: regularly cleaned up