Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a release or ship recap into a social pack: posts per platform where every claim traces to a facts file, clip cut-downs per aspect ratio cut with ffmpeg and checked with ffprobe, hand-off for publishing only after GO. Use for "social pack for the release", "posts and clips for this launch", "announce the release".
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Part of pb-content-studio (step f: social pack). What you get: posts per platform and clip cut-downs from your release recap, every claim traceable to a fact, handed off for publishing after your GO.
test -d ~/.claude/skills/content-engine; absent → log "content-engine not installed: copywriting fallback" and continue. With launch_video: command -v ffmpeg and command -v ffprobe; either missing → stop with "Missing tool: <name>. Install ffmpeg and rerun." and write nothing except the run log — probes answeredsocial/<slug>/facts.md, one numbered fact per line with its source line in the recap; no fact without a source — file writtensocial/<slug>/posts.md per platform, each claim tagged [F<n>] — every claim has a tag that exists in facts.md — stops for approvalsocial/<slug>/clips/<name>_<WxH>.mp4 per format and per requested cut, for example ffmpeg -ss <start> -t <seconds> -i <video> -vf "scale=<W>:<H>:force_original_aspect_ratio=increase,crop=<W>:<H>" -c:a copy <out>, then ffprobe -v error -select_streams v:0 -show_entries stream=width,height -of csv=p=0 <out> — ffprobe equals the asked WxH for every clip; on a mismatch stop with "clip <file> has WxH, expected ...", do not publishsocial/<slug>/publish.md; upload is manual unless the human named a tool in step 2 — hand-off file writtenRun log: production_artifacts/pb-social-pack-<date>.md in the start directory, never committed
auto-editor --version. If the binary is missing or errors, log "auto-editor not installed: silence-cut skipped" and continue — the step never fails the run.auto-editor <launch_video> -o <out.mp4> before the ffmpeg cut-downs in step 5; the cut-downs then take the silence-cut file as input.pip install auto-editor) is a manual opt-in step for the user — never pip-install it as part of this playbook.Rules
N. done|skipped|failed — artifact — check result) and WAITING FOR GO: <step> at each gate.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。