Daily Featured Skills Count
4,605 4,651 4,689 4,727 4,753 4,784 4,818
04/26 04/27 04/28 04/29 04/30 05/01 05/02
♾️ Free & Open Source 🛡️ Secure & Worry-Free

Import Skills

Composite Most Downloads Most Likes Most Comments Newest
chernistry chernistry
from GitHub Development & Coding
  • 📁 scripts/
  • 📄 SKILL.md
agent agents kill

bernstein-agents

Manage Bernstein agents — list active agents, inspect their output, kill stalled agents, or stream live logs. Use when the user asks about agents, wants to see what an agent is doing, or needs to kill one. --- # Bernstein Agent Management Inspect, monitor, and control active Bernstein agents. ## When to Use - User asks "what agents are running?" or "show me the agents" - User wants to see what a specific agent is working on - User says "kill that agent" or "stop the backend agent" - User asks "why is that agent stuck?" or wants to inspect agent output - User wants to see agent logs ## Instructions ### List agents 1. Run `scripts/agents.sh list` to get all active agents. 2. Present them clearly: ``` ## Active Agents (3) | Agent | Role | Model | Status | Task | Runtime | Cost | |-------|------|-------|--------|------|---------|------| | ses-a1b2 | backend | claude-sonnet-4 | alive | TASK-042: Fix auth | 4m 12s | $0.32 | | ses-c3d4 | qa | gpt-4.1 | alive | TASK-043: Write tests | 2m 45s | $0.18 | | ses-e5f6 | frontend | claude-sonnet-4 | stalled | TASK-044: Update UI | 8m 03s | $0.51 | ``` ### Inspect agent 3. To see what an agent is doing: `scripts/agents.sh logs <session_id>` 4. Show the last ~20 lines of output. ### Kill agent 5. To kill a stalled or misbehaving agent: `scripts/agents.sh kill <session_id>` 6. Confirm: "Agent ses-e5f6 terminated. Task TASK-044 returned to open queue." ### Stall detection 7. If any agent shows `stalled` status, proactively suggest killing it. 8. An agent is stalled if it hasn't sent a heartbeat in >60 seconds.

⬇0 ❤54 27 days ago · Uploaded Detail →
OpenAEC-Foundation OpenAEC-Foundation
from GitHub Content & Multimedia
  • 📁 references/
  • 📄 SKILL.md
cross-app multi-app override

frappe-agent-architect

Use when designing multi-app Frappe architectures, deciding whether to split functionality into separate apps, or implementing cross-app communication patterns. Prevents monolithic app sprawl, circular dependencies between apps, and broken override chains. Covers multi-app architecture decisions, app dependency management, cross-app hooks, override patterns, when to split vs extend, shared DocType strategies.

⬇0 ❤55 1 month ago · Uploaded Detail →
iPythoning iPythoning
from GitHub Business & Operations
  • 📁 .sync/
  • 📁 deploy/
  • 📁 docs/
  • 📄 .gitignore
  • 📄 ANTI-AMNESIA.md
  • 📄 CHANGELOG.md
layer whatsapp+telegram+email multi-channel

b2b-sdr-agent

Open-source B2B AI SDR template. 7-layer context system with 10-stage sales pipeline, 4-layer anti-amnesia memory, 13 automated cron jobs, WhatsApp IP isolation, multi-channel (WhatsApp+Telegram+Email). Built on OpenClaw.

⬇0 ❤55 1 month ago · Uploaded Detail →
Xquik-dev Xquik-dev
from GitHub Data & AI
  • 📄 SKILL.md
account follow which

check-mutuals

Use when the user wants to check mutual follows on X (Twitter) - which accounts follow each other, or which of account A's followers also follow account B. Useful for relationship mapping and social graph analysis. Read-only.

⬇0 ❤55 1 month ago · Uploaded Detail →
sinaptik-ai sinaptik-ai
from GitHub Databases & Storage
  • 📁 scripts/
  • 📄 SKILL.md
data database user

data-analysis

Use this skill when the user asks to analyze data from CSV, JSON, Excel, or database exports — including exploring datasets, computing statistics, creating visualizations, finding patterns, cleaning data, or building dashboards. Trigger whenever the user provides a data file and wants insights, charts, or transformations.

⬇0 ❤55 1 month ago · Uploaded Detail →
VeryGoodOpenSource VeryGoodOpenSource
from GitHub Data & AI
  • 📁 references/
  • 📄 SKILL.md
approaches through implementation

brainstorm

Explores requirements and approaches through collaborative dialogue before planning implementation. Use when user says "brainstorm", "explore idea", "what should we build", "think through this", or "let's discuss approaches".

⬇0 ❤48 15 days ago · Uploaded Detail →
koriym koriym
from GitHub Data & AI
  • 📄 SKILL.md
php coverage profile

xdebug

PHP debugging and analysis tools using Xdebug. Use when asked to trace, debug, profile, or analyze coverage of PHP code. Trigger phrases include "trace this function", "profile this code", "check coverage", "debug PHP", "set breakpoint", "find the bottleneck", "why is this slow", "トレース", "プロファイル", "カバレッジ".

⬇0 ❤47 13 days ago · Uploaded Detail →
stevenflanagan1 stevenflanagan1
from GitHub Content & Multimedia
  • 📄 SKILL.md
client social-creative-designer content-calendar

brand-onboarding

Brand onboarding setup skill. Captures a client's visual identity, content patterns, audience, and goals through evidence capture + pre-filled client doc + structured intake. Writes context/brand-style.md as the foundation for all social skills. Run once per client before using /social-creative-designer, /content-calendar, or /caption-writer.

⬇0 ❤54 29 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