Brainstorm a code change while seeing risk, ownership, and tech-debt signals from tea-rags first, so creative exploration is grounded in the actual state of the affected area. Triggers on "brainstorm X", "design feature", "refactor Y", "let's discuss", "давай обсудим", "как перестроить", "что может сломаться". NOT for trivial edits or stylistic questions with no code area to enrich. Wraps superpowers:brainstorming with a tea-rags risk-signal enrichment step. --- # dinopowers: brainstorming Wrapper over `superpowers:brainstorming`. Ensures creative exploration starts from real git signals (hotspots, owners, legacy debt) of the target area — not from assumptions about how the code looks today. ## Iron Rule **tea-rags enrichment MUST be called BEFORE `Skill(superpowers:brainstorming)`** — whenever the target area is identifiable. Correct preset selection (`hotspots`, `ownership`, `techDebt`) + correct parameters + correct ordering is the core value of this wrapper. If no code area is identifiable from the user request (pure conceptual brainstorming): skip enrichment and invoke `superpowers:brainstorming` directly. State that explicitly — do not fabricate an area. **Chaining rule:** see [CHAINING.md](../../CHAINING.md) — every dinopowers:X
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: