What problem does it solve?
Plain markdown responses are a poor fit for structured interactions like approvals, choices, and forms in a chat UI. This Skill provides the payload shape, authoring rules, and reusable templates needed to emit Adaptive Cards that the PiClaw web runtime can render and act on.
Core Features & Use Cases
- Payload Specification: Defines the exact
adaptive_card content block format PiClaw supports, including schema version 1.5, card states, and supported actions (Action.Submit, Action.OpenUrl).
- Reusable Templates: Ships five ready-made card patterns covering approvals, choices, links, status receipts, and keep-active forms.
- Prompt Patterns: Provides copy-paste prompt templates that constrain an agent to emit exactly one valid card with a concise fallback message.
- Use Case: When an agent needs user sign-off before deploying changes, it can post an approval card with Approve, Reject, and Revise buttons instead of asking the user to type a reply.
Quick Start
Ask the agent to return a PiClaw-compatible approval Adaptive Card with one concise fallback message and a single adaptive_card content block using schema version 1.5.