이메일, 캘린더, 할 일 관리, 자동화 (7.8천건)
Drafts legally compliant Notice of Annual Shareholders Meeting for US corporations, covering state-specific notice periods, record dates, quorum and voting thresholds, proxy procedures, and SEC Regulation 14A compliance for public companies. Use when preparing annual meeting notices, shareholder meeting notifications, or proxy notice and access mailings.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manages end-to-end workflow for multi-organization amicus coalition briefs in appellate courts. Covers single-pen drafting governance, position alignment, conflict resolution, documented sign-offs, FRAP 29/Rule 37.6 disclosures, FRAP 26.1 corporate disclosures, cover formatting for multiple amici, and compliant filing. Use when coordinating coalition amicus briefs, managing sign-offs, drafting joint friend-of-court briefs, handling multi-amici filing, or resolving inter-organization conflicts. Triggers on phrases like "coalition brief," "12 orgs joining this amicus," or "coordinate the amicus."
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drafts a Notice of Alibi Defense under Fed. R. Crim. P. 12.1 or state equivalents. Triggers on alibi notice drafting, alibi defense filing, Rule 12.1 disclosure, or pre-trial criminal defense notice tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Agent 专用邮箱统一管理：让 Claude Code、Codex 等平台的 Agent 用一套命令收发邮件、整理收件箱、分发任务。支持网易 ClawEmail（claw.163.com）和腾讯 Agent Mail（QQ 邮箱，agent.qq.com）两家后端，通过 MAIL_PROVIDER 切换。当用户提到收发邮件、看收件箱、搜索邮件、回复转发邮件、下载附件、整理邮件、给其他 Agent 派邮件任务、配置 Agent 邮箱、腾讯 QQ 邮箱 Agent、网易 ClawEmail 时使用此 skill。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
行政救济全流程AI技能。覆盖行政复议与行政诉讼的完整生命周期，从接案评估、受案范围判断、 被申请人适格性确认、行政行为分析、救济路径选择，到复议申请、证据整理、代理意见、 行政诉讼起诉、庭审准备、代理词撰写、二审再审、判决执行。 当用户涉及行政案件维权工作时触发，包括但不限于："帮我分析这个行政处罚能不能复议" "写行政复议申请书""这个案件走复议还是诉讼""确认被申请人是谁""写行政起诉状" "准备行政案件庭审""写行政诉讼代理词""申请停止执行行政行为""行政赔偿"等。 适用于各类行政案件（行政处罚、行政许可、行政强制、行政征收、行政确认、行政不作为、 政府信息公开等），只做申请人端（公民/企业/其他组织），不代理政府机关。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
End-to-end workflow for resolving one GitHub issue in dynamic-neural-field-composer - branch, TDD, build, review, docs, PR. Use when asked to fix, implement, or close a specific issue number.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scaffold new spell step commands and connectors. Use when building new step commands for spells or extending the spell engine with new capabilities. Connectors are for new I/O transport types OR platforms requiring complex multi-step interaction (e.g., browser-based automation).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Ticket system and work logs for context anchoring. Use when creating tickets, managing work logs, or anchoring context across multi-step tasks or sessions. Do NOT use for simple patches or single-step tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Activate when user expresses intent to start Sisyphus work (e.g., "okay then work like that", "let's execute this", "start working on this"). Extract ai-todolist.md content from GitHub comments/files, create branch, commit, and trigger GitHub Actions workflow. If no ai-todolist format found, load plan-writer skill instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Common Playwright automation patterns for web testing and scraping via MCP
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generic automated semantic versioning and release workflow. Handles version increments, git tagging, GitHub releases, and automated changelog generation for any repository.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Strategic planning consultant that produces decision-complete work plans through Socratic interview, codebase exploration, Metis gap analysis, and optional Momus high-accuracy review. MUST USE when the task has 5+ steps, scope is ambiguous, multiple modules are involved, or the user asks for a plan. Triggers: plan this, create a work plan, interview me, start planning, prometheustic, plan mode, help me plan this, break this down.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage the project's TODO list in .unikit/TODO.md — capture work to remember for later, not to do right now. Use it to add a deferred item, mark a todo complete, or show the list. The point is to park tasks you don't want to act on in the moment but don't want to forget. Trigger on "add a todo", "add this to the todo list", "put X on the todo list", "remind me to...", "don't forget to...", "note this for later", "we should do this later", "mark this todo done", "what's on the todo list", "what's left to do". This is only for parking reminders — to actually plan or do the work now, use /unikit-plan, /unikit-implement, or /unikit-devcontext.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write, open and — when allowed — merge a pull request for the current feature branch of a {{engine_name}} project, with or without a plan. Builds a plain-language PR text (one feature per line) from the plan's `## Modules` and task `WHY:` lines, or — without a plan — from the commits and the code changes themselves; pushes the current state (asking where to end when it stands inside a plan module), opens or updates the branch's single open PR through the GitHub MCP, and merges with a merge commit only when the merge brings nothing from the base branch. Levels: remind (text only), create, merge; capped by `git.pull_requests.max_level`. Trigger phrases: "pull request", "open a PR", "create PR", "PR description", "merge the PR". For commit messages use /unikit-commit; for reviewing a PR's code use /unikit-review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create conventional commit messages for {{engine_name}} projects by analyzing staged changes. Handles engine-specific concerns like companion file pairing, binary assets, and linking the related plan. ALWAYS use this skill when the user asks to commit, save changes, or create a commit. Trigger phrases include "commit", "create commit", "commit this", "save changes", "save my work". Even if the user simply says "commit" or asks you to commit after finishing a task — invoke this skill, do NOT commit manually via git.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute the tasks from an already-created feature plan in .unikit/code/plans/ — read the plan manifest (the PLAN.md file in the plan folder), work through the uncompleted tasks in order, write the code, mark progress, and resume across sessions. Supports selective runs by phase or by task numbers, and continuing from where the last session stopped. Use whenever a plan exists and the user wants to build it, e.g. "implement", "implement the plan", "start coding", "execute the plan", "run the plan", "do the next task", "implement phase 3", "implement tasks 2.1 and 2.3", "continue implementation", "continue where we left off", "keep going on the feature". To create the plan first, use the planning skill — this one carries an existing plan out.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
別の tmux ペインで動いている Claude Code インスタンスを、このセッションから tmux send-keys / capture-pane で駆動するオーケストレーション。プランモード投入 → プラン再点検 (1 回目の検証) → ユーザ承認ゲート → auto mode 実装 → レポート未記載追記 → レポート矛盾再チェック (2 回目の検証) の定型フロー。長時間タスクをもう 1 体の claude に「ダブルチェック付きで」実行させ、要所だけ自分が監督したいときに使う。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The GraphQL pipeline for Skmtc generators — authoring generators whose input schema is GraphQL SDL rather than OpenAPI. Covers `toGqlOperationEntry`, `GqlOperation`, `synthesizeArgsObject` (mutation args -> object schema), the GQL enrichment routing (`[id][rootKind][fieldName][variant]` — two nested subject keys where OAS has path+method), the `to<Lang>GqlOperationProjectionBase` companion factories, and the `GeneratorKey` shape `id|rootKind|fieldName|variant`. Use this skill ALONGSIDE `skmtc-generator` whenever the schema source is GraphQL SDL or the task mentions "GraphQL", "SDL", "GqlOperation", "toGqlOperationEntry", or GraphQL query/mutation generators. Engine rules (producers, register/insert, the axioms) stay in `skmtc-generator`; this skill carries only what differs for GraphQL.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Escalate a support ticket to a [Linear](https://composio.dev/toolkits/linear) issue and notify the team on [Slack](https://composio.dev/toolkits/slack).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Search the knowledge base in [Notion](https://composio.dev/toolkits/notion) for answers to customer questions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Process a refund request by gathering context and preparing the refund workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Send CSAT follow-up emails to customers after ticket resolution via [Gmail](https://composio.dev/toolkits/gmail)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identify churned or at-risk customers and draft personalized winback emails
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bulk verify customer email addresses using [Clearout](https://composio.dev/toolkits/clearout) or [Mailcheck](https://composio.dev/toolkits/mailcheck)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.