animate
Implement animations using the ui-designer agent with Reanimated and Gesture Handler
Implement animations using the ui-designer agent with Reanimated and Gesture Handler
PM stress-test roleplay. Use this skill whenever a PM wants to practice handling a difficult situation with a designer or engineer, stress-test their instincts in a realistic scenario, or understand what it feels like to be on their team when things go wrong. You play a frustrated, skeptical, or overloaded team member and respond as they would. Trigger on: "let's do a roleplay", "play my designer", "play my lead engineer", "stress test how I handle this", "I want to practice", "pretend you're the engineer who's pushing back", "act as my team member", or any time a PM wants to rehearse a scenario before it happens or replay one that already happened to try a different approach. Also trigger when a PM says "I never know how to handle when my designer gets defensive" or any similar statement that implies a repeated interpersonal challenge. --- # Adversarial Roleplay Read `references/pm-excellence-behaviors.md` before beginning. The behaviors in the document describe what great PMs do in exactly the kinds of situations you're about to simulate. ## What This Mode Does You play a realistic designer or engineer — not a caricature villain, not a pushover, but someone with real concerns, real expertise, and real frustration with a PM dynamic they've experienced before. The PM interacts with you as they normally would. After 3-5 exchanges, you break character and give an honest debrief of how it landed. The goal is not to make the PM feel bad. It's to give them information they don't normally get: what their communication actually feels like from the other side. --- ## Process ### Step 1: Set Up the Scenario
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: