AlphaMoatによると、2026-10時点でDecomposes complex user requests into executable subtasks, identifies required capabilities, searches for existing skills at skills.sh, and creates new skills when no solution exists. This skill should be used when the user submits a complex multi-step request, wants to automate workflows, or needs help breaking down large tasks into manageable pieces.のダウンロード数は14,243、スター数は12で、累計ダウンロード数で今回のランキング対象AIスキル10,914件中1,971位、AIエージェントでは1,632件中270位です。
一覧の初期表示は累計ダウンロード数順で、スター数順にも並べ替えできます。詳細ページの順位は累計ダウンロード数で計算しています。
| プラットフォーム | ダウンロード数 | スター数 | コメント |
|---|---|---|---|
| ClawHub ↗ | 9212 | 12 | - |
| SkillHub ↗ | 1.4万 | 12 | — |
プラットフォームごとに集計方法と集計時点が異なります。
このスキルは依頼を原子レベルのサブタスクに分解し、各タスクを汎用能力分類に割り当て、skills.sh で既存スキルを検索し、該当がない場合は新規スキルを作成します。構造化された分解レポートと実行計画を出力し、スキル作成にはユーザー承認が必要と記載します。
資料公開日 2026-10-27
スキルのドキュメントをもとに生成した例であり、実際の実行結果ではありません。
2026-09 から集計方法を変更し、同名スキルを作者ごとに分けて集計し、全スキルを対象にしました。破線は変更前の月で、変更後のデータとは直接比較せず、変更をまたぐ増減も計算していません。 同名の別スキルがあるため、変更前のデータは現在ダウンロード数が最も多いこのスキルに帰属させています。
| 月 | ダウンロード数 | 前月比 | スター数 |
|---|---|---|---|
| 2026-10 | 1.4万 | — | 12 |
| 2026-09 | 9019 | — | 12 |
| 2026-08 | 9272 | +1.8% | 12 |
| 2026-07 | 9112 | +2.9% | 12 |
| 2026-06 | 8853 | +3.0% | 12 |
| 2026-05 | 8593 | — | 12 |
| 2026-03 | 6716 | — | 10 |
作者が公開した元のファイルをテキストのまま表示しています。AlphaMoat による編集や審査はしていません。リンクはクリックできません。コマンドは内容を確認してから実行してください。取得日 2026-10-23。
--- name: task-decomposer description: Decomposes complex user requests into executable subtasks, identifies required capabilities, searches for existing skills at skills.sh, and creates new skills when no solution exists. This skill should be used when the user submits a complex multi-step request, wants to automate workflows, or needs help breaking down large tasks into manageable pieces. --- # Task Decomposer & Skill Generator This skill helps decompose complex user requests into executable subtasks, identify required capabilities for each task, search for existing skills from the open skills ecosystem, and automatically create new skills when no existing solution is available. ## Core Workflow
```
User Request → Task Decomposition → Capability Identification → Skill Search → Gap Analysis → Skill Creation → Execution Plan
```
## Phase 1: Task Analysis & Decomposition
When receiving a user request, follow these steps:
### Step 1: Understand User Intent
Analyze the request to identify:
- **Core objective**: What is the end goal?
- **Domains involved**: What areas of expertise are needed?
- **Trigger mechanism**: One-time, scheduled, or event-driven?
Example analysis:
```
User Input: "Help me get email summaries every morning and send them to Slack"
Analysis:
- Core objective: Automated email digest delivery to Slack
- Domains: Email access, content summarization, messaging
- Trigger: Scheduled (daily morning)
```
### Step 2: Decompose into Atomic Tasks
Break down the complex task into minimal executable units:
```yaml
Task Decomposition:
- task_id: 1
name: "Access and retrieve email list"
type: "data_retrieval"
input: "Email credentials/session"
output: "List of emails with metadata"
dependencies: []
- task_id: 2
name: "Extract key information from emails"
type: "data_extraction"
input: "Email list"
output: "Structured email data"
dependencies: [1]
- task_id: 3
name: "Generate email summary"
type: "content_generation"
input: "Structured email data"
output: "Formatted summary text"
dependencies: [2]
- task_id: 4
name: "Send message to Slack"
type: "message_delivery"
input: "Summary text, Slack webhook/token"
output: "Delivery confirmation"
dependencies: [3]
- task_id: 5
name: "Configure scheduled execution"
type: "scheduling"
input: "Workflow script, schedule config"
output: "Active scheduled job"
dependencies: [4]
```
## Phase 2: Capability Identification
Map each subtask to a capability type from the universal capability taxonomy.
### Universal Capability Types
| Capability | Description | Search Keywords |
|------------|-------------|-----------------|
| `browser_automation` | Web navigation, interaction, scraping | browser, selenium, puppeteer, playwright, scrape |
| `web_search` | Internet search and information retrieval | search, google, bing, duckduckgo |
| `api_integration` | Third-party API communication | api, rest, graphql, webhook, {service-name} |
| `data_extraction` | Parse and extract structured data | parse, extract, scrape, ocr, pdf |
| `data_transformation` | Convert, clean, transform data | transform, convert, format, clean, etl |
| `content_generation` | Create text, images, or other content | generate, write, create, summarize, translate |
| `file_operations` | Read, write, manipulate files | file, read, write, csv, excel, json, pdf |
| `message_delivery` | Send notifications or messages | notify, send, email, slack, discord, telegram |
| `scheduling` | Time-based task execution | schedule, cron, timer, daily, weekly |
| `authentication` | Identity and access management | auth, oauth, login, token, credentials |
| `database_operations` | Database CRUD operations | database, sql, mongodb, query, store |
| `code_execution` | Run scripts or programs | execute, run, script, shell, python |
| `version_control` | Git and code repository operations | git, github, gitlab, commit, pr, review |
| `testing` | Automated testing and QA | test, jest, pytest, e2e, unit |
| `deployment` | Application deployment and CI/CD | deploy, docker, kubernetes, ci-cd, release |
| `monitoring` | System and application monitoring | monitor, alert, log, metrics, health |
### Capability Identification Process
For each subtask:
1. Analyze the task description and requirements
2. Match to one or more capability types
3. Generate search keywords for skill discovery
Example:
```yaml
Task: "Send message to Slack"
Capability: message_delivery
Search Keywords: ["slack", "notification", "message", "webhook"]
```
## Phase 3: Skill Search
Use the Skills CLI to search for existing skills at https://skills.sh/
### Search Process
For each capability need, search using relevant keywords:
```bash
# Search for skills matching the capability
npx skills find <keyword>
# Examples:
npx skills find slack notification
npx skills find browser automation
npx skills find pdf extract
npx skills find github api
```
### Evaluate Search Results
When results are returned:
```
Install with npx skills add <owner/repo@skill>
owner/repo@skill-name
└ https://skills.sh/owner/repo/skill-name
```
Evaluate each result for:
- **Relevance**: Does it match the required capability?
- **Completeness**: Does it cover all needed functionality?
- **Quality**: Is it well-documented and maintained?
### Generate Capability Mapping
```yaml
Capability Mapping:
- task_id: 1
capability: browser_automation
search_query: "browser email automation"
found_skills:
- name: "anthropic/claude-skills@browser-use"
url: "https://skills.sh/anthropic/claude-skills/browser-use"
match_score: high
recommendation: "Install browser-use skill"
- task_id: 4
capability: message_delivery
search_query: "slack notification"
found_skills: []
recommendation: "Create new skill: slack-notification"
```
## Phase 4: Gap Analysis
Identify tasks without matching skills:
### Built-in Capabilities (No Skill Needed)
These capabilities are typically handled by the agent's native abilities:
- `content_generation` - LLM's native text generation
- `data_transformation` - Basic data manipulation via code
- `code_execution` - Direct script execution
- `scheduling` - System-level cron/scheduler configuration
### Skills Required
For capabilities without built-in support, determine:
1. **Skill exists**: Install from skills.sh
2. **Skill not found**: Create new skill
## Phase 5: Skill Creation
When no existing skill matches a required capability, create a new skill.
### Skill Creation Process
1. **Define scope**: Determine what the skill should do
2. **Design interface**: Define inputs, outputs, and usage patterns
3. **Create SKILL.md**: Write the skill definition file
4. **Add resources**: Include scripts, references, or assets as needed
### Skill Template
```markdown
---
name: {skill-name}
description: {Clear description of what the skill does and when to use it. Written in third person.}
---
# {Skill Title}
{Brief introduction explaining the skill's purpose.}
## When to Use
{Describe scenarios when this skill should be triggered.}
## Prerequisites
{List any required installations, configurations, or credentials.}
## Usage
{Detailed usage instructions with examples.}
### Basic Usage
```bash
{Basic command or code example}
```
### Advanced Usage
{More complex examples and options.}
## Configuration
{Any configuration options or environment variables.}
## Examples
### Example 1: {Use Case}
{Step-by-step example with code.}
## Troubleshooting
{Common issues and solutions.}
```
### Initialize New Skill
```bash
# Create skill using the skills CLI
npx skills init <skill-name>
# Or manually create the structure:
# skill-name/
# ├── SKILL.md (required)
# ├── scripts/ (optional)
# ├── references/ (optional)
# └── assets/ (optional)
```
## Phase 6: Generate Execution Plan
Compile all information into a structured execution plan:
```yaml
Execution Plan:
title: "{Task Description}"
prerequisites:
- "{Prerequisite 1}"
- "{Prerequisite 2}"
skills_to_install:
- skill: "owner/repo@skill-name"
command: "npx skills add owner/repo@skill-name -g -y"
url: "https://skills.sh/owner/repo/skill-name"
skills_to_create:
- name: "{new-skill-name}"
capability: "{capability_type}"
description: "{What it does}"
execution_steps:
- step: 1
task: "{Task name}"
skill: "{skill-name | built-in}"
action: "{Specific action to take}"
- step: 2
task: "{Task name}"
skill: "{skill-name | built-in}"
action: "{Specific action to take}"
verification:
- "{How to verify step 1 succeeded}"
- "{How to verify step 2 succeeded}"
```
## Task Decomposition Principles
### Principle 1: Atomicity
Each subtask should be the minimal executable unit with clear input and output.
### Principle 2: Independence
Minimize dependencies between tasks to allow parallel execution where possible.
### Principle 3: Verifiability
Each task should have a clear way to verify successful completion.
### Principle 4: Reusability
Identify reusable patterns and prefer creating general-purpose skills.
### Principle 5: Single Responsibility
Each task should do one thing well.
## Output Format
Present the decomposition results in a structured format:
```
════════════════════════════════════════════════════════════════
📋 TASK DECOMPOSITION REPORT
════════════════════════════════════════════════════════════════
🎯 Original Request:
{User's original request}
────────────────────────────────────────────────────────────────
📊 SUBTASKS
────────────────────────────────────────────────────────────────
┌─────┬────────────────────────┬───────────────────┬───────────┐
│ ID │ Task │ Capability │ Status │
├─────┼────────────────────────┼───────────────────┼───────────┤
│ 1 │ {task name} │ {capability} │ Found │
│ 2 │ {task name} │ {capability} │ Built-in │
│ 3 │ {task name} │ {capability} │ Create │
└─────┴────────────────────────┴───────────────────┴───────────┘
────────────────────────────────────────────────────────────────
🔍 SKILL SEARCH RESULTS
────────────────────────────────────────────────────────────────
Task 1: {task name}
Search: npx skills find {keywords}
Found: owner/repo@skill-name
URL: https://skills.sh/owner/repo/skill-name
Task 3: {task name}
Search: npx skills find {keywords}
Found: No matching skills
Action: Create new skill
────────────────────────────────────────────────────────────────
🛠️ SKILLS TO CREATE
────────────────────────────────────────────────────────────────
1. {skill-name}
Capability: {capability_type}
Description: {what it does}
────────────────────────────────────────────────────────────────
📝 EXECUTION PLAN
────────────────────────────────────────────────────────────────
Prerequisites:
• {prerequisite 1}
• {prerequisite 2}
Steps:
1. {action} using {skill}
2. {action} using {skill}
3. {action} using {skill}
════════════════════════════════════════════════════════════════
```
## Examples
### Example 1: Workflow Automation
**User Request:**
```
Create a workflow that monitors GitHub issues, summarizes new issues, and posts notifications to Discord
```
**Decomposition:**
```yaml
Subtasks:
1. Monitor GitHub repository for new issues
Capability: api_integration
Search: "npx skills find github issues"
2. Extract issue content and metadata
Capability: data_extraction
Status: Built-in (code)
3. Generate issue summary
Capability: content_generation
Status: Built-in (LLM)
4. Send notification to Discord
Capability: message_delivery
Search: "npx skills find discord notification"
5. Configure webhook or polling trigger
Capability: scheduling
Status: Built-in (system)
```
### Example 2: Data Pipeline
**User Request:**
```
Search for AI research papers, download PDFs, extract key findings, and save to Notion
```
**Decomposition:**
```yaml
Subtasks:
1. Search for AI research papers
Capability: web_search
Search: "npx skills find academic search"
2. Download PDF files
Capability: browser_automation
Search: "npx skills find browser download"
3. Extract text from PDFs
Capability: data_extraction
Search: "npx skills find pdf extract"
4. Generate summaries of key findings
Capability: content_generation
Status: Built-in (LLM)
5. Save to Notion database
Capability: api_integration
Search: "npx skills find notion"
```
## Best Practices
1. **Start with skill search**: Always check https://skills.sh/ before creating new skills
2. **Use specific search terms**: Combine capability keywords with domain terms
3. **Leverage built-in capabilities**: Don't create skills for things the agent can do natively
4. **Create reusable skills**: Design new skills to be general-purpose when possible
5. **Document thoroughly**: New skills should have clear usage instructions
6. **Verify before proceeding**: Confirm skill installation before executing tasks
7. **Handle errors gracefully**: Include fallback strategies in execution plans
## Integration with find-skills
This skill works in conjunction with the `find-skills` skill for discovering existing solutions:
```bash
# Search the skills ecosystem
npx skills find <query>
# Install a discovered skill
npx skills add <owner/repo@skill> -g -y
# Browse all available skills
# Visit: https://skills.sh/
```
## Notes
- Always search for existing skills before creating new ones
- Built-in capabilities (LLM, basic code) don't require skills
- Skill creation requires user confirmation before proceeding
- Complex workflows may need multiple skills working together
開発中の学び、エラー、訂正を Markdown ファイルに記録し、再利用やワークスペースの記憶への昇格に備えます。
やりたいことを自然文で伝えると、ローカルとリモートのカタログからスキルを探して推薦するスキルです。
AI エージェント向けのブラウザ自動化コマンドラインスキルです。
利用者の訂正と自己点検を層構造の記憶に蓄え、使われ方に応じて昇格や保管を行うスキルです。
AI エージェントの先回り、作業記憶、振り返りの手順を計画するためのワークスペース設定ガイドです。
効果的な Claude スキルの作成・更新ガイドです。
第三者のスキルを入れる前に、出所と権限と危険な作りを手順に沿って調べるスキルです。
以李白(701—762,字太白,号青莲居士,世称诗仙)的诗学观、意象系统与口吻,进行唐诗赏析、文学评论、考据问答与拟体创作。触发词:李白、李太白、太白、青莲居士、诗仙、谪仙人、将进酒、静夜思、蜀道难、唐诗、盛唐诗人、浪漫主义诗人、拟李白风格、以李白视角、李白会怎么写、用李白口吻。能力:诗词鉴赏与风格DNA解析、诗学观与文学谱系评述、诗句出处考据与真伪边界标注、以李白口吻答问、拟李白体旧体诗(必显式标注非原作)。适用边界:仅用于唐代文学与古典诗歌相关话题,非此类话题不触发;本 skill 为文学普及与研究辅助,不代表李白本人立场,所拟之作均非李白原作;涉及生平佚事、篇目归属等内容不构成学术定论,皆标存疑或待考。
DuckDuckGo でリアルタイムのウェブ情報を検索するスキルです。
メールにログインして毎日の要約を作るスキルです。
データ月:2026-10 · ダウンロード数とスター数は公開スキルレジストリ(ClawHub、SkillHub)から月単位で集計しています。詳しくはデータの方法論をご覧ください。