Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
中文简介正在准备中。当前显示原文说明。
邮件、日历、任务管理、自动化(7848 个)
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
中文简介正在准备中。当前显示原文说明。
Commit, push, and open a PR using the cheap low-token git-ops agent. Use for git/github wrap-up — git commit, git push, gh pr create, "ship it", "open a PR", "create the PR", "push and PR", end-of-task git handoff.
中文简介正在准备中。当前显示原文说明。
Reddit automation skill collection. Supports authentication, content publishing, search & discovery, social interactions, and compound operations. Triggered when a user asks to operate Reddit (post, search, comment, login, analyze, upvote, save).
中文简介正在准备中。当前显示原文说明。
Check and install prerequisites for the Todo app project. Use when setting up the development environment, when a user first opens the workspace, when troubleshooting missing tools, or when the user mentions setup, install, prerequisites, or environment.
中文简介正在准备中。当前显示原文说明。
Auto-activate for litestar_queues, QueuePlugin, QueueConfig, WorkerConfig, QueueService, @task, QueuedBackgroundTask, QueueEventsConfig, or SQLSpecBackendConfig. Not for litestar-saq, Celery, or Dramatiq.
中文简介正在准备中。当前显示原文说明。
Auto-activate for litestar_email, EmailPlugin, EmailConfig, EmailService, EmailMessage, SMTPConfig, ResendConfig, SendGridConfig, MailgunConfig, SESConfig. Not for marketing APIs — use vendor SDKs.
中文简介正在准备中。当前显示原文说明。
问题到方案 Workflow:当用户显式调用 `$problem-to-solution`,或明确要求运行“问题到方案”完整流程时使用。 把模糊产品问题经过校准、必要的研究/决策、方案生成和挑战,推进为一个可进入 PRD 的已确认方案;不负责 PRD 交付或外部发布。
中文简介正在准备中。当前显示原文说明。
方案到交付 Workflow:当用户显式调用 `$solution-to-delivery`,或明确要求运行“方案到交付”完整流程时使用。 把已确认产品方案转成经过独立 Review 的 PRD、适用的 UI/HTML/截图、版本拆分和 Product Delivery Package;当前 Agent Runtime 只做 Package 发布 dry-run,真实写入保持 authorization_required。
中文简介正在准备中。当前显示原文说明。
研究プロジェクトの定例会議、日程調整、アジェンダ、議事録、ToDoフォローアップを運営する
中文简介正在准备中。当前显示原文说明。
Deliberate system-improvement loop — audit your own Claude Code setup (rules / memory / skills / MCP / agents / registry), evaluate incoming tools via /vet, adopt the worthwhile ones with discipline (backup → verify), and record every decision. Use when bringing in a tool/idea/collection to improve the setup, or when doing a tooling-improvement pass. Triggers — "upgrade the workflow", "audit our setup", "let's improve the tooling", "evaluate this for us", when handed a post/repo/reel with a tool.
中文简介正在准备中。当前显示原文说明。
Phased workflow for delivering a Drupal feature or non-trivial change: plan, implement, review, test, finalize. Use when building a new custom module, adding a route/form/plugin, changing entity structure or schema, or any task touching more than a couple of files. Do NOT use for typo fixes, CSS tweaks, or single-line changes — use the tiny-fix skill instead. Each phase has an exit condition; do not move to the next phase until it is met.
中文简介正在准备中。当前显示原文说明。
Use for operational Drupal 11 workflows in DDEV environments, including safe updates, backup-first procedures, and troubleshooting commands.
中文简介正在准备中。当前显示原文说明。
當 Codex 任務需要依小型、中型、大型或 Goal 模式選擇正確 SKILL、逐階段重新路由,或尊重使用者指定 SKILL 與輔助能力同意時使用。
中文简介正在准备中。当前显示原文说明。
Use when rating whether a project, repo, skill, workflow, plugin, agent product or post uses TypeSafe's Jev (System One) model well -- "is this a good use of Jev?", "rate this Jev integration", "jevaluate <url>", or a link to something named after Jev; also when checking whether something that calls itself Jev actually uses it.
中文简介正在准备中。当前显示原文说明。
How to manually regenerate the compiled agentic workflow .lock.yml files when the gh-aw Version Check workflow reports version drift. All workflows track the newest github/gh-aw release or prerelease.
中文简介正在准备中。当前显示原文说明。
Reliable progress watching for long-running background commands (training runs, live audits, batch jobs, CI) without losing output to stdout buffering. Prefer post-completion cat-and-grep over tail -F.
中文简介正在准备中。当前显示原文说明。
GEODE evidence-first development workflow. Use for feature work, provider/model changes, GUI/computer-use work, PDF/document ingestion, observability/schema/event/state changes, verification planning, GitFlow merge prep, and requests to "follow the workflow" or "scaffold the process".
中文简介正在准备中。当前显示原文说明。
Monitor long-running GEODE work, CI, audits, and training without losing output to buffering or confusing a watcher with the underlying state authority.
中文简介正在准备中。当前显示原文说明。
Slack Gateway operations guide. Socket Mode credentials, config.toml bindings, serve restart, receiver debugging, reaction behavior. Triggers on "serve", "gateway", "slack", "바인딩", "binding", "소켓", "socket", "폴러", "poller", "config.toml".
中文简介正在准备中。当前显示原文说明。
Diagnose and repair a failed GEODE smoke workflow within the requested acceptance criteria. Preserve failed evidence, verify the shared root cause, and apply merge, rebuild, or live rerun stages only when authorized.
中文简介正在准备中。当前显示原文说明。
ユーザーと対話しながら機能仕様を策定し、Notion に自動でドキュメント化するスキル。「仕様を作ろう」「スペックを書いて」「仕様を詰めよう」などの指示で呼び出される。
中文简介正在准备中。当前显示原文说明。
Runs the full implement-and-commit loop over a task list — selects the next incomplete sub-task, implements it, runs linters and tests, marks it done, commits, and repeats until the list is finished. Use when asked to work through a feature's task list at .ai/[feature]/tasks.md unattended, or to keep going until every sub-task is complete. For a single sub-task with no commit, use task-implementation; to stop for approval between each one, use iterative-development.
中文简介正在准备中。当前显示原文说明。
Implements one numbered sub-task from a task list at .ai/[feature]/tasks.md, running linters and tests, without staging, committing, or marking the task complete. Use when asked to carry out a specific sub-task by number, or as the inner step of a larger loop that handles commits separately. For the full loop including commits, use task-orchestration.
中文简介正在准备中。当前显示原文说明。
Turns an existing Product Requirements Prompt at .ai/[feature]/prp.md into a step-by-step task list of parent tasks and sub-tasks, saved to .ai/[feature]/tasks.md and committed. Use when a PRP is ready to be broken down into implementable work, or when planning how a feature will be built before any implementation starts. To write the PRP itself first, use prp- generation.
中文简介正在准备中。当前显示原文说明。