Penpot Clojure Wrap

Problem

Penpot Wrap addresses manual wrapping, repeated setup, and fragmented GitHub workflows around Penpot. When engineers need to fold Penpot assets, scripts, or automation steps into a repeatable process, ad-hoc commands and unclear ownership make verification, sync, and handoff slower. The skill centers on wrap as a key concept: turning scattered operations into a reusable, inspectable unit instead of throwaway scripts.

How It Works

Based on the name, tags, and SKILL.md signals, it is positioned in dev-programming and likely connects Penpot, Clojure, and GitHub. Expected capabilities include:
- Wrapping repeated actions into a single entry point.
- Clojure-side integration where scripts or tooling need a stable call surface.
- GitHub context for keeping changes traceable across repos, branches, or automation tasks.

A typical flow starts by identifying the target to wrap, then fixing inputs, execution steps, and output expectations, and finally preserving the change path through GitHub workflows.

Boundaries

The available material does not detail Penpot APIs, permission models, Webhooks, deployment targets, or private integrations. It should not be assumed to be a full Penpot system integrator. It is better suited for small teams experimenting with Penpot automation, Clojure script wrapping, or GitHub task flow. Before production use, verify the repository code, configuration surface, and required permissions.