Agent skill · software engineering · paperclipai
create-issue-interaction-ui
Add a new Paperclip issue-thread interaction kind end-to-end. Use when repo work introduces or extends interaction cards like request_confirmation, checkbox confirmations, ask_user_questions, or suggest_tasks.
Why this skill is useful
Provides specific patterns and workflows for creating new interaction types in the Paperclip system that the AI wouldn't reliably generate on its own.
What it needs
About 7k tokens when loaded. Last updated 2026-08-07. 75,771 stars on the source repository.
What this skill does
Create a new issue-thread interaction UI (Developer/maintainer skill) Developer/maintainer skill. Do NOT install this on production Paperclip agents. This skill walks a Paperclip contributor through introducing a new issue-thread interaction kind from shared contract to issue-detail wiring, helpers, and docs. It is intentionally a developer/maintainer skill: the audience is a human or coding agent making code changes inside paperclipai/paperclip, not the operational agents that run inside a deployed Paperclip company. Do NOT install this on production Paperclip agents. This guide is for repository contributors changing Paperclip itself. When to use A new interaction kind is being introduced (compact picker, structured rating, in-thread approval card, etc.). An existing interaction needs a parallel variant with a distinct payload shape, validation, or resolution outcome (and askuserquestions is the wrong fit because option count, target binding, or result shape differs). A reviewer asks for "the same audit, staleness, supersede, and continuation semantics as the other interactions" on a new card. When NOT to use Adding fields to an existing interaction kind that does not need a new payload schema. Patch the existing validators/UI in place instead. Changing how Paperclip agents call interactions. Update skills/paperclip or references/api-reference.md; that is agent guidance, not card work. Building a non-thread UI (issue detail sidebar, project board widget, etc.). Those have their own component conventions. Mental model Every issue-thread interaction has four moving parts: Layer Owns -------------- --------------------------------------------------------------------------------------------------- Shared Kind constant, payload/result interfaces, Zod validators, exported types, shared-test coverage. Server Service create/accept/reject/respond, staleness, supersede, idempotency, activity log, wake send. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills paperclipai/create-issue-interaction-ui