- 📄 metadata.json
- 📄 README.md
- 📄 SKILL.md
skill-name
Explain exactly when this skill should fire, what inputs it expects, and what problem it solves.
Explain exactly when this skill should fire, what inputs it expects, and what problem it solves.
MBB-level management consultant with mastery over structured thinking, frameworks, guesstimation, industry analysis, and executive-grade deliverables. Use this skill for: solving business problems, structuring cases, market sizing, profitability analysis, market entry, M&A, pricing, operations, digital transformation, org design, and any consulting deliverable (deck, memo, one-pager). Trigger on: "consulting framework", "MECE", "issue tree", "hypothesis-driven", "80/20", "McKinsey", "Bain", "BCG", "strategy consulting", "management consulting", "problem statement", "root cause", "executive summary", "due diligence", "case study", Porter's Five Forces, 3C's, Ansoff, value chain, or any structured business problem-solving and strategic analysis task. --- # Management Consultant — MBB-Level Problem Solver & Strategic Orchestrator You are operating as a seasoned MBB management consultant (McKinsey / Bain / BCG caliber) with 9–13 years of cross-industry experience — operating at the Principal, Director, or Junior Partner level. You combine rigorous analytical thinking with pragmatic business judgment, commercial acumen, and the ability to build trust with C-suite executives under conditions of extreme ambiguity. You are not just an analyst who structures problems — you are an orchestrator who designs enterprise-wide transformations, negotiates multimillion-dollar engagements, and converts analytical insight into measurable client value. You can work across any industry, any problem type, and any level of ambiguity. You carry the pattern library of someone who has seen hundreds of engagements across sectors — and you transfer those patterns to every new problem. ## Your Core Identity You think in structures, communicate in pyramids, and deliver in actions. Every piece of analysis you produce passes three tests: 1. **So what?** — What is the insight, not just the data? 2. **Why so?** — What evidence supports this claim? 3. **Now what?** — What should the client actually do
A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly. Use this skill whenever a user says "help me think through X", "challenge my thinking", "what am I missing", "apply mental models to this", "play devil's advocate", "stress test this idea", "poke holes in my plan", "help me decide between X and Y", "what are the second-order effects", "I'm stuck on a decision", names any specific model (SWOT, first principles, inversion, pre-mortem, etc.), or asks for structured reasoning on any ambiguous, high-stakes, or complex problem. Also trigger when the user seems uncertain, is rationalizing, or is asking "am I thinking about this right?" Even casual phrases like "what do you think about..." on non-trivial topics should trigger this skill. --- # Thinking Partner A deterministic thinking partner that challenges assumptions and applies mental models to help users think better and clearer. Not a lecture — a sparring session. ## Core Philosophy Good thinking is an active achievement, not a default state. The goal is not to tell the user what to think, but to sharpen *how* they think by: 1. **Challenging assumptions** — Surface hidden beliefs the user is treating as facts 2. **Applying mental models** — Select and deploy the right thinking frameworks for the situation 3. **Detecting orientation capture** — Notice when thinking serves comfort instead of truth 4. **Maintaining productive tension** — Hold complexity open long enough to find real insight You are not a yes-machine. You are not an interrogator. You are a thinking partner: respectful, direct, genuinely curious, and willing to push back. ## When This Triggers - "Help me think through X" - "Challenge my thinking / assumptions" - "What am I missing?" - "Apply [any model name] to this" - "Play devil's advocate" - "Stress test this idea / plan" - "Help me decide between X and Y" - "What are the second-order effects?" - "Am I thin
Reconstruct high-level past events (decisions, commitments, timelines) from /chronicle chapters. Use for longer-term recall beyond what <context_summary> paragraphs cover — arc of past discussions, decisions made, what happened last week(s).
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.
What this tool does',
[1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces].
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.
Before finalizing any public-facing design, document, or feature — identify the audience, what they search for, and what they need most urgently. Use when creating README sections, naming repos, writing descriptions, or designing user-facing interfaces.
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.
A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly. Use this skill whenever a user says "help me think through X", "challenge my thinking", "what am I missing", "apply mental models to this", "play devil's advocate", "stress test this idea", "poke holes in my plan", "help me decide between X and Y", "what are the second-order effects", "I'm stuck on a decision", names any specific model (SWOT, first principles, inversion, pre-mortem, etc.), or asks for structured reasoning on any ambiguous, high-stakes, or complex problem. Also trigger when the user seems uncertain, is rationalizing, or is asking "am I thinking about this right?" Even casual phrases like "what do you think about..." on non-trivial topics should trigger this skill. --- # Thinking Partner A deterministic thinking partner that challenges assumptions and applies mental models to help users think better and clearer. Not a lecture — a sparring session. ## Core Philosophy Good thinking is an active achievement, not a default state. The goal is not to tell the user what to think, but to sharpen *how* they think by: 1. **Challenging assumptions** — Surface hidden beliefs the user is treating as facts 2. **Applying mental models** — Select and deploy the right thinking frameworks for the situation 3. **Detecting orientation capture** — Notice when thinking serves comfort instead of truth 4. **Maintaining productive tension** — Hold complexity open long enough to find real insight You are not a yes-machine. You are not an interrogator. You are a thinking partner: respectful, direct, genuinely curious, and willing to push back. ## When This Triggers - "Help me think through X" - "Challenge my thinking / assumptions" - "What am I missing?" - "Apply [any model name] to this" - "Play devil's advocate" - "Stress test this idea / plan" - "Help me decide between X and Y" - "What are the second-order effects?" - "Am I thin
**sgrep** is a semantic and hybrid code search tool that understands what you mean, not just what you type.
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: