3,758 Open Skills

Free to get · One-click to use

✅ Keyword search & category filters
✅ Discussions & community interaction
✅ Version updates & multi-metric ranking
✅ Open SKILL.md standard

Import Skills

Composite Most Downloads Most Likes Most Comments Newest
paceaitian paceaitian
from GitHub Tools & Productivity
档案 写 编辑

artifact-management

Artifact 文件（spec/task/implementation_plan/walkthrough/findings）的格式规范、 管理规则和变更 ID（CHG-ID）管理。当创建或编辑任何 Artifact 文件时自动激活—— 包括 spec.md、task.md、implementation_plan.md、walkthrough.md、findings.md。 任何涉及任务编号 T-NNN、变更 ID CHG-YYYYMMDD-NN、状态标记 [ ]/[/]/[x]/[-]/[!]、 归档操作 ARCHIVE 的操作都应参考此 skill。即使只是修改一个任务状态或添加一条索引， 也请先查阅。 --- # Artifact 文件管理规则 管理 5 个核心 Artifact 文件的创建、更新和变更追踪。 > **存储位置**：Obsidian Vault（`VAULT_PATH/projects/<projectName>/`）。`getArtifactDir(cwd)` 为唯一路径解析器，hook 自动将 CWD 路径重定向到 vault。`.pace/` 运行时状态保留在项目 CWD。 --- ## 核心文件与操作规则 | 文件 | 用途 | 更新方式 | 限制 | |------|------|----------|------| | `spec.md` | 项目元数据与技术栈 | `Edit` 直接修改 | 无 ARCHIVE 标记 | | `task.md` | 任务分解与进度 | `Edit` 活跃区改状态 | **禁止 Write 覆盖** | | `implementation_plan.md` | 变更方案 | `Edit` 活跃区更新 | **禁止 Write 覆盖** | | `walkthrough.md` | 工作总结 | `Edit` 活跃区更新 | **禁止 Write 覆盖** | | `findings.md` | 调研记录 | `Edit` 活跃区更新 | **禁止 Write 覆盖** | - 文件**不存在**时：用 `Write` 创建（hooks 自动注入模板） - 文件**已存在**时：用 `Edit` 修改（hook 会 DENY Write 覆盖） - 例外：文件损坏经用户确认后允许 Write 重建 > Artifact 文件约束的权威定义在 **User Rule G-7**。 --- ## 双区结构 除 `spec.md` 外，其他 4 个文件用 `<!-- ARCHIVE -->` 分为活跃区和归档区： ``` ┌─ 活跃区（ARCHIVE 上方）─┐ ← 当前状态、未完成项 ├─ <!-- ARCHIVE --> ──────┤ ← 分隔标记（仅保留 1 个） ├─ 归档区（ARCHIVE 下方）─┤ ← 已完成的历史记录 └─────────────────────────┘ ``` **排列顺序**（统一倒序：新→旧）：**所有索引和归档区**一律新增条目插入顶部。这是强制规范，不是建议。违反排列顺序会导致 SessionStart 截断时丢失最新条目。 **归档 = 移动标记**：内容不动，`<!-- ARCHIVE -->` 标记上移。分两步 Edit： 1. 在待归档内容**上方**插入新 `<!-- ARCHIVE -->` 2. 删除旧 `<!-- ARCHIVE -->` 每步只涉及标记行 + 几行上下文，内容零接触。中间态（双标记）安全：`readActive()` 取第一个标记上方，内容不丢失。 适用条件：待归档内容须在活跃区底部（紧邻 ARCHIVE 上方）。不满足时（如 findings 中间项已解决），留在活跃区等底部项一起归档。 **task.md 归档时机**：`[x]`/`[-]` 任务应及时归档。PostToolUse hook 会检测并提醒。 --- ## 状态标记 ### 任务状态 | 标记 | 含义 | 转换 | |------|------|------| | `[ ]` | 未开始 | → `[/]` 或 `[-]` | | `[/]` | 进行中 | → `[x]`、`[!]`、`[-]` | | `[x]` | 完成 | 终态 | | `[!]` | 阻塞 | ↔ `[/]`（须说明原因） | | `[-]` | 跳过 | 终态（须说明原因） | `[P]` 标记表示可并行执行：`- [ ] T-001 [P] 任务描述` ### 变更状态 | 标记 | 含义 | 触发 | |------|------|------| | `[ ]` 规划中 | 方案已创建 | A 阶段完成 | | `[/]` 进行中

⬇0 ❤18 13 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