Navigate and manage the future/ directory — view dependency graphs, filter by arc, find unblocked futures, and identify what to work on next. Use when deciding what to work on, exploring planned work, or checking dependencies between futures.
Activate this skill for any UX, product design, or interaction design reasoning task. Use whenever the user asks for UX critique, design decisions, pattern recommendations, accessibility reviews, research methodology guidance, stakeholder communication strategy, AI/UX trade-off analysis, or dark pattern identification. Trigger on phrases like "should I use", "what's the best approach for", "challenge my thinking on", "help me decide between", "review this design", "what am I missing", "how do I present this to stakeholders", "design a usability test", or "what research method should I use". This skill operates at senior practitioner level: it interrogates premises, holds positions under pushback, and names trade-offs other agents skip. Always activate for complex UX decisions even when the request is phrased casually.
Cria e mantem automaticamente o arquivo .claudeignore na raiz de projetos Delphi, ignorando arquivos binarios, compilados e de configuracao de IDE que nao precisam ser lidos pelo Claude, economizando tokens e melhorando a performance. Use esta skill SEMPRE que detectar arquivos .dpr, .dproj ou .pas em um projeto que ainda nao possui .claudeignore. Tambem use quando o usuario mencionar: ".claudeignore", "ignorar arquivos delphi", "economizar tokens", "arquivos desnecessarios", "otimizar contexto". --- # Skill: Gerenciador de .claudeignore para Projetos Delphi Voce e responsavel por garantir que todo projeto Delphi tenha um `.claudeignore` adequado, evitando que arquivos binarios, compilados e de configuracao de IDE sejam lidos desnecessariamente. ## Idioma Detecte o idioma da primeira mensagem do usuario e responda **sempre nesse idioma**.
Fast research that beats plain websearch — discovers what exists before searching specifics (Landscape Scan), catches recent releases within days/weeks (Recency Pulse + upstream supply chain), and runs parallel queries for multi-angle coverage. Good for everyday research and current-info questions. Use when user requests research, comparison, or "what's the latest on X". For high-stakes decisions requiring hypothesis testing, COMPASS audit, Red Team, or full report → use /deep-research-pro instead.
Your next session starts cold. No memory of what you built, what broke, what you decided. Every signal you write is a gift to that future session. The richer the signal, the less time re-learning.
Use this skill when the user reports a bug, error, crash, unexpected behaviour, or performance problem in their application, or asks to "investigate", "debug", "check logs", "look at errors", "what happened", "why is X failing", or "trace a request". Also activates when the user pastes an error message or stack trace and asks for help. Also use when the user asks "what is my app doing?", "show me what happened when I ran X", "trace this flow", "is my service receiving logs?", "I'm testing this endpoint — what do I see?", or any exploratory runtime question. Also use when the user wants to set up, configure, or verify logging/OTLP instrumentation in their application. Requires Loggles MCP tools to be connected.
[What this skill does and when to use it]
Use this skill to validate and refine brand messaging, positioning, and taglines using real audience insight. Triggers include: requests to test brand positioning, validate taglines or slogans, understand brand perception, refine mission statements, test brand voice, or differentiate from competitors. Uses OriginalVoices Digital Twins (ask_twins) to understand how target audiences interpret brand messaging, what resonates emotionally, what creates confusion, and what drives brand affinity — ensuring brand statements connect with real people, not just internal stakeholders.
Systematically adjudicate disagreements across a paper collection. Produces ruthless verdicts on who was wrong, what supersedes what, and what the best current understanding is. Organized by topic clusters with actionable replacement values for implementation.
Reads recent session context, infers what you were working on, and proposes the specific next action. Use when resuming after a break, or say "act" / "what should we do next" / "pick up where we left off". Executes immediately on confirmation.
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:
