- 📁 resources/
- 📄 bmad-skill-manifest.yaml
- 📄 SKILL.md
bmad-tea
Master Test Architect and Quality Advisor. Use when the user asks to talk to Murat or requests the Test Architect.
9 days ago · Uploaded
Detail →
Daily Featured Skills Count
04/05
04/06
04/07
04/08
04/09
04/10
04/11
♾️ Free & Open Source 🛡️ Secure & Worry-Free
Import Skills
- 📄 LICENSE.txt
- 📄 SKILL.md
ab-test-generator
Generate A/B test variants for affiliate content. Triggers on: "create A/B test", "test my headline", "optimize my CTA", "generate variants", "split test ideas", "improve click-through rate", "test my landing page copy", "headline alternatives", "CTA variations", "which version is better", "optimize conversions", "test my email subject line", "compare approaches".
12 days ago · Uploaded
Detail →
- 📄 SKILL.md
create-integration-test
Write an end-to-end integration test for the CodeScene MCP Server, covering file structure, backend abstraction, MCPClient usage, test registration, and verification.
11 days ago · Uploaded
Detail →
- 📄 SKILL.md
add-test-case
Add a new conformance test case to auth-testing-library. Use when adding a new test for auth endpoints (sign-up, sign-in, session, sign-out).
5 days ago · Uploaded
Detail →
- 📄 SKILL.md
sample-skill
A sample skill for testing - must be at least 20 characters
6 days ago · Uploaded
Detail →
- 📁 _build/
- 📁 _data/
- 📁 _includes/
- 📄 .gitignore
- 📄 _headers
- 📄 _redirects
htest
Use when writing or modifying tests with hTest (htest.dev) — JS-first or HTML-first. Use when a project has htest.dev in devDependencies or uses `npx htest` to run tests. Use when writing declarative tests as nested object literals, or reftest tables in HTML.
9 days ago · Uploaded
Detail →
- 📁 evals/
- 📁 references/
- 📄 SKILL.md
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.
12 days ago · Uploaded
Detail →
- 📄 SKILL.md
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.
12 days ago · Uploaded
Detail →
- 📄 SKILL.md
bubbletea-testing
Use this skill whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go. Triggers include any mention of testing Bubble Tea models, teatest, golden file testing for TUIs, testing tea.Cmd or tea.Msg, snapshot testing terminal output, or writing tests for any Go CLI/TUI that uses the Elm Architecture (Init/Update/View). Also use when the user asks about testing bubbletea components, bubbles, or lipgloss-styled views, or when they need CI-friendly TUI test patterns. Even if they just say "test my TUI" or "add tests to my Bubble Tea app", use this skill.
9 days ago · Uploaded
Detail →
- 📄 SKILL.md
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.
11 days ago · Uploaded
Detail →
- 📁 references/
- 📄 SKILL.md
e2e-test
End-to-end integration tests for Grafana Lens agent tools against a live LGTM stack. Detects local code changes and runs targeted tests for affected tools.
8 days ago · Uploaded
Detail →
- 📄 SKILL.md
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.
5 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.
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