Move records from an external source (CSV, JSON, SQL dump, or API response) into a live FileMaker solution via OData. Reads the source data, maps source columns to FM fields with type coercion, gets developer approval on the mapping, then executes the migration with error tracking. Use when the developer asks to "migrate data", "import records", "move data into FileMaker", "load CSV", or "import JSON".
Use when adding a new problem model to the codebase, either from an issue or interactively
Build, critique, and iterate high-converting marketing or product landing pages using React + Vite + TypeScript + Tailwind and shadcn/ui components, with all icons sourced from Iconify. Use when the user asks for a landing page, sales page, signup page, CRO improvements, above-the-fold vs below-the-fold structure, hero + CTA copy, section order, or wants production-ready shadcn + Vite code.
Unity API の探索と実行。u api schema で検索、u api call で任意の public static メソッドを呼ぶ。
This skill should be used when performing a structured, read-only code review of a file, module, diff, commit, or pull request, especially when the user asks to review a PR or diff, 审查一个模块或文件, 看看改动有没有问题, or coordinate multiple review perspectives from one manual entry point.
Compare ERB and JavaScript template outputs for the offline scoring SPA. Use when working on ERB-to-JS conversion, debugging template parity issues, or verifying that changes to scoring views work correctly in both ERB and SPA modes.
First open-source AI sanitizer with local semantic detection. 7 layers + code block awareness + LLM intent analysis. Catches prompt injection, reverse shells, memory tampering, encoding evasion, trust abuse. 85% fewer false positives in v2.1. Zero cloud — your prompts stay on your machine.
百度地图 JSAPI WebGL (BMapGL)完整开发指南，覆盖地图初始化、覆盖物、图层、事件、样式、性能优化的任务，一站式开发高性能 3D 地图应用。当用户提及 BMapGL、百度地图、jsapi-gl或相关地图开发需求时自动触发。
Address PR review comments systematically. Use when responding to code review feedback on a pull request.
Generates a CSS stylesheet for a lobster.js page, targeting lbs-* class names. Use this whenever the user wants to style a lobster.js page, create a CSS theme for lobster.js, customize the visual appearance of a lobster.js site, or asks for CSS that targets lbs-* classes. Also trigger when a user describes a visual style (e.g. "dark mode", "minimal", "playful") while working on a lobster.js project — even if they don't mention CSS or lbs-* explicitly. --- Generate a CSS stylesheet for a lobster.js page based on the user's design description. lobster.js outputs semantic HTML where every element has a predictable `lbs-*` class name. Write CSS targeting these classes to style the page. Use the design description from the user's message. If no description is given, generate a clean minimal light theme. --- ## HTML structure reference ```html <!-- Content wrapper --> <div id="content"> … </div> <!-- Page regions --> <header class="lbs-header"> … </header> <footer class="lbs-footer"> … </footer> <!-- Headings --> <h1 class="lbs-heading-1"> … </h1> <h2 class="lbs-heading-2"> … </h2> <!-- h3–h6 follow the same pattern --> <!-- Paragraph --> <p class="lbs-paragraph"> … </p> <!-- Inline --> <em class="lbs-emphasis"> … </em> <strong class="lbs-strong"> … </strong> <del class="lbs-strikethrough"> … </del> <code class="lbs-code-span"> … </code> <!-- Horizontal rule --> <hr class="lbs-hr" /> <!-- Code block --> <div class="lbs-code-block"> <div class="lbs-code-filename">filename.js</div> <!-- optional --> <pre data-language="js"><code class="language-js"> … </code></pre> </div> <!-- Blockquote --> <blockquote class="lbs-blockquote"> <p class="lbs-paragraph"> … </p> </blockquote> <!-- Lists --> <ul class="lbs-ul"> <li class="lbs-list-item"> … </li> </ul> <ol class="lbs-ol"> <li class="lbs-list-item"> <input type="checkbox" class="lbs-checkbox" /> … <!-- task list --> </li> </ol> <!-- Table (standard) --> <table class="lbs-table"> <thead><tr><th> … </th></tr></thead> <tbody><tr><
Install, deploy, or reconfigure a VibeBridge Main server. Use when setting up configs/main.toml, asking the user for required main deployment settings, creating a dedicated Python virtualenv, deciding whether to rebuild the frontend, choosing nohup/systemd/launchd/manual process management, and validating the Main health endpoint plus browser entrypoint. 适用于安装或部署 VibeBridge Main 服务，并在改配置前向用户确认必要参数。
Git decorator that gives every commit memory — links AI sessions, tokens, and code attribution to your commits. Use when the user asks about commit history with AI context, session history, code attribution, token usage, or generating a developer card.
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
├─ ⭐ 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
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.
Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.
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.
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.
Use these three together:
Note: file size for all methods should be within 10MB.
Typical paths (may vary by local setup):
One SKILL.md can usually be reused 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.
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
Most common reasons:
We try to avoid that. Use ranking + comments to surface better skills:
