388 件 ・ 関連度順
概要と使いどころ
Choose a practical social media posting cadence by channel, campaign period, audience, available assets, and review capacity. Use when deciding how often to post and how to distribute formats over time.
日本語の概要は準備中です。原文の説明を表示しています。
Codified expertise for demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation at multi-location retailers. Informed by demand planners with 15+ years experience managing hundreds of SKUs. Includes forecasting method selection, ABC/XYZ analysis, seasonal transition management, and vendor negotiation frameworks. Use when forecasting demand, setting safety stock, planning replenishment, managing promotions, or optimizing inventory levels.
日本語の概要は準備中です。原文の説明を表示しています。
Designs multi-step agent workflows with tool usage, retry logic, state management, and budget controls. Provides orchestration diagrams, tool execution order, fallback strategies, and cost limits. Use for "AI agents", "agentic workflows", "multi-step AI", or "autonomous systems".
日本語の概要は準備中です。原文の説明を表示しています。
Planning specialist that breaks a VNX feature or track into small, independently-shippable PRs with dependencies and per-PR task-class routing. USE THIS when the user wants to break a feature down into PRs, sequence the work, or turn a plan into a PR queue. Delegated to by @horizon (formerly @pm — @pm still resolves via alias). Works from Horizon's tracks DB (`vnx horizon`, alias `vnx objective`); the repo FEATURE_PLAN.md is a generated generic example, not the source.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a weekly Facebook Page content plan from a theme, audience, and content pillars. Produces per-day picks (short post vs story post, hook formula, angle, posting time, primary goal), a short-to-story post mix, a daily comment-reply target, and a share-optimized goal-mix balance check across shares, comments, and reactions. Use when the user wants to plan a week of Page content. Not for drafting one post (use fb-post-writer) or replying to comments (use fb-engagement-drafter).
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing an autonomous agent, planning agent architecture, building a scheduled automation, or creating a Claude Code agent workflow. Triggers: 'design an agent', 'build an automation', 'agent architecture', 'automate this workflow', 'create a scheduled agent', 'shell script agent'.
日本語の概要は準備中です。原文の説明を表示しています。
Build a weekly YouTube upload plan: long-form vs YouTube Shorts mix, posting cadence, per-slot title and thumbnail pairing, hook angle, community-tab posts between uploads, and a goal balance across CTR, retention, and subscribes. Maps Shorts as top-of-funnel that points at long-form, and long-form as the loyalty and watch-time engine. Use to plan a week or a content calendar instead of shipping ad hoc. Not for writing a single title, description, or hook (use the dedicated yt skills).
日本語の概要は準備中です。原文の説明を表示しています。
Partnership and co-marketing campaign planner — partner selection criteria, joint content strategy, cross-promotion plans, and co-branded assets. Use when "partnership", "co-marketing", "partner program", "cross-promotion", "joint venture", "co-branded", "partner campaign", or any request to plan or execute a marketing partnership.
日本語の概要は準備中です。原文の説明を表示しています。
Manages ArgoCD Application sync waves and hooks through the ArgoCD REST API and Kubernetes custom resources. Uses kubectl diff and Helm template rendering to validate manifests before triggering progressive rollouts via Argo Rollouts.
日本語の概要は準備中です。原文の説明を表示しています。
Leverages Ahrefs REST API v3 to identify content gap opportunities through competing domain analysis. Pulls referring domains data, anchor text distributions, and DR metrics to prioritize content creation for link-worthy topics.
日本語の概要は準備中です。原文の説明を表示しています。
Breaks down complex tasks into ordered, verifiable sub-tasks with dependencies, milestones, and risks.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically routes requests to the correct skill (Planner, Debugger, Advisor, etc.) based on first message content.
日本語の概要は準備中です。原文の説明を表示しています。
Authoritative reference for working with the released Wandelbots NOVA API v2 in the wandelbots-nova Python SDK. Use whenever a task touches the NOVA API, the generated `wandelbots_api_client` models (`nova.api.models.*`), motion planning requests (`plan_trajectory`, `MotionGroupSetup`, `LimitSet`, `LimitsOverride`), robot limits, or torque/velocity/acceleration/jerk limits. Reach for this skill before guessing field names or assuming a field exists — the installed client reflects the RELEASED API, while nightly specs may contain unreleased fields. Especially relevant for controller-reported limits (e.g. KUKA torque) and any "does field X exist / how is it forwarded to the planner?" question.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a weekly Threads (Meta) content plan from a theme, audience, and content pillars. Produces per-day recommendations (single post vs thread, Threads hook formula, angle, posting time, primary goal), a single-to-thread mix, daily reply and quote-post targets, and a goal-mix balance check across replies, reposts, likes, and quotes. Use when the user wants to plan a week of Threads content instead of ad-hoc posting. Not for drafting one post or thread (use threads-post-writer).
日本語の概要は準備中です。原文の説明を表示しています。
実装計画・設計書からタスクを分解し、ファイル単位の依存関係を分析して 並列実行可能な Wave に自動グルーピングするスキル。 編集ファイルが被らないタスクは全て同時並列にし、 Mermaid 依存関係図 + ディレクトリ分割された TODO ファイル群を出力する。 team-plan の後工程、team-implement の前工程として使える。 Use when: 実装計画を並列タスクに分解したい、Wave 実行順序を設計したい、 タスクの依存関係を可視化したい、分業できる部分を洗い出したい。 Triggers: "タスク分解", "並列タスク", "parallel task", "Wave 設計", "依存関係を整理", "分業", "タスクリスト作成", "並列計画", "task breakdown", "parallel plan", "wave planning", "同時に進められる"
When the user wants to plan a product launch, feature announcement, release strategy, or go-to-market plan. Also use when the user mentions 'launch plan', 'go to market', 'GTM', 'Product Hunt', 'beta launch', 'how do I launch', 'pre-launch', 'launch checklist', 'distribution plan', 'release strategy', 'feature announcement', or is about to ship something and needs a distribution plan. Even vague requests like 'I'm almost done building, what now?' or 'how do I get users?' should trigger this skill. Make sure to use this whenever someone is planning ANY kind of product or feature release, even if they don't say 'launch' explicitly — if they're thinking about getting something in front of users, this is the skill. This is the STRATEGIC planner — for operational platform submissions and directory launches, see /startup-launcher instead.
日本語の概要は準備中です。原文の説明を表示しています。
리서치 에이전트. RFP 분석 결과를 기반으로 시장 환경, 경쟁/벤치마킹, 타겟 인사이트, Best Practice, KPI 벤치마크 5대 영역을 웹 리서치하여 research_brief.md를 생성합니다. Planner가 Evidence에 실제 데이터를 사용할 수 있도록 지원합니다. 트리거: 리서치, 시장조사, 트렌드, 벤치마킹, research, 시장 분석, 경쟁 분석
日本語の概要は準備中です。原文の説明を表示しています。
Refactoring pipeline: analyzes a target file or directory for code quality issues, plans safe incremental improvements, optionally writes tests first as a safety net, implements the changes, and reviews the result. Orchestrates refactor-planner → (test-writer) → parallel-task-orchestrator → code-reviewer.
日本語の概要は準備中です。原文の説明を表示しています。
策略（Camp）· 战役策划师。专注于营销战役策略制定、受众定义、渠道组合、预算分配和内容日历编排。
日本語の概要は準備中です。原文の説明を表示しています。
研究编辑（季要纲 Ji）。由 research-chief-editor 主理人调度，分析 Phase 1 初步调研摘要，提取核心观点，确定报告标题，规划章节大纲（3-5 章），管理章节不重叠、逻辑递进。也负责根据用户反馈修改大纲。 触发词：由 research-chief-editor 主理人调度执行，不直接面向用户。当主理人下发 Phase 2 规划任务时激活。
日本語の概要は準備中です。原文の説明を表示しています。
Build a measured semantic core for a brand through official keyword APIs (Yandex Wordstat for RU, Google Ads Keyword Planner / Bing Webmaster worldwide, autocomplete everywhere), commit it as core.json plus a questions.csv, and hand that straight to an open-geo visibility run. Use when the user wants demand research, a semantic core, keyword volume, or "collect the questions and then measure visibility" — no browser and no manual keyword tool.
日本語の概要は準備中です。原文の説明を表示しています。
Use Codex (CLI + AppServer) as the full agent provider — planning, tool orchestration, native compaction, MCP tools, session resume — in place of the Claude Agent SDK. ChatGPT subscription or OPENAI_API_KEY. Per-group via agent_provider. Distinct from using OpenAI as an MCP tool (where Claude remains the planner).
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing an autonomous agent, planning agent architecture, building a scheduled automation, or creating a Claude Code agent workflow. Triggers: 'design an agent', 'build an automation', 'agent architecture', 'automate this workflow', 'create a scheduled agent', 'shell script agent'.
日本語の概要は準備中です。原文の説明を表示しています。
Route Microsoft Graph work from VS Code. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
日本語の概要は準備中です。原文の説明を表示しています。