Daily Featured Skills Count
5,034 5,070 5,117 5,165 5,205 5,241 5,259
05/08 05/09 05/10 05/11 05/12 05/13 05/14
♾️ Free & Open Source 🛡️ Secure & Worry-Free

Import Skills

Composite Most Downloads Most Likes Most Comments Newest
awaik awaik
from GitHub Tools & Productivity
  • 📁 config/
  • 📁 references/
  • 📁 scripts/
  • 📄 skill.md
tool automation workflow

demand-research

Исследование спроса и семантики: анализ упущенного спроса, сезонный прогноз бюджета, каннибализация ключевых, верификация интента. Используй при запросах 'исследование спроса', 'найти ключевые', 'упущенный спрос', 'каннибализация', 'сезонность', 'минус-слова из запросов'.

⬇0 ❤7 18 days ago · Uploaded Detail →
Viniciuscarvalho Viniciuscarvalho
from GitHub Tools & Productivity
  • 📁 .claude/
  • 📁 .github/
  • 📁 assets/
  • 📄 .DS_Store
  • 📄 .env.example
  • 📄 .gitignore
feature workflow automation

feature-marker

End-to-end feature development orchestrator that automates the full lifecycle from requirements to pull request. Generates PRD, Tech Spec, and Task breakdown artifacts, then executes a 4-phase workflow: Analysis → Implementation → Tests → Commit & PR. Supports 5 execution modes: Full Workflow (generate all artifacts + run all phases), Tasks Only (skip generation, use existing files), Ralph Loop (autonomous self-correcting execution), Spec-Driven (multi-agent review with worktree isolation), and Test Only (run tests phase exclusively). Includes checkpoint/resume so work can be paused and resumed at any phase, and auto-detects GitHub, Azure DevOps, or GitLab for PR creation. Platform-agnostic with auto stack detection for iOS/Swift, Node.js/TypeScript, Rust, Python, and Go. ALWAYS use this skill when the user says "implement this feature", "build feature X", "start a new feature", "create a PRD", "generate tech spec", "break down tasks", "feature workflow", "plan this feature", "implement from spec", "run the full workflow", "resume feature", "continue where I left off", asks to go from requirements to implementation, wants to automate feature development end-to-end, mentions PRD-to-PR pipelines, or says "/feature-marker" — even if they just say "I need to build X" without explicitly mentioning a workflow. Also trigger when the user mentions "Ralph Loop", "spec-driven mode", "checkpoint", or asks to generate tasks from a PRD or tech spec.

⬇0 ❤7 26 days ago · Uploaded Detail →
oomol-lab oomol-lab
from GitHub Tools & Productivity
  • 📄 SKILL.md
automation ai workflow

oo-create-skill

Author, generate, scaffold, or update a local AI agent skill that turns an OOMOL/oo package, connector action, block, or selected workflow into reusable instructions. Use when the user asks to create a skill, write a skill, make a Codex/Claude/agent skill, or refine an existing local skill for an oo-powered workflow, even if capability discovery is needed first.

⬇0 ❤6 16 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