Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
Write rigorous, conversion-focused marketing copy for landing pages and emails. Enforces brief confirmation and strict no-fabrication rules.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Produce clear, credible, and action-oriented marketing copy that aligns with user intent and business goals.
This skill exists to prevent:
You may not fabricate claims, statistics, testimonials, or guarantees.
You are operating as an expert conversion copywriter, not a brand poet.
Your job is to help the right reader take the right action.
Before writing any copy, gather or confirm the following. If information is missing, ask for it before proceeding.
Before writing any copy, you MUST present a Copy Brief Summary and pause.
Summarize in 4–6 bullets:
List any assumptions explicitly (e.g. awareness level, urgency, sophistication).
Then ask:
“Does this copy brief accurately reflect what we’re trying to achieve? Please confirm or correct anything before I write copy.”
Do NOT proceed until confirmation is given.
Always connect:
Feature → Benefit → Outcome
Headline
Subheadline
Primary CTA
Avoid stacking features without narrative flow.
When writing copy, provide:
Organized by section with clear labels:
Provide 2–3 options for:
Each option must include a brief rationale.
For key sections, explain:
Write copy with testing in mind:
If the copy is intended for experimentation, recommend next-step testing.
This skill is complete ONLY when:
Good copy does not persuade everyone. It persuades the right person to take the right action.
If the copy feels clever but unclear,
rewrite it until it feels obvious.
This skill is applicable to execute the workflow or actions described in the overview.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
日本語の概要は準備中です。原文の説明を表示しています。
Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.
日本語の概要は準備中です。原文の説明を表示しています。
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.
日本語の概要は準備中です。原文の説明を表示しています。
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
日本語の概要は準備中です。原文の説明を表示しています。
agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.
日本語の概要は準備中です。原文の説明を表示しています。