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

goto-lab goto-lab
from GitHub Data & AI
  • 📁 assets/
  • 📁 references/
  • 📁 scripts/
  • 📄 SKILL.md

pufu-editor

プ譜(プロジェクト譜)のJSONデータを既存のドキュメントから自動生成するスキル。 使用するタイミング: (1) PowerPoint、Excel、PDF、テキストファイルからプ譜を生成したい (2) 複数のドキュメントを解析してプ譜の要素を抽出したい (3) プロジェクト関連資料からプ譜を自動作成したい (4) プ譜エディタ(pufu-editor)で使えるJSON形式でエクスポートしたい (5) 時系列で複数ステップがあるプロジェクトの複数局面プ譜を生成したい (6) 偶数局面を振り返り局面として、計画と振り返りのペアでプ譜を生成したい # プ譜ジェネレーター (Pufu Generator) 既存のドキュメント(pptx, xlsx, pdf, docx, txt, md)からプ譜エディタ互換のJSONデータを自動生成する。 単一局面のプ譜だけでなく、時系列で複数局面のプ譜を生成可能。偶数局面は振り返り局面として自動構成される。 ## ワークフロー ``` 入力ファイル → 読み取り・分析 → プ譜JSON生成 → サマリ表示 → (任意)画像生成 ``` **処理フロー:** 1. **読み取り・分析**: 入力ファイルを直接読み取り、プ譜の各要素を抽出する - 対応形式: pptx, xlsx, pdf, docx, txt, md - 時系列のステップがある場合は局面を検出し、複数局面モードで処理 2. **プ譜JSON生成**: 抽出した要素からpufu-editor互換のJSONを生成し、ファイルに保存 - 単一局面: `ProjectScoreModel` 形式 - 複数局面: `ProjectScoreMap` 形式(局面ごとの個別JSONも出力) 3. **サマリ表示**: 生成結果の概要をユーザーに表示 4. **画像生成**(オプション): Playwrightスクリプトでプ譜をPNG画像に変換 > **注意**: ファイルの読み取り・要素抽出・統合はClaude自身が直接行う。 > Pythonスクリプトは最終成果物の生成(JSON整形・画像キャプチャ)にのみ使用する。 ### 作業ディレクトリ構成 各ステップの成果物をフォルダに格納する。処理開始時にディレクトリを作成すること。 ``` {work_dir}/ ├── 01_analysis/ # Step 1: 読み取り・分析の結果 │ └── analysis.json # 抽出した要素の分析結果 ├── 02_output/ # Step 2: プ譜JSON(最終成果物) │ ├── pufu.json # 単一局面の場合 │ ├── pufu_all_phases.json # 複数局面の場合(ProjectScoreMap) │ ├── pufu_phase1.json # 複数局面の場合(個別局面) │ ├── pufu_phase2.json │ └── ... └── 03_image/ # Step 4: 画像(オプション) ├── pufu.png # 単一局面の場合 ├── pufu_phase1.png # 複数局面の場合(局面ごと) ├── pufu_phase2.png └── ... ``` **01_analysis/analysis.json の形式(単一局面):** ```json { "source_files": ["project_plan.pdf"], "mode": "single", "gainingGoal": "抽出した獲得目標テキスト", "winCondition": "抽出した勝利条件テキスト", "purposes": [ { "text": "中間目的テキスト", "measures": [ {"text": "施策テキスト", "color": "red"} ] } ], "elements": { "people": "抽出したテキスト", "money": "抽出したテキスト", "time": "抽出したテキスト", "quality": "抽出したテキスト", "businessScheme": "抽出したテキスト", "environment": "抽出したテキスト", "rival": "抽出したテキスト", "foreignEnemy": "抽出したテキスト" } } ``` **01_analysis/analysis.json の形式(複数局面):** ```json { "source_files": ["p

0 7 11 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