- 📁 .github/
- 📁 action/
- 📁 assets/
- 📄 .gitignore
- 📄 .goreleaser.yml
- 📄 COMPARISON.md
stacklit-navigator
Use stacklit.json to navigate codebases without burning tokens on file exploration
Use stacklit.json to navigate codebases without burning tokens on file exploration
Algorithm analysis with parallel multi-model reasoning — qwen_algo, qwen_reason, and minimax_code tackle your problem from different angles
Scripts, webhooks, cron, glue code
Write, refine, and adapt blog posts. Tech-first but supports any topic. Trigger when user asks to "write a blog", "draft an article", "refine this post", "写博客", "写一篇文章", "帮我写篇博客", "润色这篇文章", "写一篇内部邮件博客", "帮我改改这篇博客", "write a technical post", "blog post about", "newsletter article", or mentions writing for a personal blog, internal email, WeChat official account (公众号), or content channel. Auto-infers language, audience, and style from context. Asks only what it cannot infer. Outputs Markdown by default. Respects AGENTS.md conventions when present in the target directory.
Comprehensive guide for using Codex CLI (OpenAI) and Claude Code CLI (Anthropic) - AI-powered coding agents. Use when orchestrating CLI commands, automating tasks, configuring agents, or troubleshooting issues.
Inference-time system-prompt rules for Korean multi-turn RAG agents. Hard imperatives + Korean few-shots + decision tables for ambiguous phrasings — followup handling, persistent-filter durability, particle stripping, verifier cross-turn context, hedge-phrase suppression, LLM-over-regex routing. Distilled from Korean pharma production traces; content is domain-neutral and applies to any Korean multi-turn RAG (customer support, legal, finance, public sector, medical, e-commerce). Triggers on Korean followups like "X만", "그럼 X는", "더 보여줘", "2번째 문서", "전체 다시", or symptoms like "followup broadens instead of filtering" / "sticky filter silently dropped mid-conversation" / "verifier flags correct multi-turn answer" / "retrieval looks fine but answer says 정보 없음". The older builder-facing field-guide body is preserved at `SKILL-v1-legacy.md` for reference.
Blast radius analysis - search for ALL usages before modifying any existing code. Prevents breaking unrelated consumers by scoping impact before scoping fix.
Persistent memory and context for AI agents using Cognis by Lyzr. Use this skill when the user mentions "remember this", "what did I work on", "save this for later", "team knowledge", "project context", "recall", "memory", or needs long-term memory across sessions. Also use when the user asks about past decisions, preferences, or prior conversations. Supports personal memory (per-user), team memory (shared across repo contributors), semantic search, and automatic context assembly.
Encrypted organizational memory workflow for Rune with activation checks and /rune (or $rune for Codex CLI) command behaviors across MCP-compatible agents.
This skill should be used when the user says "hello", "hi", or "greet me".
>-
Use before any feature work — explores intent, requirements, and design. Produces HOTL contracts (intent, verification, governance) before implementation.
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: