- 📁 references/
- 📁 templates/
- 📄 SKILL.md
vibe-notion
Interact with Notion using the unofficial private API - pages, databases, blocks, search, users, comments
19 days ago · Uploaded
Detail →
Daily Featured Skills Count
04/16
04/17
04/18
04/19
04/20
04/21
04/22
♾️ Free & Open Source 🛡️ Secure & Worry-Free
Import Skills
- 📄 SKILL.md
drt-create-sync
Generate a drt sync YAML configuration file. Use this skill whenever a user wants to create a new drt sync, connect a data warehouse table to an external service, or set up a Reverse ETL pipeline with drt. --- Create a drt sync YAML configuration file for the user. ## Steps 1. Ask the user for the following (or infer from context if already provided): - **Source table or SQL**: what data to sync (e.g. `ref('new_users')` or a SQL query) - **Destination**: where to send it (Slack, Discord, Microsoft Teams, REST API, HubSpot, GitHub Actions, Google Sheets, PostgreSQL, MySQL, ClickHouse, Parquet, CSV/JSON/JSONL, Jira, Linear, SendGrid, Staged Upload (async bulk APIs), or other) - **Sync mode**: full (every run), incremental (watermark-based, needs cursor column), upsert (dedup by key), or replace (TRUNCATE + INSERT for full table refresh) - **Frequency intent**: helps set `batch_size` and `rate_limit` 2. Generate a valid sync YAML using the exact field names from `docs/llm/API_REFERENCE.md`. 3. Output the YAML in a code block and suggest where to save it: `syncs/<name>.yml` 4. Show the command to validate and run it: ```bash drt validate drt run --select <name> --dry-run drt run --select <name> ``` ## Rules - Use `type: bearer` + `token_env` (never hardcode tokens) - Default `on_error: skip` for Slack/webhooks, `on_error: fail` for critical syncs - For incremental mode, always include `cursor_field` - Use `ref('table_name')` when the source is a single DWH table; raw SQL when filtering or joining - Jinja2 templates use `{{ row.<column_name> }}` — column names must come from the user ## Reference See `docs/llm/API_REFERENCE.md` for all fields, types, and defaults.
20 days ago · Uploaded
Detail →
- 📁 .archive/
- 📁 assets/
- 📁 docs/
- 📄 .gitignore
- 📄 .gitmodules
- 📄 bun.lock
content-alchemy
Transform raw ideas into professional articles through a 5-stage semi-automated pipeline.
20 days ago · Uploaded
Detail →
- 📁 .github/
- 📁 ai-context/
- 📁 assets/
- 📄 .dockerignore
- 📄 .geo-optimizer.example.yml
- 📄 .gitignore
geo-optimizer-skill
| Platform | File | How to use |
21 days ago · Uploaded
Detail →
- 📁 references/
- 📄 SKILL.md
create-output-format
Scaffold a new planning output format adapter. Creates a format directory with all required files implementing the output format contract.
22 days ago · Uploaded
Detail →
- 📁 references/
- 📄 LICENSE.txt
- 📄 SKILL.md
data-twingler
Execute SQL, SPARQL, SPASQL, SPARQL-FED, and GraphQL queries against live data spaces and knowledge graphs via OpenLink's OpenAPI-compliant web services. Use this skill whenever the user wants to query a database, RDF store, or SPARQL endpoint; explore a knowledge graph or data space; asks "How to ...", "Define the term ...", or poses a question against a known article or graph context; or mentions linkeddata.uriburner.com, Virtuoso, OPAL, or OpenLink services. Full query templates are in references/query-templates.md — load that file before constructing any predefined query.
18 days ago · Uploaded
Detail →
- 📁 references/
- 📄 SKILL.md
accessibility
This skill should be used when the user asks to "add accessibility", "check ARIA", "handle keyboard navigation", "add focus management", or creates UI components, forms, or interactive elements. Provides WCAG 2.2 AA patterns for keyboard navigation, ARIA roles and states, focus management, color contrast, and screen reader support.
22 days ago · Uploaded
Detail →
- 📄 SKILL.md
form-filling
Guide PDF or web form filling; use when structured form completion is requested.
21 days ago · Uploaded
Detail →
- 📄 requirements.txt
- 📄 SKILL.md
browser
Control a real, local web browser to search, navigate, and extract information.
22 days ago · Uploaded
Detail →
- 📄 SKILL.md
auto-create-connector
Autonomously create, test, and validate a data connector for any web platform — end to end. Use when asked to "auto-create a connector", "automatically build a connector", or when a connector needs to be created from scratch and tested without manual guidance.
23 days ago · Uploaded
Detail →
- 📄 SKILL.md
diagnose
Diagnose espresso extraction issues by correlating machine telemetry with taste feedback.
18 days ago · Uploaded
Detail →
- 📄 SKILL.md
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
20 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