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

Composite Most Downloads Most Likes Most Comments Newest
dunialabs dunialabs
from GitHub Development & Coding
  • 📁 agents/
  • 📁 references/
  • 📄 SKILL.md
release peta-core workspace

peta-core-release

Publish peta-core releases from origin/main by preparing a detached temporary release workspace, generating English GitHub release notes, pushing Docker images, tagging the release, and publishing the GitHub release. Use when Codex is asked to release peta-core, bump the next patch version, publish a specific peta-core version, resume a prepared peta-core release, or clean up an abandoned prepared release workspace.

⬇0 ❤39 12 days ago · Uploaded Detail →
Bryptobricks Bryptobricks
from GitHub Tools & Productivity
  • 📁 assets/
  • 📁 benchmarks/
  • 📁 bin/
  • 📄 .gitignore
  • 📄 .npmignore
  • 📄 CHANGELOG.md
memory workspace node

structured-memory-engine

Structured memory system for AI workspaces. Indexes markdown memory files into SQLite FTS5 for fast, cited search. Extracts structured facts, maintains memory health, and provides an MCP server with live search + write-path for Claude Code integration. --- # Structured Memory Engine ## MCP Tools (v4) When running as an MCP server (`node lib/mcp-server.js`), exposes: - `sme_query` — Search memory. Supports `query`, `limit`, `since`, `type`, `minConfidence`, `includeStale`. - `sme_context` — Get relevant context for a message. Returns ranked, token-budgeted, formatted context for injection. Supports `message`, `maxTokens`. - `sme_remember` — Save a fact/decision/preference to today's memory log. Auto-indexed. - `sme_index` — Re-index workspace. Use `force: true` for full rebuild. - `sme_reflect` — Run maintenance: decay, reinforce, stale detection, contradictions, prune. Use `dryRun: true` to preview. - `sme_status` — Index statistics. ## CLI Commands ```bash # Index workspace memory files node lib/index.js index [--workspace PATH] [--force] [--include extra.md,other.md] # Search indexed memory node lib/index.js query "search terms" [--limit N] [--since 7d|2w|3m|2026-01-01] [--context N] [--type fact|confirmed|inferred|...] [--min-confidence 0.5] [--include-stale] # Show index status node lib/index.js status [--workspace PATH] # Memory maintenance node lib/index.js reflect [--workspace PATH] [--dry-run] node lib/index.js contradictions [--workspace PATH] [--unresolved] node lib/index.js archived [--workspace PATH] [--limit N] node lib/index.js restore <chunk-id> [--workspace PATH] ``` ## Configuration

⬇0 ❤11 9 days ago · Uploaded Detail →
arach arach
from GitHub Tools & Productivity
  • 📁 references/
  • 📁 scripts/
  • 📄 SKILL.md
automation workspace lattices

lattices-workspace

Control a macOS developer workspace via the Lattices daemon API. Use when managing windows, tiling layouts, launching terminal sessions, searching screen text, switching workspace layers, or automating desktop workflows. Activates on "lattices", "tile windows", "workspace layout", "screen text", "session layers", or any desktop automation task on macOS.

⬇0 ❤10 9 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