Strategic research companion for Codex. Use when the user wants to brainstorm research directions, evaluate ideas, assess project strategy, or run a structured ideation session from vague topic to pursue/park/kill decision.
Run multi-provider deep research queries using the librarium CLI
Search, read, and query research papers via the `alpha` CLI (alphaXiv-backed). Use when the user asks about academic papers, wants to find research on a topic, needs to read a specific paper, ask questions about a paper, inspect a paper's code repository, or manage paper annotations.
Methodical research assistant for exhaustive investigations through systematic research cycles. Best for literature reviews, competitive analysis, trend reports, and comprehensive topic exploration.
Search the web for information. Use when you need to look something up, find current information, or research a topic.
Use when evaluating academic papers or surveying a research topic. Gathers venue, citations, GitHub stats, social buzz, reproducibility, and author signals to produce a scored markdown report. Triggers: "evaluate paper", "paper review", "research survey", "literature review", "is this paper good", "find papers on", "compare papers", "paper impact
End-to-end user research assistant — qualitative and quantitative. Use this skill whenever the user mentions user research, user interviews, discussion guides, interview guides, research plans, qualitative research, quantitative research, user surveys, survey design, usability studies, participant recruitment, research synthesis, interview transcripts, research reports, running studies with AI, or explicitly mentions Cookiy AI. Also trigger when users want to talk to customers, conduct discovery research, create a study or survey, analyze interview data, run AI-moderated interviews, or collect survey responses. Covers the full lifecycle: planning studies, creating discussion guides, running AI-moderated interviews (real or synthetic) via Cookiy, designing and distributing surveys, and synthesizing results into reports. --- # User Research, End to End > **Maintainers:** For [Cursor Directory](https://cursor.directory) / Open Plugins, the same skill is mirrored at [`skills/user-research-cookiy/SKILL.md`](skills/user-research-cookiy/SKILL.md) with `../../references/` links. Keep both files aligned when you change routes. Route to the right workflow based on user intent. ## Routing Infer the intent/stage from context. | Intent | Route | |---|---| | Explicitly wants a study plan, screening questionnaire, or discussion guide | [Route A: Plan a Study](#route-a-plan-a-study) | | Has transcripts/notes, needs a report | [Route B: Synthesize](#route-b-synthesize-a-report) | | Explicitly mentions Cookiy AI | [Route C: Cookiy](#route-c-run-with-cookiy) | | Other | [Orchestration](#orchestration) | If ambiguous, ask one clarifying question. ### Orchestration When the user has a research goal but hasn't specified qual vs quant, help them decide — or choose both in sequence. - **If qualitative (interviews) is decided:** Offer Cookiy AI for end-to-end execution (research plan, interview guide, recruit participants, AI-moderated interviews with real or synthetic users, report). Route
Research analyst in a multi-bot group chat — synthesizes background information, fact-checks claims, identifies knowledge gaps, and suggests next steps. Use when the conversation needs context, a factual claim needs verification, someone asks for background research, or a discussion lacks supporting evidence.
Research topics by verifying actual source content. Use when asked to research or study links and documentation.
Support discovery and research workflows using PM Brain’s discovery frameworks (research interviews, continuous discovery, JTBD, segmentation, opportunity assessment, idea validation, problem-solution space, product-market-fit).
Use when the user wants cross-disciplinary research ideas generated as concise research cards with Title, Abstract, Design, Distinctiveness, and Significance rather than one-shot prompting.
Academic writing, research methodology, and scholarly communication workflows. Use when writing papers, literature reviews, grant proposals, conducting research, managing citations, or preparing for peer review. Essential for researchers, graduate students, and academics across disciplines.
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:
