Render a Commentary Form

Read as Markdown

Purpose: Implement Commentary Form renderers, bindings, and SDK bridges.

Use it when: Use when adding a native, static HTML, or custom Live Preview Form rendering path.

Install

Check out the published v0.6.2 tag of the Commentary Skills repository, then copy the complete skills/commentary-form-rendering/ folder into the skills directory for your compatible SKILL.md agent. Preserve references and metadata. Restart or refresh the harness if it loads skills at startup.

Invoke

Copy this request into a compatible agent:

Use `commentary-form-rendering` to add a customer-owned form renderer inside our existing Live Preview Review. Use the published Forms SDK bridge, preserve the Form Contract version, and return server validation errors to the participant.

Expected result: The agent returns renderer code and a test flow for the nonce/origin-bound bridge; no credential is included in the renderer.

Workflow

Choose native rendering, sanitized HTML bindings, or the Forms SDK bridge; preserve the contract id/version, submit structured values, and surface server validation diagnostics.

Environment and limits

Read the published v0.6.2 SKILL.md and its referenced files for the exact transport, scopes, target, and environment settings; those instructions are authoritative for this skill. For transport setup, see CLI, MCP, and Developer access. Never store credentials in the skill folder or send them to a renderer. Custom rendering requires an existing authorized Live Preview Review and the nonce-bound origin-aware bridge. Do not fetch renderer URLs server-side or execute renderer code inside Commentary.