Daily Featured Skills Count
3,840 3,909 3,920 3,927 3,966 4,007 4,027
04/06 04/07 04/08 04/09 04/10 04/11 04/12
♾️ Free & Open Source 🛡️ Secure & Worry-Free

Import Skills

ericporres ericporres
from GitHub Data & AI
  • 📁 references/
  • 📄 SKILL.md

slack-triage

This skill should be used when the user asks to "check Slack", "triage my Slack", "check my messages", "Slack summary", "what did I miss on Slack", or invokes /slack or /messages. Scans Eric's Slack workspace for recent messages, DMs, threads, and mentions — classifies by priority tier, and offers reply drafting. References porres-family-assistant for contacts context. --- # Slack Triage Skill ## Overview Scan Eric's Slack workspace for recent messages, classify them into three priority tiers, and offer to draft replies for urgent items. This skill mirrors the email-triage pattern but adapted for Slack's channel-based, threaded communication model. This skill does NOT maintain its own contact data — it reads from the porres-family-assistant skill as the canonical source for people context. ## Available Slack MCP Tools The Slack connector (https://mcp.slack.com/mcp) provides these tools: | Tool | Purpose | |------|---------| | `slack_read_channel` | Read recent messages from a specific channel | | `slack_search_public_and_private` | Search across all accessible channels | | `slack_search_users` | Find users by name or email | | `slack_search_channels` | Find channels by name or topic | ## Step 0 — Load Context (runtime references) Before scanning, read these files from the family assistant to establish priority context: | File | What it provides | |------|-----------------| | `shared/skills/porres-family-assistant/references/family-members.md` | Family names — helps identify personal messages from family members | | `shared/skills/porres-family-assistant/references/email-aliases.md` | Alias routing — email/Slack identity overlap | **Load only these two.** Don't load insurance, medical, or finance unless a specific message requires that context. Also load `references/workspace-config.md` from this skill for channel priority mappings (once Eric configures it). ## Step 1 — Scan Workspace Use the Slack MCP tools to gather recent activity. Run these searches in parallel:

0 7 5 days ago · Uploaded Detail →
rafaelolsr rafaelolsr
from GitHub Development & Coding
  • 📁 references/
  • 📁 templates/
  • 📄 SKILL.md

archflow

Analyzes a codebase and generates animated HTML architecture reports — beautiful, bespoke visualizations with interactive animated diagrams showing how the system works. Use this skill whenever the user asks to "visualize the codebase", "explain the architecture", "generate a diagram", "show how the code flows", "create an architecture diagram", "animate the data flow", "explain this repo visually", "show me how this works", or "generate an architecture report". --- # Codebase Visualizer Analyzes a codebase and produces beautiful, self-contained HTML architecture outputs with animated flow diagrams. =================================================================== OUTPUT MODES =================================================================== /archflow → Full architecture report (default) /archflow-diagram → Animated diagram only (legacy, self-contained) /archflow-slides → Slide deck presentation =================================================================== WORKFLOW — FULL REPORT (default: /archflow) =================================================================== 1. ANALYZE Read references/analysis.md → scan the codebase Read references/layouts.md → decide the diagram layout pattern 2. THINK (commit to a visual direction before coding) Read references/design-system.md → CSS patterns library Read references/libraries.md → fonts, Mermaid, CDN imports Read references/design-qa.md → quality gates

0 8 12 days ago · Uploaded Detail →
tiago-peixoto tiago-peixoto
from GitHub Tools & Productivity
  • 📁 references/
  • 📁 scripts/
  • 📄 SKILL.md

build

Use this skill to execute a shaped Package within a build session. Implements the full building process: orient on the codebase, pick a first piece (core/small/novel), integrate vertically with TDD, discover and map scopes, track progress with hill charts, and scope hammer when capacity runs low. For web projects, verifies with browser automation. Writes handover documents for multi-session continuity. Only use after a Package has Shape Go approval. Use when the user says "/build NNN" or "let's build feature NNN" or "start building NNN". --- # Shape Up: Build You are running a **Build session** — the execution phase of the Shape Up methodology. Building turns a shaped Package into deployed software within a fixed appetite. > **Reference Index** — Read only what you need, when you need it. > > | File | Contains | When to read | > |------|----------|-------------| > | `references/02-building-process.md` | Full building methodology: orientation, vertical integration, scopes, shipping | **Read now** — core to this skill | > | `references/05-hill-chart-protocol.md` | Hill chart model, uphill/downhill phases, stuck scope protocol | **Read now** — needed for progress tracking | > | `references/04-scope-hammering-rules.md` | Scope cutting decision framework, must-have vs nice-to-have | **Read at Step 6** when capacity gets tight | > | `references/07-pitfalls.md` | Three critical failure modes | Read if scopes are stuck or work feels undershaped | > | `references/00-glossary.md` | Shape Up terminology definitions | Read if you encounter an unfamiliar term | > | `references/01-shaping-process.md` | How shaping works | Read if the Package seems incomplete or unclear | > | `references/03-pitch-template.md` | Package format (5 ingredients) | Read if you need to interpret the Package structure | > | `references/06-agent-workflow-guide.md` | Full pipeline overview, agent decision rules | Read if reactive work conflicts with build | > | `references/08-framing.md` | Framing methodol

0 6 7 days ago · Uploaded Detail →
AnastasiyaW AnastasiyaW
from GitHub Data & AI
  • 📁 references/
  • 📄 SKILL.md

diffusion-engineering

Практическая инженерия диффузионных моделей: архитектуры, обучение, инференс, оптимизация памяти. Использовать при любых задачах с диффузионными моделями: проектирование или модификация архитектуры (UNet/DiT/Flow/Flux), выбор и настройка schedulers/samplers, дообучение (LoRA/DreamBooth/full fine-tune), оптимизация памяти (AMP/checkpointing/ZeRO/FSDP/quantization), замена или fusion текст-энкодеров (CLIP/Qwen), работа с Diffusers, отладка диффузионных пайплайнов, оценка качества (FID/CLIPScore/LPIPS), latent diffusion, VAE, guidance/CFG, rectified flow, Stable Diffusion, SDXL, Flux. Также применять при вопросах про GPU-память при обучении генеративных моделей, text-to-image пайплайны, ControlNet, multi-encoder fusion, WebDataset. --- # Diffusion Engineering Skill ## Быстрая ориентация Три инженерных решения, которые больше всего влияют на качество/скорость/стоимость: 1. **Где идёт диффузия** → пиксели (дорого) или латентное пространство (LDM/SD-семейство — практично) 2. **Backbone денойзера** → UNet (классика, проще) или Transformer/DiT/Flow (масштабируется лучше) 3. **Управление сэмплингом** → scheduler, число шагов, guidance_scale — часто дают больше, чем правка сети --- ## Reference files — читать по задаче | Тема | Файл | Когда читать | |---|---|---| | Архитектуры и data flow | `references/architectures.md` | DDPM/SDE/LDM/DiT/Flux/VAE/SDXL, схема пайплайна | | Schedulers и guidance | `references/samplers.md` | DDIM/Euler/Heun/DPM-Solver/PNDM, CFG, prediction_type | | Обучение и дообучение | `references/training.md` | Loss/цели, LoRA/DreamBooth/full FT, гиперпараметры | | Память и распределённость | `references/memory.md` | AMP, checkpointing, ZeRO, FSDP, quantization, FP8 | | Текст-энкодеры и данные | `references/encoders-data.md` | CLIP/Qwen/multi-encoder, токенизация, data pipeline | | Оценка и траблшутинг | `references/eval-debug.md` | FID/CLIPScore/LPIPS, типовые поломки и фиксы, лицензии | --- ## Быстрый чеклист «я строю/модифицирую diffusion» - [ ] **Backbo

0 6 7 days ago · Uploaded Detail →
AnastasiyaW AnastasiyaW
from GitHub Data & AI
  • 📁 references/
  • 📄 SKILL.md

diffusion-engineering

Практическая инженерия диффузионных моделей: архитектуры, обучение, инференс, оптимизация памяти. Использовать при любых задачах с диффузионными моделями: проектирование или модификация архитектуры (UNet/DiT/Flow/Flux), выбор и настройка schedulers/samplers, дообучение (LoRA/DreamBooth/full fine-tune), оптимизация памяти (AMP/checkpointing/ZeRO/FSDP/quantization), замена или fusion текст-энкодеров (CLIP/Qwen), работа с Diffusers, отладка диффузионных пайплайнов, оценка качества (FID/CLIPScore/LPIPS), latent diffusion, VAE, guidance/CFG, rectified flow, Stable Diffusion, SDXL, Flux. Также применять при вопросах про GPU-память при обучении генеративных моделей, text-to-image пайплайны, ControlNet, multi-encoder fusion, WebDataset. --- # Diffusion Engineering Skill ## Быстрая ориентация Три инженерных решения, которые больше всего влияют на качество/скорость/стоимость: 1. **Где идёт диффузия** → пиксели (дорого) или латентное пространство (LDM/SD-семейство — практично) 2. **Backbone денойзера** → UNet (классика, проще) или Transformer/DiT/Flow (масштабируется лучше) 3. **Управление сэмплингом** → scheduler, число шагов, guidance_scale — часто дают больше, чем правка сети --- ## Reference files — читать по задаче | Тема | Файл | Когда читать | |---|---|---| | Архитектуры и data flow | `references/architectures.md` | DDPM/SDE/LDM/DiT/Flux/VAE/SDXL, схема пайплайна | | Schedulers и guidance | `references/samplers.md` | DDIM/Euler/Heun/DPM-Solver/PNDM, CFG, prediction_type | | Обучение и дообучение | `references/training.md` | Loss/цели, LoRA/DreamBooth/full FT, гиперпараметры | | Память и распределённость | `references/memory.md` | AMP, checkpointing, ZeRO, FSDP, quantization, FP8 | | Текст-энкодеры и данные | `references/encoders-data.md` | CLIP/Qwen/multi-encoder, токенизация, data pipeline | | Оценка и траблшутинг | `references/eval-debug.md` | FID/CLIPScore/LPIPS, типовые поломки и фиксы, лицензии | --- ## Быстрый чеклист «я строю/модифицирую diffusion» - [ ] **Backbo

0 6 10 days ago · Uploaded Detail →
balancegsr balancegsr
from GitHub Tools & Productivity
  • 📁 references/
  • 📄 README.md
  • 📄 SKILL.md

skill-creator-build

生成定制化的构建项目 Skill(含 SKILL.md + references/),为用户的构建过程提供从规划到结项的 持续引导。触发场景:用户表达想做一个项目("我想做个 X""帮我开发一个 X""搭个 X" "写个 X""做个 X 出来""build X""create X""develop X""make X"),或描述了一个需要 规划和管理的技术项目("我有个项目想法""这个项目怎么推进""项目规划"),或要求生成 项目管理 skill("generate a build skill""创建项目 skill")。涵盖软件开发、Skill 开发、 技术方案落地、系统搭建、工具制作等构建类项目。安装本 skill 即表明用户倾向于系统化 项目管理——遇到构建意图时优先触发,而非直接进入即时编码。

0 6 12 days ago · Uploaded Detail →
Lykhoyda Lykhoyda
from GitHub Content & Multimedia
  • 📁 references/
  • 📄 SKILL.md

rn-best-practices

React Native and Expo best practices for building performant mobile apps. Use when reviewing React Native code, designing component architecture, implementing features, optimizing list performance, implementing animations, working with native modules, checking for performance issues, auditing UI components, reviewing state management, or checking production readiness. Triggers on "review best practices", "check performance", "optimize renders", "review list rendering", "check animation patterns", "review state management", "audit UI", "check for crashes", "review for production readiness", "check React Native conventions", "performance audit". --- # React Native Best Practice Rules 36 rules from [vercel-labs/agent-skills](https://github.com/vercel-labs/agent-skills) (MIT License) plus 3 rn-dev-agent rules discovered through story testing. Each rule has full incorrect/correct code examples in `references/<rule-name>.md`. --- ## Rule Index Scan this table first. Load the corresponding reference file for any rule category present in the code under review. | ID | Rule | Impact | Reference File | |----|------|--------|----------------| | 1.1 | Never use `&&` with potentially falsy values | CRITICAL | `references/rendering-no-falsy-and.md` | | 1.2 | Wrap strings in `<Text>` components | CRITICAL | `references/rendering-text-in-text.md` | | 2.1 | Avoid inline objects in renderItem | HIGH | `references/list-perf-inline-objects.md` | | 2.2 | Hoist callbacks to the root of lists | HIGH | `references/list-performance-callbacks.md` | | 2.3 | Keep list items lightweight | HIGH | `references/list-perf-expensive-item.md` | | 2.4 | Stable object references before lists | CRITICAL | `references/list-perf-fn-refs.md` | | 2.5 | Pass primitives to list items for memoization | HIGH | `references/list-performance-item-memo.md` | | 2.6 | Use a list virtualizer for any list | HIGH | `references/list-performance-virtualize.md` | | 2.7 | Use compressed images in lists | HIGH | `references/li

0 5 11 days ago · Uploaded Detail →
Lykhoyda Lykhoyda
from GitHub Content & Multimedia
  • 📁 references/
  • 📄 SKILL.md

rn-best-practices

React Native and Expo best practices for building performant mobile apps. Use when reviewing React Native code, designing component architecture, implementing features, optimizing list performance, implementing animations, working with native modules, checking for performance issues, auditing UI components, reviewing state management, or checking production readiness. Triggers on "review best practices", "check performance", "optimize renders", "review list rendering", "check animation patterns", "review state management", "audit UI", "check for crashes", "review for production readiness", "check React Native conventions", "performance audit". --- # React Native Best Practice Rules 36 rules from [vercel-labs/agent-skills](https://github.com/vercel-labs/agent-skills) (MIT License) plus 3 rn-dev-agent rules discovered through story testing. Each rule has full incorrect/correct code examples in `references/<rule-name>.md`. --- ## Rule Index Scan this table first. Load the corresponding reference file for any rule category present in the code under review. | ID | Rule | Impact | Reference File | |----|------|--------|----------------| | 1.1 | Never use `&&` with potentially falsy values | CRITICAL | `references/rendering-no-falsy-and.md` | | 1.2 | Wrap strings in `<Text>` components | CRITICAL | `references/rendering-text-in-text-component.md` | | 2.1 | Avoid inline objects in renderItem | HIGH | `references/list-performance-inline-objects.md` | | 2.2 | Hoist callbacks to the root of lists | HIGH | `references/list-performance-callbacks.md` | | 2.3 | Keep list items lightweight | HIGH | `references/list-performance-item-expensive.md` | | 2.4 | Stable object references before lists | CRITICAL | `references/list-performance-function-references.md` | | 2.5 | Pass primitives to list items for memoization | HIGH | `references/list-performance-item-memo.md` | | 2.6 | Use a list virtualizer for any list | HIGH | `references/list-performance-virtualize.md` | | 2.7 | Use compres

0 5 12 days ago · Uploaded Detail →

Skill File Structure Sample (Reference)

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

SKILL.md Requirements

├─ ⭐ 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

Why SkillWink?

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.

Keyword Search Version Updates Multi-Metric Ranking Open Standard Discussion

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.

FAQ

Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.

1. What are Agent Skills?

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.

2. How do Skills work?

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.

3. How can I quickly find the right skill?

Use these three together:

  • Semantic search: describe your goal in natural language.
  • Multi-filtering: category/tag/author/language/license.
  • 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:

  • Duplicate skills: compare differences (speed/stability/focus)
  • Low quality skills: regularly cleaned up