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 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.
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: