作業の依存関係を整理し、独立した調査・実装・検証を並行して進めるためのスキルです。変更先の競合を避け、各作業の完了状況と確認結果を表にまとめます。
- 独立したファイル調査の一括実行
- 複数エージェントでの分担実装
- Git worktreeで変更先を分けたいとき
1.8万 件 ・ 関連度順
概要と使いどころ
作業の依存関係を整理し、独立した調査・実装・検証を並行して進めるためのスキルです。変更先の競合を避け、各作業の完了状況と確認結果を表にまとめます。
複雑な作業や失敗から、根本原因、次回の行動、問題を見分ける兆候を抽出し、再利用できる学習記録にまとめます。同じ原因の既存記録との重複も整理します。
開発の目的に合うECCのコマンド群を選び、実行順序と停止条件を案内します。現在のファイルを基に一覧も整理し、複数コマンドの使い分けを助けます。
Claude Codeの記憶、定期実行、タスク待ち行列を組み合わせ、継続的な作業を設計するスキル。外部の実行環境や画面操作の連携設定も案内します。
AIエージェントによる有料APIやサービスへの支払いをx402で組み込み、タスク別・セッション別の予算、送金先の制限、秘密鍵を自分で管理するウォレットを設定します。
初期設定で選んだアプリや利用目的を引き継ぎ、最初の依頼を具体的な成果物にします。仕事の要約、HTMLページ、自動化スクリプト、アプリ導入などの小さな作業を進めます。
動画の企画を整理し、作風に合う専門エージェントのチームと制作環境を組むスキル。Hermesのカンバンで作業を振り分け、進捗確認や停止・失敗時の対応を支援します。
Use when a task is too large for one model pass, needs parallel research or generation across many subtasks (like researching a dozen competitors at once), or the user asks to orchestrate multiple models, split work across a model team, run an advisor-worker loop, have a stronger model review the plan while cheap workers execute, or says "too big for one model" or "fan this out". Not for single-file edits or tasks one model handles in one pass.
日本語の概要は準備中です。原文の説明を表示しています。
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
日本語の概要は準備中です。原文の説明を表示しています。
Guide the user's first Paperclip task when its description invokes /first-task. Interpret the opening answer, clarify their goal, propose a plan or a single task, and wait for approval before hiring agents or executing approved work.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate supervised Orca workers: threaded messages, blocking ask/reply, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator loops, and decomposing work across agents. Use `orca-cli` for full ownership handoffs — "hand off", "handoff", "handover", "give this to another agent", "another worktree" — unless asked to supervise, monitor, or coordinate a DAG, and for terminal control, lightweight terminal prompts, shell commands, Orca worktree management, and reading or waiting on terminals.
日本語の概要は準備中です。原文の説明を表示しています。
Creates, assigns, and updates tasks in an AI team run so work has one owner and one deliverable each. Use when the user asks to break down, assign, claim, block, or complete tasks in a run. Changes recorded task state only.
日本語の概要は準備中です。原文の説明を表示しています。
Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.
日本語の概要は準備中です。原文の説明を表示しています。
Scales pandas, NumPy, and custom Python research workflows beyond memory or across clusters with Dask. Covers DataFrames, Arrays, Bags, Futures, chunking, schedulers, and distributed diagnostics. Use for partitioned file processing, scientific array computation, or parallel tasks whose memory and dependency structure require Dask.
日本語の概要は準備中です。原文の説明を表示しています。
Prepares the user for a specific interview from their real experience. Builds a story bank in Situation/Task/Action/Result/Reflection form mapped to the competencies the role and company test (such as Amazon's Leadership Principles), writes a cited company and role brief from public sources, predicts questions per round, drafts opener, why-us, weakness and salary answers, prepares questions to ask and a logistics checklist, and runs a post-interview debrief. Use when the user says "help me prepare for my interview", "I have an interview tomorrow" or "in 2 hours", "build my story bank", "STAR stories", "interviewing as a career changer", "what will they ask me", "how do I answer tell me about yourself", "questions to ask the interviewer", "research the company" or "debrief my interview". Uses Reactive Resume MCP tools when connected. For scored role-play practice, mock-interview; for thank-you notes and tracking, job-application-manager; for a salary number, offers or negotiation, offer-negotiation.
日本語の概要は準備中です。原文の説明を表示しています。
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
日本語の概要は準備中です。原文の説明を表示しています。
Google Tasks: Manage task lists and tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Scores inbound HubSpot leads by engagement signals, company fit, and urgency markers, ranks the ones worth a call today with talking points, drafts the follow-ups, and proposes calendar times for the owner to book. Use when the owner asks to prioritize, score, or rank leads, asks "who should I call first," or asks about their pipeline. An ask that wants the ranked leads turned into a call list with time blocked on the calendar routes to /call-list, which runs this skill first and then books the time.
日本語の概要は準備中です。原文の説明を表示しています。
Deprecated redirect skill that routes legacy 'content creator' requests to the correct specialist. Use when a user invokes 'content creator', asks to write a blog post, article, guide, or brand voice analysis (routes to content-production), or asks to plan content, build a topic cluster, or create a content calendar (routes to content-strategy). Does not handle requests directly — identifies user intent and redirects to content-production for writing/SEO/brand-voice tasks or content-strategy for planning tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Build, deploy and operate Kortix Apps through the pre-authenticated CLI or SDK: static sites and SPAs, Dockerfile or OCI servers, workers, and stateful backends (a database, a Convex backend) with persistent volumes, snapshots and built-in Kortix sign-in. Use when the user asks to publish, host, deploy, preview, inspect, scale, wake, suspend, roll back, debug, or remove an App; asks for a database, an API, a backend, a data model, auth, or 'store this'; asks for an internal tool, business app, CRM, tracker, dashboard, portal, or any app the team logs in to; before writing any Convex code; or asks what an App costs or how it runs.
日本語の概要は準備中です。原文の説明を表示しています。
Turns decided work — a PRD, design doc, RFC, or thread — into tasks a builder can act on without guessing. Finds slices that each prove something, grounds them in the code, and writes intent, observable criteria with concrete values, the boundary, what the change disturbs, and only the decisions that are hard to reverse. Walks every surface the work exposes and sweeps the nine unwritten requirements, recording each landing as a criterion already in the source, existing behaviour, n/a, or Unresolved — never as a criterion the walk invented. Defaults to one task per source. Use when the user says "write the task", "cut this PRD into tasks", "turn this design doc into work", or "tlc-plan". Do NOT use for discovery itself or to implement — a one-line ticket is a decision; a blank wish is not.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you act as Leader to turn ready Quick Task or Project Work state into Worker task instructions, send assignment messages, check submitted results, and define completion/blocker report contracts. Do not use to create projects, create rooms, or execute Worker tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Use when admin gives a task to delegate to a Worker, when a Worker reports task completion, when managing recurring scheduled tasks, or when you need to check worker availability.
日本語の概要は準備中です。原文の説明を表示しています。
Review a task implementation against approved specs, task boundaries, and verification evidence. Use after an implementer finishes a task, after remediation, or before accepting a task as complete.
日本語の概要は準備中です。原文の説明を表示しています。