メール、カレンダー、タスク管理、自動化（7,769 件）
Import information from foreign sources into a set of artifact kinds (the target), generating or updating them to reflect the imported information. Use when the user wants to "import", "ingest", or "bring in" external sources like files, URLs, or pasted text into artifacts like SPEC, CODE, DOCS, TASK, INFR, or OTHR.
日本語の概要は準備中です。原文の説明を表示しています。
Interview the user relentlessly about the task plan until reaching a shared understanding, resolving each branch of the question decision tree. Use when the user wants to stress-test a plan, get grilled on their plan, or mentions "grill me" or "grill plan".
日本語の概要は準備中です。原文の説明を表示しています。
Get or set unique task id <id>. Use when user requests to work on a certain task or wants to know what the current task is.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a new agent tool skill, written in the style of ASE skills, which orchestrates a workflow of sequential actions, parallel actions, sub-agent calls, and skill calls. Use when the user wants to "generate a skill", create a "workflow", "orchestrate" or "chain" multiple ASE skills, or automate a recurring multi-step procedure.
日本語の概要は準備中です。原文の説明を表示しています。
Condense the current or given task plan by compressing its wording. Use when the user calls to "condense", "compress", "shrink" or "shorten" the "task", "plan", "spec", or "specification".
日本語の概要は準備中です。原文の説明を表示しています。
Iteratively edit and refine a named plan for a task through a conversational loop. A new plan is optionally composed along the chosen one of several proposed crafting, refactoring, resolution, or specification approaches. Each round, the current plan is shown and the user is asked whether to keep refining, mark the plan as done, or proceed to the implementation or draft. Use when the user wants to plan a task purely through chat-driven refinement, or wants a plan to "craft" a new feature, "refactor" the code base, or "resolve" a problem (also from a bare analyzer issue id like "P1").
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing, debugging, or hardening Shell/Bash scripts in this repo (.github/workflows/*.yml steps, website build scripts, or any *.sh file) or when asked to "review bash", "revisa el script", "shellcheck", or "revisa el pipeline shell". Reviews for robustness, error handling, quoting, portability, injection, and CI-friendliness, and ends with what a CI failure or a hostile input would catch.
日本語の概要は準備中です。原文の説明を表示しています。
AI browser automation via CDP. Use when you need to control a browser, navigate pages, click elements, fill forms, extract content, or take screenshots.
日本語の概要は準備中です。原文の説明を表示しています。
Use when preparing for a sales meeting, discovery call, demo, or customer check-in. Triggers: 'prep me for a meeting with [company]', 'meeting brief for [company]', 'pre-call prep', 'I have a call with [contact] at [company]', 'meeting prep', 'call prep'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you want a monthly editorial planning workshop that produces a rolling calendar, themes, and a repurposing matrix.
日本語の概要は準備中です。原文の説明を表示しています。
Generates email sequences for different contexts. Currently supports event follow-up sequences. Produces ready-to-send emails with subject lines, body copy, and timing guidance.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you want an email sequence, especially event follow-up emails with timing guidance and ready-to-send copy.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you want a weekly feature announcement package from recent merge requests, including Slack, blog, LinkedIn, and carousel outputs.
日本語の概要は準備中です。原文の説明を表示しています。
Interactive workshop that builds a monthly rolling editorial calendar using MKT1 methodology. Walks through Perceptions, content pillars, themes, and capacity to produce a 4-week detailed plan plus 3-month roadmap. Designed to be re-run monthly.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a brand's positioning into a 30-day, multi-platform content batch — 3-7 pillars, subtopic matrix mapped to funnel stage and persona, pillar pieces plus derivative fan-out, proof elements in at least half the slots, all registered in the editorial calendar store and quality-gated. Use when "content batch", "batch my content", "30 days of content", "month of content", "content batching machine", "content pillars", "fill the content calendar", "plan a month of posts", or any request to produce a full month of multi-platform content in one run.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare an approved social content queue for BulkPublish scheduling or publication. Use when "schedule social posts", "publish the calendar", "send posts to BulkPublish", or "hand off approved social content".
日本語の概要は準備中です。原文の説明を表示しています。
Plan and produce a content calendar — a month (or quarter) of blog posts, LinkedIn articles, and SEO content mapped to business goals, personas, and keywords. Generates briefs for each piece, optionally batch-produces all content with quality gates. Use when "content calendar", "plan blog content", "monthly content", "quarterly content plan", "what should we publish", "content strategy", "editorial calendar", or any request to plan multiple pieces of content over time.
日本語の概要は準備中です。原文の説明を表示しています。
Build email nurture flows using lifecycle marketing + perception engineering frameworks. Generates subject lines, body copy, and send timing.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and batch-produce an entire email system for a product. Maps every lifecycle touchpoint (onboarding, activation, conversion, retention, transactional, win-back), generates all emails with quality gates, outputs Loops-ready copy. Use when "create all emails", "email system", "build email sequences", "lifecycle emails", "onboarding sequence", "set up transactional emails", "plan all the emails for [product]", or any request to systematically produce a complete set of emails for a platform.
日本語の概要は準備中です。原文の説明を表示しています。
Universal task initializer that automatically loads PAI context for all user requests. Ensures complete context availability (contacts, preferences, protocols) before responding to any task. (project, gitignored)
日本語の概要は準備中です。原文の説明を表示しています。
Use when you have a spec or requirements for a multi-step task, before touching code
日本語の概要は準備中です。原文の説明を表示しています。
Conventions and APIs for the offload-project/laravel-waitlist package — multiple waitlists, entry status tracking, optional email verification, lifecycle events, mailing list sync (Mailchimp/Kit/Audienceful), and bridge into laravel-invite-only.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user reports a problem or names a piece of work and wants to start on it in a fresh worktree — "start a task", "new task", "file this and make a branch", "/start-task". Finds or files the GitHub issue, creates the feat/… or bugfix/… branch linked to it, and prints the paste-ready `ai fwt|bwt` (Docker) and `ai os fwt|bwt` (host) commands that open the worktree. Linear flow with hard stops; asks nothing.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end OCA module migration workflow for porting addons between Odoo major versions and preparing [MIG] pull requests. Use when migrating OCA modules, porting addons between Odoo versions, applying OCA migration checklists, resolving migration patch conflicts, or preparing versioned OCA migration PRs.
日本語の概要は準備中です。原文の説明を表示しています。