Pencil Renderer

Render DNA codes to Pencil .pen frames. Does ONE thing well. Input: DNA code + component type (hero, card, form, etc.) Output: .pen frame ID + screenshot Use when: design-exploration or other orchestrators need to render visual proposals using Pencil MCP backend.

This skill appears to do exactly what it says: translate DNA codes into Pencil frames using the Pencil MCP backend. Before installing, confirm that your platform's MCP integration is trusted and that any credentials for Pencil MCP are managed by the platform (not this skill). Note that MCP-side operations may include AI image generation (G(..., "ai", ...)) and creating/storing .pen files/screenshots — consider whether those outputs may be visible to other users or logs in your environment. If you rely on sensitive or proprietary DNA inputs, ensure the MCP service's data handling/privacy policies meet your requirements. No environment variables or local installs are required by the skill itself.

Type: OpenClaw Skill Name: pencil-renderer Version: 0.1.2 The skill is classified as suspicious due to the `G()` function in `references/batch-design-patterns.md` and `references/dna-to-pencil.md`. This function allows the agent to generate or retrieve images from external AI or stock services using user-provided prompts and keywords. While plausibly needed for the skill's stated purpose of rendering visual proposals, this represents a risky capability involving external network calls and potential for prompt injection against third-party services (e.g., for resource exhaustion, inappropriate content generation, or other abuses), even if no malicious intent is evident in the provided examples. The `SKILL.md` itself does not contain malicious prompt injection against the OpenClaw agent.