Loading...
Loading...
Found 35 Skills
Strict parser and validator for Workbench closeout comments, verdict/status discipline, PR reference types, and cross-issue REMAINING sync.
Specification-driven development from raw requirement to product design, technical design, task list, execution, and verification.
Post-change documentation sync for decisions, synthesis, skill maps, release notes, and durable handoffs.
Findings-first review discipline for code, diffs, task plans, live workflow changes, and implementation evidence.
Goal-persistence execution wrapper for autonomous work that must continue across turns until the stated objective is actually satisfied.
Browser verification, proof screenshots, traces, console and network checks, and reproducible UI evidence for Workbench QA.
Source-first, self-loop resistant guardrails for Capy GitHub dialogue responders before any write-capable PR, issue, or review action.
PASS, FLAG, and BLOCK review discipline for workflow review, QA verification, release checks, and issue closeout.
Two-layer autonomous conductor — design loop produces decision packets, dispatch loop routes to bounded issues with dedupe/cooldown/archive controls. Replaces v1's single-agent persistence with a durable control loop that stops only at real blockers.
Compact context, cache-aware execution, scoped evidence reads, and role-specific skill attachment discipline.
Comprehensive reference for LINE Messaging API — webhook setup, message sending, Flex Message design, Rich Menu management, audience targeting, insights, coupons, and channel access tokens. This skill should be used when the user asks to "build a LINE Bot", "set up a webhook", "send a push message", "design a Flex Message", "create a Rich Menu", "manage audience targeting", "get messaging insights", "create a coupon campaign", "debug webhook signature verification", or mentions LINE Messaging API, LINE OA chatbot, reply/push/multicast/narrowcast/broadcast, Flex Message JSON, Rich Menu, group chat bot, channel access token, or URL schemes. Always use this skill whenever the user mentions LINE bots, chatbots, LINE OA, or any messaging-related LINE integration, even if they don't explicitly say "Messaging API".