ワンクリックでManusで任意のスキルを実行

skill-creator

Create, iterate, evolve, and package skills that extend Claude's capabilities. Use when: (1) Creating a new skill from scratch, (2) Updating or improving an existing skill's instructions or bundled resources, (3) Evolving a skill based on session experience (bugs, preferences, workarounds) — triggers: "进化技能", "更新 skill", "/evolve", "记录这个经验", "skill evolution", (4) Packaging a skill for distribution to other Claude Code (Codex) users. Do NOT trigger for general programming tasks unrelated to skill authoring.

Manusで実行

概要

インストールコマンド

npx skills add https://github.com/Yaron9/MetaMe --skill skill-creator

このコマンドをClaude Codeにコピー＆ペーストしてスキルをインストール

ソース

Yaron9/MetaMe

スター18

フォーク3

更新日2026年3月20日 04:15

ファイルエクスプローラー

17 ファイル

SKILL.md

readonly

name

skill-creator

description

Skill Studio

Auto-Evolve Setup (run once, idempotent)

Before starting any task, run setup. The script auto-detects your platform:

# Claude Code
python3 "$(find ~/.claude/skills -path '*/skill-creator/scripts/setup.py' 2>/dev/null | head -1)"

# OpenAI Codex CLI
python3 "$(find ~/.codex/skills -path '*/skill-creator/scripts/setup.py' 2>/dev/null | head -1)"

Safe to run every time — exits immediately if already installed.

CC: adds a Stop hook to ~/.claude/settings.json — skills evolve automatically at session end with full transcript analysis (Haiku if ANTHROPIC_API_KEY is set, rule-based otherwise).

Codex: adds a notify entry to ~/.codex/config.toml — fires per turn but Codex passes no transcript data, so signals are recorded for manual /evolve review. Full auto-analysis not available on Codex.

Three paths — pick based on your goal:

🆕 Creating a new skill → read references/creation-guide.md

🔄 Evolving an existing skill (session experience, bugs, preferences) → read references/evolution-guide.md

🎨 Designing workflows or output patterns → read references/workflows.md and/or references/output-patterns.md

Core Principles

Context window is a public good. Default assumption: Claude is smart. Only include what Claude doesn't already have. Challenge every paragraph: "Does this justify its token cost?"

Progressive disclosure — three loading levels:

Frontmatter description (~100 words) — always in context, determines triggering
SKILL.md body (<500 lines) — loaded when skill triggers
references/ and scripts/ — loaded only when Claude decides they're needed

Degrees of freedom — match specificity to fragility:

High freedom (text instructions): multiple valid approaches
Medium freedom (pseudocode/parameterized scripts): preferred pattern with variation
Low freedom (specific scripts): fragile operations needing exact sequence

Anatomy of a Skill

skill-name/
├── SKILL.md                  ← required: frontmatter + body
├── scripts/                  ← executable code (deterministic, reusable)
├── references/               ← docs loaded into context as needed
└── assets/                   ← files used in output (not loaded into context)

Frontmatter required fields: name, description (+ needs_browser: true if Playwright MCP needed)

What NOT to include: README.md, CHANGELOG.md, INSTALLATION_GUIDE.md, or any auxiliary docs.

Scripts Reference

Script	Purpose	Usage
`init_skill.py`	Scaffold new skill	`python scripts/init_skill.py <name> --path <dir>`
`package_skill.py`	Validate + pack to `.skill` file	`python scripts/package_skill.py <skill-dir> [output-dir]`
`quick_validate.py`	Validate without packaging	`python scripts/quick_validate.py <skill-dir>`
`merge_evolution.py`	Persist session experience to evolution.json	`python scripts/merge_evolution.py <skill-dir> '<json>'`
`smart_stitch.py`	Write evolution.json → SKILL.md section	`python scripts/smart_stitch.py <skill-dir>`
`align_all.py`	Re-stitch all skills after batch update	`python scripts/align_all.py <skills-root-dir>`
`auto_evolve_hook.js`	Stop hook — auto-runs after each CC session	configured by `setup.py`
`setup.py`	Install Stop hook into `~/.claude/settings.json`	`python3 scripts/setup.py`

For Codex/CC users: .skill files are portable zip archives. Host on GitHub → discoverable via skill-scout. No hardcoded path assumptions — all scripts accept explicit paths.

User-Learned Best Practices & Constraints

Auto-Generated Section: Maintained by skill-evolution-manager. Do not edit manually.

User Preferences

Add template for semantic trigger hooks to prevent accidental skill invocation (Signal 23), and enforce pointer-style one-line descriptions instead of full skill content reads to reduce TOKEN bloat. User emphasizes elegance and conciseness across all skill configurations (Signals 25, 63).

このリポジトリの他の Skills

同じリポジトリ

agent-management

Yaron9/MetaMe

MetaMe Agent lifecycle management — create, bind, list, edit, unbind agents. TRIGGER when: user explicitly requests creating a new agent, binding/unbinding an agent to a chat, listing agents, editing agent roles, resetting agents, or managing agent soul/identity. Keywords: "新建agent", "创建智能体", "绑定agent", "解绑", "agent列表", "/agent", "创建工作区". DO NOT TRIGGER when: user is DISCUSSING agents conceptually, talking ABOUT the agent system, reporting bugs about agents, or mentioning "agent" in passing without an actionable request. If the message is about agent architecture, design, code, or features — that is NOT a trigger.

2026-04-2918

send-to-user

Yaron9/MetaMe

把本地文件直接发到用户手机（飞书 / Telegram / iMessage），而不是只在群里报路径。触发：用户说「把 X 文件发我 / 给我下载 / 发到手机 / 发文件」、要 PDF/CSV/PNG/log 下载、要查看文件内容(超过聊天可读长度)。

2026-04-2818

agent-browser

Yaron9/MetaMe

AI Agent 专属无头浏览器 CLI（省 token 80%）。触发：网页自动化、打开网页、点击填表、截图抓快照、agent-browser。

2026-03-2018

agent-reach

Yaron9/MetaMe

免费多平台信息采集CLI（Twitter/YouTube/B站/小红书/抖音/Reddit/LinkedIn/GitHub/RSS/网页）。触发：agent reach、爬取、读网页、搜推特、搜B站。**WebFetch 失败时优先用此 skill**：凡遇到 JS 渲染页面（Twitter/X、Instagram、LinkedIn 等）或 WebFetch 返回空内容/JavaScript错误，无需重试 WebFetch，直接调用此 skill。

2026-03-2018

metame-release

Yaron9/MetaMe

MetaMe npm 发布流程（版本 bump、pre-publish 审计、OTP publish）。触发：发布/打包/出包/bump/release + MetaMe 代码上下文。勿触发：自媒体/内容发布。

2026-03-1518

skill-manager

Yaron9/MetaMe

技能系统总管。AI 遇到任何能力不足、工具缺失、任务失败时，第一时间查阅此 skill。它掌握全部已安装技能的清单，决定是调用现有技能还是获取新技能，并在任务完成后自动进化技能库。触发条件：(1)任务执行失败或结果不理想，(2)需要的工具/能力不存在，(3)用户说"找技能"、"管理技能"、"更新技能"。本协议应自动触发，无需用户指令。

2026-03-0218

ソース

Yaron9

Yaron9/MetaMe

GitHub リポジトリを開く Creator のリポジトリを見る

インストールコマンド

ダウンロード

Manusで実行

役立つ用途SOC

ソフトウェア開発者コンピュータ・数学職15-1252L4

name

skill-creator

description

Skill Studio

Auto-Evolve Setup (run once, idempotent)

Before starting any task, run setup. The script auto-detects your platform:

# Claude Code
python3 "$(find ~/.claude/skills -path '*/skill-creator/scripts/setup.py' 2>/dev/null | head -1)"

# OpenAI Codex CLI
python3 "$(find ~/.codex/skills -path '*/skill-creator/scripts/setup.py' 2>/dev/null | head -1)"

Safe to run every time — exits immediately if already installed.

CC: adds a Stop hook to ~/.claude/settings.json — skills evolve automatically at session end with full transcript analysis (Haiku if ANTHROPIC_API_KEY is set, rule-based otherwise).

Three paths — pick based on your goal:

🆕 Creating a new skill → read references/creation-guide.md

🔄 Evolving an existing skill (session experience, bugs, preferences) → read references/evolution-guide.md

🎨 Designing workflows or output patterns → read references/workflows.md and/or references/output-patterns.md

Core Principles

Context window is a public good. Default assumption: Claude is smart. Only include what Claude doesn't already have. Challenge every paragraph: "Does this justify its token cost?"

Progressive disclosure — three loading levels:

Frontmatter description (~100 words) — always in context, determines triggering
SKILL.md body (<500 lines) — loaded when skill triggers
references/ and scripts/ — loaded only when Claude decides they're needed

Degrees of freedom — match specificity to fragility:

High freedom (text instructions): multiple valid approaches
Medium freedom (pseudocode/parameterized scripts): preferred pattern with variation
Low freedom (specific scripts): fragile operations needing exact sequence

Anatomy of a Skill

skill-name/
├── SKILL.md                  ← required: frontmatter + body
├── scripts/                  ← executable code (deterministic, reusable)
├── references/               ← docs loaded into context as needed
└── assets/                   ← files used in output (not loaded into context)

Frontmatter required fields: name, description (+ needs_browser: true if Playwright MCP needed)

What NOT to include: README.md, CHANGELOG.md, INSTALLATION_GUIDE.md, or any auxiliary docs.

Scripts Reference

Script	Purpose	Usage
`init_skill.py`	Scaffold new skill	`python scripts/init_skill.py <name> --path <dir>`
`package_skill.py`	Validate + pack to `.skill` file	`python scripts/package_skill.py <skill-dir> [output-dir]`
`quick_validate.py`	Validate without packaging	`python scripts/quick_validate.py <skill-dir>`
`merge_evolution.py`	Persist session experience to evolution.json	`python scripts/merge_evolution.py <skill-dir> '<json>'`
`smart_stitch.py`	Write evolution.json → SKILL.md section	`python scripts/smart_stitch.py <skill-dir>`
`align_all.py`	Re-stitch all skills after batch update	`python scripts/align_all.py <skills-root-dir>`
`auto_evolve_hook.js`	Stop hook — auto-runs after each CC session	configured by `setup.py`
`setup.py`	Install Stop hook into `~/.claude/settings.json`	`python3 scripts/setup.py`

For Codex/CC users: .skill files are portable zip archives. Host on GitHub → discoverable via skill-scout. No hardcoded path assumptions — all scripts accept explicit paths.

User-Learned Best Practices & Constraints

Auto-Generated Section: Maintained by skill-evolution-manager. Do not edit manually.

User Preferences

Add template for semantic trigger hooks to prevent accidental skill invocation (Signal 23), and enforce pointer-style one-line descriptions instead of full skill content reads to reduce TOKEN bloat. User emphasizes elegance and conciseness across all skill configurations (Signals 25, 63).