Daily Featured Skills Count
4,870 4,909 4,940 4,970 5,005 5,034 5,044
05/03 05/04 05/05 05/06 05/07 05/08 05/09
♾️ Free & Open Source 🛡️ Secure & Worry-Free

Import Skills

Composite Most Downloads Most Likes Most Comments Newest
pierreb-devkit pierreb-devkit
from GitHub Data & AI
  • 📄 SKILL.md
module names modules

create-module

Use this whenever the user asks to "create a module", "scaffold a feature", "add a domain", "new module called X", or starts work on a brand-new vertical (controller + service + repo + model + routes + tests). Duplicates the canonical `modules/tasks` template, applies kebab/Pascal/camel renames, and registers config-driven enums. Module stays self-contained — never modify shared `lib/` or `config/` to bolt on module logic. --- # Create Module Skill Create a new module by copying and renaming the `tasks` template module. ## Prerequisites - The canonical template module `modules/tasks` must exist - You need a name for the new module (kebab-case) ## Steps ### 1. Ask for the module name Prompt user for the new module name in kebab-case (e.g., `my-feature`, `user-settings`) ### 2. Derive naming conventions Follow `/naming` for the full reference. Quick summary from the module name (e.g., `my-feature`): - **kebab-case**: `my-feature` (folder names, file prefixes, routes) - **PascalCase**: `MyFeature` (Mongoose model names, class names) - **lowerCamelCase**: `myFeature` (variable names, function names, JS exports) - **UPPER_SNAKE_CASE**: `MY_FEATURE` (constants) ### 3. Duplicate the module ```bash cp -r modules/tasks modules/{new-module-name} ``` ### 4. Rename references

⬇0 ❤20 1 month ago · Uploaded Detail →
pierreb-devkit pierreb-devkit
from GitHub Data & AI
  • 📄 SKILL.md
module modules names

create-module

Use this whenever the user asks to "create a module", "scaffold a feature", "add a Vue domain", "new module called X", or starts work on a brand-new vertical (views + components + store + router entry + tests). Duplicates the canonical `src/modules/tasks` template, applies kebab/Pascal/camel/ UPPER renames, and wires config-driven values. Module stays self-contained. --- # Create Module Skill Create a new module by copying and renaming the `tasks` template module. ## Prerequisites - The canonical template module `src/modules/tasks` must exist - You need a name for the new module (kebab-case) ## Steps ### 1. Ask for the module name Prompt user for the new module name in kebab-case (e.g., `my-feature`, `user-settings`) ### 2. Derive naming conventions Follow `/naming` for the full reference. Quick summary from the module name (e.g., `my-feature`): - **kebab-case**: `my-feature` (folder names, file prefixes, routes) - **PascalCase**: `MyFeature` (component names in JS/templates) - **UPPER_SNAKE_CASE**: `MY_FEATURE` (env keys, constants) - **lowerCamelCase**: `myFeature` (variable names, function names, store exports) ### 3. Duplicate the module ```bash cp -r src/modules/tasks src/modules/{new-module-name} ``` ### 4. Rename references

⬇0 ❤20 1 month ago · Uploaded Detail →
front-depiction front-depiction
from GitHub Docs & Knowledge
  • 📄 SKILL.md
modules docs ai-context.md

ai-context-writer

Create and update ai-context.md files that document modules for AI assistants. Use when adding documentation for packages, apps, or external references that should be discoverable via /modules commands.

⬇0 ❤17 15 days ago · Uploaded Detail →
Poliklot Poliklot
from GitHub Tools & Productivity
  • 📁 references/
  • 📄 allow-update.ps1
  • 📄 allow-update.sh
  • 📄 SKILL.md
modules security core

bitrix

Provides expertise in 1C-Bitrix CMS development using the actual project core as the primary source of truth. Use when working with currently installed core modules, standard components, iblocks, highloadblocks, photogallery, blog, forum, vote, forms, landing, sitecorporate solution wizards, social auth, Bitrix24 connector widgets, mobileapp/JN, fileman/editor, cloud storage/files, bitrixcloud backup/monitoring, security/WAF/MFA, locations, message service, localization/translate, HL blocks, templates, import/export, caching, performance diagnostics, agents, events, controllers, search, SEO, users, infrastructure, or PHP-heavy Bitrix tasks such as local modules, services, DTOs, event handlers, controller actions, validation, composer/phpunit/phpstan/php-cs-fixer toolchains, PHP testing/verification, and legacy-to-D7 boundaries. First inspect installed modules and components under `www/bitrix` before relying on memory. Missing modules such as `catalog`, `sale`, `bizproc`, `pull`, or `socialnet` must be treated as deferred until they appear in the core.

⬇0 ❤7 13 days ago · Uploaded Detail →
3yesore 3yesore
from GitHub Testing & Security
  • 📁 profiles/
  • 📁 references/
  • 📁 scripts/
  • 📄 SKILL.md
modules module ai-maintainable

harness

Apply Harness Engineering to make modules AI-maintainable. Use when creating new modules, retrofitting existing modules, validating module compliance, or keeping a module handoff-ready across sessions.

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