القائمة
Detects the active data source provider and retrieves configuration (database IDs, constants). Internal shared skill — not for direct user invocation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Unified daily routine: ingests messages into tasks, then guides user through task refinement and dispatch. Works in both Claude Code and Cowork. Triggers on: "daily tasks", "daily routine", "run daily tasks", "デイリータスク", "日次ルーティン"
Generates or refines Acceptance Criteria and Execution Plans for tasks. Single task or batch mode. Ensures tasks are executable at agent-autonomous quality. Uses multi-round brainstorming to extract quality information from users. Triggers: "plan task", "refine task", "generate AC", "write execution plan", "plan all tasks", "auto-plan", "タスク計画", "AC作成", "実行計画作成", "タスクを計画して"
Delegates a task to another organization member by updating Assignees, resetting executor fields, and recording delegation history in Context. Triggers on: "delegate task", "assign to", "transfer task", "reassign", "タスク委任", "タスク移管", "割り当て変更"
Orchestrates autonomous task execution via current session, tmux parallel, or Cowork scheduled tasks. Fetches ready tasks, validates working directories, and dispatches to the chosen execution mode. Triggers on: "do the next task", "process tasks", "execute tasks", "ready tasks", "タスク実行", "次のタスクを実行", "タスク処理".
Performs a health check on tasks. Analyzes task age (stagnation), field completeness by status, blocked tasks (including other assignees' blockers), and executor ratio (human vs AI delegation). Supports 3 modes: specific assignee (by name), all tasks (team-wide overview), or defaults to current user when no target is specified. Use this skill whenever the user wants to monitor task health, check stagnation, audit task quality, or review AI delegation metrics — even if they don't say "monitor" explicitly. Triggers on: "monitor tasks", "task health check", "task analysis", "stagnation report", "task monitoring", "task report"
Reads incoming messages (Slack, Teams, Discord) addressed to the current user and auto-converts them into categorized Notion tasks (hearing-needed, self-action, or delegate). Designed for daily scheduled execution. Triggers on: "message intake", "intake", "process messages", "メッセージ取り込み", "メッセージ処理"
| name | detecting-provider |
| description | Detects the active data source provider and retrieves configuration (database IDs, constants). Internal shared skill — not for direct user invocation. |
| user-invocable | false |
Determine the active provider using the following layered check. Skip if already determined in this conversation.
Inspect which MCP tools are available:
notion-* tools present → active_provider = notionmcp__airtable__* tools present → active_provider = airtableIf exactly one provider MCP is detected, use it.
REQUIRED — Read ${CLAUDE_PLUGIN_ROOT}/skills/providers/{active_provider}/SKILL.md now.
This file contains query method selection logic (Query Path Detection) and data operation procedures.
Skipping this step causes incorrect query paths and suboptimal performance.
Do NOT use MCP search/fetch tools for task queries until you have read the provider SKILL.md.
If multiple provider MCPs are detected, determine the environment:
env.AGENTIC_TASKS_PROVIDER in ~/.claude/settings.jsonAGENTIC_TASKS_PROVIDER: <value> in the Global Instructions or CLAUDE.mdIf a value is found, use it as active_provider. REQUIRED — Read the corresponding provider SKILL.md (same instruction as Layer 1).
If provider is still undetermined, use AskUserQuestion:
"Multiple data source MCPs are available. Which provider should I use for agentic-tasks? Available: [list detected providers]"
If no provider MCP is found at all, inform the user they need to run the setting-up-tasks skill first to configure a data source, then stop.
After detecting the provider, also determine the execution environment and set execution_environment as a conversation context variable.
Skip if already set in this conversation.
Detection logic:
CLAUDE_CODE_IS_COWORK is 1 → execution_environment = "cowork"execution_environment = "claude-code"(CLAUDECODE=1 is common to both environments, so it is not used for detection.)
This value is used by downstream skills (executing-tasks, managing-tasks, etc.) for execution flow branching.
After detecting the provider, retrieve database IDs and constants from the Config page.
Skip if headless_config is already set in this conversation.
Follow the active provider SKILL.md's Config Retrieval section to populate headless_config.
Constants shared across skills. All skills that go through detecting-provider reference these values.
| Constant | Value | Purpose |
|---|---|---|
maxConcurrentAgents | 3 | Default maximum parallel agents (configurable in headless_config) |