スキルを探す

Use when configuring the outbound Send Email quick action in Lightning Case Feed — creating the action in Setup on Case (Action Type = Send Email), attaching a default Custom email template, setting predefined To/CC/BCC values, wiring QuickAction.QuickActionDefaultsHandler Apex defaults, respecting the Lightning Experience 10-file / 25 MB attachment limits, and letting agents move an email to a different case. Trigger keywords: Send Email quick action, case email composer, Email action missing from Case Feed, Don't Apply Template Subject, QuickActionDefaultsHandler, SendEmailQuickActionDefaults, move email to another case. NOT for Email-to-Case inbound routing, routing addresses, or thread-ID matching (use admin/email-to-case-configuration), NOT for authoring or migrating the templates themselves (use admin/email-templates-and-alerts and admin/classic-email-template-migration), and NOT for Apex Messaging.SingleEmailMessage sends outside Case Feed.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Generic automated semantic versioning and release workflow. Handles version increments, git tagging, GitHub releases, and automated changelog generation for any repository.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

AI Agile/Scrum Coach — sprint ceremony, velocity tracking, retrospective, team coaching รองรับทีม dev + non-dev

日本語の概要は準備中です。原文の説明を表示しています。

AI โปรดิวเซอร์เพลง — beat making, mixing/mastering brief, DAW workflow, artist direction รองรับทุก genre

日本語の概要は準備中です。原文の説明を表示しています。

Doc-first async culture — RFC, status update, async meeting alternative, decision log

日本語の概要は準備中です。原文の説明を表示しています。

AI Personal Knowledge Manager — Zettelkasten, Obsidian, PARA, Note-Taking System, Second Brain สำหรับนักเรียนรู้ตลอดชีวิต

日本語の概要は準備中です。原文の説明を表示しています。

AI ผู้จัดการเวลา — Pomodoro, Time Block, GTD, Deep Work, Calendar Design สำหรับผู้ที่อยากควบคุมเวลาได้จริง

日本語の概要は準備中です。原文の説明を表示しています。

AI ผู้ช่วยจัดการบ้าน — KonMari decluttering, minimalism, household schedule, maintenance calendar, inventory system

日本語の概要は準備中です。原文の説明を表示しています。

AI No-Code Automation Expert — Zapier, Make, n8n, workflow design, trigger/action, process automation สำหรับทุก business

日本語の概要は準備中です。原文の説明を表示しています。

จัดการ email แบบ inbox zero — triage, reply template, follow-up, scheduling, signature design

日本語の概要は準備中です。原文の説明を表示しています。

สรุป meeting แบบมืออาชีพ — agenda, decision log, action items (owner + due date), follow-up email

日本語の概要は準備中です。原文の説明を表示しています。

AI Executive Assistant — calendar, travel itinerary, expense, briefing doc, gatekeeping email

日本語の概要は準備中です。原文の説明を表示しています。

ออกแบบ Notion workspace — schema database, relation, automation, PARA method สำหรับ knowledge worker

日本語の概要は準備中です。原文の説明を表示しています。

Project plan ครบ — WBS, Gantt, sprint, retrospective, RAID log, stakeholder communication

日本語の概要は準備中です。原文の説明を表示しています。

แปลไทย-อังกฤษ (และอังกฤษ-ไทย) ที่ได้ใจความ ปรับ tone ท้องถิ่น พร้อม subtitle (.srt), email, เอกสารธุรกิจ

日本語の概要は準備中です。原文の説明を表示しています。

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).

日本語の概要は準備中です。原文の説明を表示しています。

Draft a customer support email reply based on ticket context.

日本語の概要は準備中です。原文の説明を表示しています。