Free to get · One-click to use
Research a topic deeply, plan a blog step by step, and write a long-form article with structured Markdown outputs in the current working directory. Supports multilingual writing, source tracking, metadata generation, and optional image insertion via available image tools.
[1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces]. --- # [Skill Name] [One sentence summary of the skill's purpose.] ## Workflow Overview 1. **Step 1** → Brief description 2. **Step 2** → Brief description 3. **Step 3** → Brief description ## Core Output Template [Define the primary output structure this skill produces] | Element | Definition | Evidence | |---------|------------|----------| | **Field 1** | What this captures | How to validate | | **Field 2** | What this captures | How to validate | See `assets/output-template.md` for copy-paste template. ## Step 1: [First Major Step] [Detailed instructions for this step] ### Checklist - [ ] Item 1 - [ ] Item 2 ## Step 2: [Second Major Step] [Detailed instructions for this step] ## Step 3: [Third Major Step] [Detailed instructions for this step] ## Quality Gates ### Pass Checklist - [ ] Gate 1: [Specific, measurable criterion] - [ ] Gate 2: [Specific, measurable criterion] - [ ] Gate 3: [Specific, measurable criterion] ### Testability Check - [ ] Can this output be validated? - [ ] Does it reference IDs from SoT/? ## Anti-Patterns | Pattern | Example | Fix | |---------|---------|-----| | Bad pattern 1 | "Example" | → "Better approach" | | Bad pattern 2 | "Example" | → "Better approach" | ## Bundled Resources - **`references/[file].md`** — [Description of when to use] - **`assets/[template].md`** — [Description of template purpose] ## Handoff [What happens after this skill completes? What stage/skill comes next?]
Generate complete, production-ready Agent Skill packages via a 7-step pipeline. Each step has defined inputs, outputs, and quality constraints.
登壇プレゼン資料を自動生成するスキル（LT〜30分講演まで対応）。 テーマからアウトライン作成、PowerPoint/ODPスライド生成、 トークスクリプト（台本）の記入、音声合成、音声埋め込み、 MP4動画エクスポートまで一括対応。 使用場面: (1) 登壇テーマからプレゼンを一括作成したい, (2) 既存アウトラインからスライドを作りたい, (3) スライドにトークスクリプトを追加したい, (4) スクリプトから音声を合成してスライドに埋め込みたい, (5) プレゼンを動画としてエクスポートしたい。 トリガー: LT, ライトニングトーク, プレゼン作成, スライド作成, 代打, 登壇, presentation, slides, talk script, 音声合成, 講演, 動画, MP4, video。 --- # 代打AI — 登壇プレゼン自動生成スキル ## 概要 テーマ入力から完成プレゼンまでの一連のパイプラインを実行する。 Step 6（スライドショー設定）までで **PPTX として完成** する。 さらに Step 7 で **MP4動画としてもエクスポート可能** だが、追加の外部ツール（LibreOffice, ffmpeg）が必要。 動画が不要なユーザーも多いため、**Step 6 完了後に動画も作るか確認し、不要なら Step 7 はスキップすること。** ## ヘルプ表示 ユーザーが「ヘルプ」「使い方」「流れを教えて」等と聞いた場合、以下のパイプライン図を表示する: ``` ╔══════════════════════════════════════════════════════════════╗ ║ 代打AI パイプライン ║ ╠══════════════════════════════════════════════════════════════╣ ║ ║ ║ Step 1 テーマ → アウトライン (Markdown) ║ ║ │ ║ ║ Step 1.5 アウトライン → スライド仕様 (JSON) ║ ║ │ ║ ║ Step 1.7 画像生成 (SVG / Gemini) ─── オプション ║ ║ │ ║ ║ Step 2 スライド仕様 → PPTX 生成 ║ ║ │ ↕ ユーザーがPPTXを確認・修正可能 ║ ║ Step 3 トークスクリプト更新 ────── オプション ║ ║ │ ║ ║ Step 4 読み辞書 → TTSスクリプト → 音声合成 ║ ║ │ ↕ ユーザーが読みを確認・修正可能 ║ ║ Step 5 音声ファイル → PPTX に埋め込み ║ ║ │ ║ ║ Step 6 スライドショー自動再生設定 ║ ║ │ ║ ║ ▼ ║ ║ 完成！ presentation_final.pptx ║ ║ │
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
├─ ⭐ 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
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.
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.
Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.
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.
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.
Use these three together:
Note: file size for all methods should be within 10MB.
Typical paths (may vary by local setup):
One SKILL.md can usually be reused 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.
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
Most common reasons:
We try to avoid that. Use ranking + comments to surface better skills:
