Loading...
Loading...
Found 196 Skills
Buddy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Buddy data.
Decomposition playbook + anti-temptation rules for an orchestrator profile routing work through Kanban. The "don't do the work yourself" rule and the basic lifecycle are auto-injected into every kanban worker's system prompt; this skill is the deeper playbook when you're specifically playing the orchestrator role.
Structured clarification and requirements gathering through focused dialogue. Use when a task is ambiguous, underspecified, or requires user input before any action can be taken. Do not plan or implement anything—only ask questions to collect the information needed. Triggers on: 'ask me', 'ask questions about', 'clarify requirements', 'gather requirements', 'I need you to ask', or when the user explicitly wants a question-and-answer session before work begins.
Knowledge comics (知识漫画): educational, biography, tutorial.
When developing new features, follow this sub-process — take the vague idea of "add X capability" through to the acceptance closure, with solution documents archived so that both AI and users can later check the original thinking and decision rationale. Trigger scenarios are focused on adding new capabilities ("develop new feature", "add X", "implement XX"), and do not handle bugs in existing code. This skill only acts as a router, deciding which sub-skill to trigger next among brainstorm / design / fastforward / implement / acceptance based on existing artifacts.
Radar integration. Manage Organizations. Use when the user wants to interact with Radar data.
Generate or update CLAUDE.md from blueprint artifacts. Use when adding team instructions, converting inline content to @imports, or setting up CLAUDE.local.md.
プラットフォーム利用者（acomo 上でワークフローモデルを使って開発する開発者）向け。 acomo CLI および公開 API の標準的な使い方（モデル取得・プロセス操作・認証）を案内する。 acomo 本体の内部実装は対象外。 acomo CLI を使うとき、ワークフローやプロセスの操作・モデル定義の確認を行うときに参照する。
Send a message through Sent or retrieve a message and its activity history with the Sent MCP tools. Use for direct message operations and lifecycle checks; use messaging-performance-analyzer for aggregate delivery diagnosis.
Searches for and retrieves existing visual media (images, logos, icons, photos, graphics, banners, thumbnails, hero images, backgrounds) from sources such as Salesforce CMS, Data 360 or any other source. Use this skill ANY TIME a user request involves finding, searching, getting, fetching, retrieving, grab, looking up, locating media. NEVER call search_media_cms_channels, search_electronic_media tools directly — always go through this skill first. This skill must be activated before any tool is used for media search or retrieval, without exception. Takes PRIORITY and activates FIRST when ANY media search/retrieval is mentioned, regardless of what else happens with the media afterward. Triggers for requests like "search for logo", "find hero image", "get company logo", "locate icons", "fetch background image", "retrieve product photos". Handles the search and source selection workflow. Does not apply when the request is about brand search, to generate NEW images with AI, or edit existing images.
How to work in a Knowledge Base project (the `knowledge-base` starter pack). Read when the project has the three-layer source-grounded layout — `external-sources/` → `research/` → `articles/` — or when asked how this project is organized. Carries the layer model, per-folder rules, status flows, and log discipline so this guidance does NOT live inside template bodies or log.md. The three procedures live elsewhere: ingest in the platform `open-knowledge` skill, research and consolidate as their own sibling skills in this pack. Complements the platform `open-knowledge` skill; does not replace it.
Analyzes article structure, identifies positions requiring visual aids, generates illustrations with Type × Style two-dimension approach. Use when user asks to "illustrate article", "add images", "generate images for article", or "为文章配图".