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
b1rdmania b1rdmania
from GitHub Data & AI
  • 📁 evals/
  • 📁 references/
  • 📄 SKILL.md
test experiment better

ab-test-setup

When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," or "how long should I run this test." Use this whenever someone is comparing two approaches and wants to measure which performs better. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

⬇0 ❤24 12 days ago · Uploaded Detail →
antithesishq antithesishq
from GitHub Tools & Productivity
  • 📄 SKILL.md
triage test antithesis-triage

test:triage

This skill should be used when the user asks to "test the triage skill", "run triage tests", "validate antithesis triage", "test:triage", or "smoke test triage". Orchestrates end-to-end testing of the antithesis-triage skill by running real triage operations via sub-agents and reviewing the results for bugs, skill compliance issues, and papercuts. --- # Test: Antithesis Triage Skill End-to-end test harness for the `antithesis-triage` skill. Spawn sub-agents that perform real triage operations, then review their work for issues. **The top-level agent MUST NOT use the antithesis-triage skill directly.** All triage operations happen inside sub-agents. The top-level agent only orchestrates and reviews. ## Prerequisites Before starting, verify the same prerequisites the triage skill requires: ```bash which snouty && which agent-browser && which jq ``` Also confirm `ANTITHESIS_TENANT` is set: ```bash echo "$ANTITHESIS_TENANT" ``` If any prerequisite is missing, stop and report which ones are unavailable. ## Phase 1: Discover Runs Spawn a **general-purpose sub-agent** with the Agent tool. Provide these instructions, replacing `{{TENANT}}` with the actual value of the `$ANTITHESIS_TENANT` environment variable and `{{TRIAGE_SKILL}}` with the absolute path to `antithesis-triage/SKILL.md` in this repository: ``` Read the skill file at {{TRIAGE_SKILL}} and follow its instructions to list recent runs for the tenant "{{TENANT}}". Follow the "Summarize recent runs" workflow.

⬇0 ❤23 12 days ago · Uploaded Detail →
dlt-hub dlt-hub
from GitHub Tools & Productivity
  • 📄 SKILL.md
eval test triggers

create-eval

Create trigger evaluation setup for a toolkit skill. Use when the user wants to test whether a skill's description triggers correctly, set up eval workspaces, or generate trigger test queries for a skill. Use when user says 'create eval', 'test triggers', 'eval skill', or wants to measure skill triggering accuracy.

⬇0 ❤20 11 days ago · Uploaded Detail →
Umutayb Umutayb
from GitHub Development & Coding
  • 📄 SKILL.md
automation test pickleib

pickleib

Use this skill whenever writing, editing, or generating Cucumber/Gherkin tests with the Pickleib framework! Triggers on any mention of Pickleib, PickleibSteps, BuiltInSteps, page-repository.json, @PageObject, @ScreenObject, @FindBy page objects, CommonSteps, ObjectRepository, PickleibWebDriver, PickleibAppiumDriver, or any request to write, fix, or add to a Cucumber test in a test automation project. Also use when asked to add entries to a page-repository JSON file, define page objects, write feature files, select dropdowns, verify elements, or perform any browser/mobile interaction through Pickleib. Always consult this skill before generating test code or locator definitions — do not guess step syntax or method signatures. --- # Pickleib — Agent Skill A Cucumber-based test automation framework that decouples **element acquisition** (via JSON repository or Java Page Objects) from **element interaction** (via built-in Cucumber steps). Tests are written in Gherkin; raw Selenium/Appium calls never appear in feature files. ## Companion Skills | Skill | Activates when | What it does | |---|---|---| | `test-composer` | User asks to expand coverage or "add more scenarios" | Iterative test suite expansion across the full app | | `bug-discovery` | After test coverage is achieved | Adversarial bug hunting after tests pass | --- ## ABSOLUTE RULES **STOP. Read before any action.** ### 1. Do NOT skip stages This skill operates in four stages. Complete each stage and get user approval before advancing.

⬇0 ❤12 5 days ago · Uploaded Detail →
pvillega pvillega
from GitHub Data & AI
  • 📁 references/
  • 📄 SKILL.md
cases edge test

bugmagnet

Discover edge cases and test coverage gaps through systematic analysis. Use when analysing test coverage, finding bugs, hunting for edge cases, reviewing code for robustness, or when code-reviewer identifies test gaps. Also use when the user says things like "what could go wrong", "is this well tested", "find holes in my tests", "what am I missing", or asks about edge cases for any function or module.

⬇0 ❤13 12 days ago · Uploaded Detail →
imyousuf imyousuf
from GitHub Data & AI
  • 📄 SKILL.md
test make lint

atr-analyze

Run tests, linters, type checkers, and builds with AI-powered analysis. Use this INSTEAD OF running test/lint/build commands directly via Bash. Wraps any command (pytest, jest, go test, make test, npm test, make lint, mypy, tsc, eslint, golangci-lint, cargo clippy, make typecheck, make build, etc.) to produce clean summarized output, keeping conversation context small. When a test or lint fails, ATR analyzes the full output and returns actionable failure insights.

⬇0 ❤8 6 days ago · Uploaded Detail →
JUVOJustin JUVOJustin
from GitHub Business & Operations
  • 📁 references/
  • 📄 SKILL.md
tests test phpunit

application-testing

Write, extend, or debug PHPUnit application tests for this WordPress plugin. Use this skill whenever tests are involved — adding a test for a new feature, testing hook or filter behavior, testing WordPress data operations with factories, or when asked to "add a test", "write tests", "test this function", or "verify this behavior with a test". This skill is opinionated about the project's wp-env-based setup and supersedes any generic PHPUnit guidance. --- # Application Testing Tests run exclusively inside the `wp-env` test container. The bootstrap and PHPUnit config are pre-wired. Do not modify `tests/bootstrap.php` or `phpunit.xml.dist`. The plugin is already loaded when tests run — no manual require needed. For full reference including common patterns, plugin dependencies, and CI details, read `references/testing.mdx`. ## Running the test suite

⬇0 ❤8 9 days ago · Uploaded Detail →
djscheuf djscheuf
from GitHub Ops & Delivery
  • 📄 SKILL.md
test playwright logging

e2e-logging-and-artifacts

How to set up comprehensive logging and artifact extraction for Playwright e2e test suites. Use this skill when creating new e2e test suites, setting up Playwright from scratch, implementing BaseContext logging infrastructure, configuring test failure diagnostics, or adding custom test context logging. Essential for debugging e2e test failures with console logs, network logs, page errors, and Playwright artifacts (screenshots, videos, traces).

⬇0 ❤7 9 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