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

Import Skills

Composite Most Downloads Most Likes Most Comments Newest
keep-starknet-strange keep-starknet-strange
from GitHub Testing & Security
  • 📁 .agents/
  • 📁 .changeset/
  • 📁 .claude-plugin/
  • 📄 .coderabbit.yaml
  • 📄 .env.example
  • 📄 .gitignore
automation security devops

starknet-agentic-skills

Routes Starknet skill invocations to focused modules for contract authoring, testing, optimization, deployment, and audit workflows.

⬇0 ❤77 10 days ago · Uploaded Detail →
ClariSortAi ClariSortAi
from GitHub Ops & Delivery
  • 📁 references/
  • 📄 SKILL.md
devops plan interactive

onboarding

This skill should be used when the user asks to "set up OpenClaw", "get started", "onboard me", "plan my setup", or "help me choose channels". Conducts an interactive interview, then generates a tailored deployment plan.

⬇0 ❤72 11 days ago · Uploaded Detail →
mizchi mizchi
from GitHub Ops & Delivery
  • 📁 agents/
  • 📁 assets/
  • 📁 references/
  • 📄 LICENSE.txt
  • 📄 SKILL.md
cloudflare deploy devops

cloudflare-deploy

Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.

⬇0 ❤58 10 days ago · Uploaded Detail →
julianobarbosa julianobarbosa
from GitHub Ops & Delivery
  • 📁 references/
  • 📁 scripts/
  • 📁 templates/
  • 📄 SKILL.md
secrets devops environments

1password

Guide for implementing 1Password secrets management - CLI operations, service accounts, Developer Environments, and Kubernetes integration. Use when retrieving secrets, managing vaults, configuring CI/CD pipelines, integrating with External Secrets Operator, managing Developer Environments, or automating secrets workflows with 1Password.

⬇0 ❤49 8 days ago · Uploaded Detail →
mr-daedalium mr-daedalium
from GitHub Ops & Delivery
  • 📁 autoplan/
  • 📁 benchmark/
  • 📁 bin/
  • 📄 .env.example
  • 📄 .gitignore
  • 📄 .gitmodules
screenshots devops verify

ostack

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots.

⬇0 ❤51 12 days ago · Uploaded Detail →
Soneso Soneso
from GitHub Development & Coding
  • 📁 references/
  • 📄 SKILL.md
horizon devops php

stellar-php-sdk

Build Stellar blockchain applications in PHP using soneso/stellar-php-sdk. Use when generating PHP code for transaction building, signing, Horizon API queries, Soroban RPC, smart contract deployment and invocation, XDR encoding/decoding, and SEP protocol integration. Covers all 26 operations, 50 Horizon endpoints, 12 RPC methods, and 18 SEP implementations with synchronous Guzzle HTTP patterns.

⬇0 ❤41 7 days ago · Uploaded Detail →
juliuschun juliuschun
from GitHub Development & Coding
  • 📄 SKILL.md
deploy devops code

deploy

Deploy code to Cloudflare Pages (static) or Azure Container Apps (dynamic). Use when the user says "/deploy", "배포해줘", "이거 올려줘", "publish this", "사이트 배포", "앱 배포", or wants to deploy code from a project to production.

⬇0 ❤29 4 days ago · Uploaded Detail →
JayFarei JayFarei
from GitHub Development & Coding
  • 📄 SKILL.md
site vercel deploy

deploy-site

Deploy the opentraces.ai marketing site to Vercel production. Use when the user says "deploy site", "deploy to vercel", "push site", "ship the site", or "deploy-site". For a full coordinated release that includes a version bump and package publish alongside the site deploy, use /release-pack instead. --- # Deploy Site Deploy the Next.js marketing site (`web/site/`) to Vercel production. ## Context - **Project**: `opentraces` on Vercel (jayfareis-projects/opentraces) - **Framework**: Next.js 16 (App Router) - **Root directory**: Vercel is configured with root at `web/site/` - **Domain**: opentraces.ai - **Build**: `next build` (runs from `web/site/`) - **Version**: Auto-read from `src/opentraces/__init__.py` at build time via `next.config.ts` ## Steps ### 1. Verify build locally ```bash cd web/site && npm run build ``` If the build fails, fix issues before deploying. ### 2. Commit and push Ensure all changes are committed and pushed to `main`: ```bash git status git push origin main ``` ### 3. Deploy to Vercel Run the deploy from the **repo root** (not `web/site/`), because Vercel resolves the root directory from its project settings: ```bash cd /path/to/repo/root npx vercel --prod ``` ### 4. Verify Check the deployment URL in the Vercel output. The production URL is: ```

⬇0 ❤46 12 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