- 📄 SKILL.md
marp-agent-mcp
Marp形式のスライドを作成・編集する。スライド作成、プレゼン作成、パワポ作成、発表資料、プレゼンテーション資料などを依頼されたときに使用する。「〜についてスライドを作って」「〜のプレゼン資料を作成して」「〜を説明するパワポが欲しい」などの依頼があれば必ずこのスキルを使用すること。
Marp形式のスライドを作成・編集する。スライド作成、プレゼン作成、パワポ作成、発表資料、プレゼンテーション資料などを依頼されたときに使用する。「〜についてスライドを作って」「〜のプレゼン資料を作成して」「〜を説明するパワポが欲しい」などの依頼があれば必ずこのスキルを使用すること。
**MANDATORY for ALL MCP server work** - mcp-use framework best practices and patterns. **READ THIS FIRST** before any MCP server work, including: - Creating new MCP servers - Modifying existing MCP servers (adding/updating tools, resources, prompts, widgets) - Debugging MCP server issues or errors - Reviewing MCP server code for quality, security, or performance - Answering questions about MCP development or mcp-use patterns - Making ANY changes to server.tool(), server.resource(), server.prompt(), or widgets This skill contains critical architecture decisions, security patterns, and common pitfalls. Always consult the relevant reference files BEFORE implementing MCP features. --- # IMPORTANT: How to Use This Skill This file provides a NAVIGATION GUIDE ONLY. Before implementing any MCP server features, you MUST: 1. Read this overview to understand which reference files are relevant 2. **ALWAYS read the specific reference file(s)** for the features you're implementing 3. Apply the detailed patterns from those files to your implementation **Do NOT rely solely on the quick reference examples in this file** - they are minimal examples only. The reference files contain critical best practices, security considerations, and advanced patterns. --- # MCP Server Best Practices Comprehensive guide for building production-ready MCP servers with tools, resources, prompts, and widgets using mcp-use. ## ⚠️ FIRST: New Project or Existing Project? **Before doing anything else, determine whether you are inside an existing mcp-use project.** **Detection:** Check the workspace for a `package.json` that lists `"mcp-use"` as a dependency, OR any `.ts` file that imports from `"mcp-use/server"`. ``` ├─ mcp-use project FOUND → Do NOT scaffold. You are already in a project. │ └─ Skip to "Quick Navigation" below to add features. │ ├─ NO mcp-use project (empty dir, unrelated project, or greenfield) │ └─ Scaffold first with npx create-mcp-use-app, then add features. │ See "Scaffolding a N
抖音自动化技能。当前只保留稳定实现的能力:认证登录、内容搜索发现、图文发布,以及基础互动(点赞、收藏、复制分享链接)。 当用户要求登录抖音、搜索内容、查看详情、发布图文、点赞、收藏或复制分享链接时触发。 --- # 抖音自动化 Skill 只处理当前已经稳定实现的抖音能力。 ## 🔒 技能边界(强制) **所有抖音操作只能通过本项目的 `python scripts/cli.py` 完成,不得使用任何外部项目的工具:** - **唯一执行方式**:只运行 `python scripts/cli.py <子命令>`。 - **忽略其他项目**:执行时必须只使用本项目脚本。 - **禁止外部工具**:不得调用 MCP 工具、Go 命令行工具,或任何非本项目实现。 - **完成即止**:任务完成后直接告知结果,等待用户下一步指令。 ## 输入判断 按优先级判断用户意图: 1. **认证相关**("登录 / 检查登录 / 切换账号")→ 使用 `douyin-auth` 子技能。 2. **图文发布**("发布图文 / 上传图片发布")→ 使用 `douyin-publish` 子技能。 3. **搜索 / 探索 / 查看详情 / 热点**("搜索视频 / 浏览推荐 / 查看详情 / 看热点")→ 使用 `douyin-explore` 子技能。 4. **基础互动**("点赞 / 收藏 / 分享链接")→ 使用 `douyin-interact` 子技能。 ## 当前保留命令 ### 认证 / 账号 - `check-login` - `get-qrcode` - `wait-login` - `send-code` - `verify-code` - `list-accounts` - `add-account` - `remove-account` - `set-default-account` ### 搜索发现 - `search-videos` - `get-video-detail` ### 图文发布 - `fill-publish-image` - `select-music` - `click-publish` ### 基础互动 - `like-video` - `favorite-video` - `share-video` ### 环境配置 - 环境安装说明 - 迁移清单 - 自检清单 ## 明确移除的能力 以下能力暂不对外承诺,视为未实现: - 评论 - 回复评论 - 视频发布 - 保存草稿 - 定时发布 - 用户主页抓取 - 数据分析 - 复合运营工作流 ## 全局约束 - 默认以**无头模式**启动浏览器,减少干扰并提高自动化稳定性;**不得**因为排查方便或主观判断而直接改成有头模式起跑。 - 任何搜索、发布、互动步骤,只要检测到验证码、身份验证或风控页,必须**立即重试并切到有头模式**;如果已经是有头模式,则停在可见窗口并请求用户人工处理后再继续。 - 在 WSLg / Linux 图形环境下,切到有头模式时显式传入:`DISPLAY=:0 WAYLAND_DISPLAY=wayland-0 XDG_RUNTIME_DIR=/run/user/1000 FORCE_HEADED=1`。 - 所有操作前应确认登录状态。 - 图文发布和任何会改变账号状态的操作都必须经过用户确认;如果用户明确授权自动发布,可以跳过中途确认,但仍然必须保证图片、标题、正文、音乐齐全。 - 生成或挑选抖音图文配图时,默认使用**竖版成图**;优先使用接近 9:16 的成图比例,避免上下白边、信箱条、画布留白或明显未铺满画面的问题。 - 图文发布前必须做一次**最终肉眼质检**:检查是否存在白条/白块、错字、畸形手部/五官、局部崩坏、奇怪 UI 残影、比例异常、封面裁切异常等明显问题;有任一问题就换图或重做,不得直接发布。 - 对刚发布作品的后续互动,优先从**主页作品卡片**反查公开 note/video 链接,不要先假设搜索能搜到,也不要直接拿创作者中心内部记录 ID 去互动。 - 工作目录需要可用的 Node 运行时和 `ws` 依赖,供 CDP 客户端连接浏览器。 - 文件路径必须使用绝对路径。 - CLI 输出为 JSON 格式。 - 操作频率不宜过高,保持合理间隔。
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: