adaptive-cards-authoring

Author Adaptive Card payloads for structured web interactions in the PiClaw runtime.

847|79|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/rcarmo/piclaw --skill adaptive-cards-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adaptive-cards-authoring
Source: https://github.com/rcarmo/piclaw/tree/main/skel/.pi/skills/adaptive-cards-authoring
Command: npx skills add https://github.com/rcarmo/piclaw --skill adaptive-cards-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about adaptive-cards-authoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an Adaptive Card for an approval workflow?

Emit one adaptive_card content block with schema_version 1.5, a short fallback_text, and Action.Submit buttons carrying decision data such as approve, reject, or revise. The templates.md file includes a complete approval card example you can adapt.

What Adaptive Card actions does PiClaw support?

PiClaw currently supports Action.Submit for structured decisions and Action.OpenUrl for external links. Action.ShowCard, Action.ToggleVisibility, and complex refresh or auth flows are not supported unless you extend core support yourself.

Which Adaptive Card schema version should I use?

Use schema version 1.5 for both the top-level schema_version field and the payload version. The authoring rules recommend staying on 1.5 unless there is a specific reason to change it.

When should I use markdown instead of an Adaptive Card?

Use markdown when the interaction is long-form, when the action semantics are not supported by the runtime, or when a card would be denser than plain text. Cards are best for approvals, short choices, and compact structured data capture.

How do I keep an Adaptive Card active after submission?

Set submit_behavior to keep_active on the content block so the card remains interactive after each submission. This pattern suits iterative forms where users submit values repeatedly without the card locking into a completed state.