Use this skill for any pencil.dev work, such as designing UI in a .pen file, editing an open Pencil canvas, sketching or mocking screens, instantiating components from a .lib.pen library, reading an existing design system from a .pen or .lib.pen file, fixing batch_design schema errors, or recovering from Pencil MCP host-not-connected issues. Pick it on any mention of pencil.dev, .pen, .lib.pen, "the Pencil MCP", "the Pencil canvas", or a design-system/ folder in a Pencil context, even when the user phrases it casually, mid-sentence, or doesn't name the tool. This is the canonical skill for all Pencil tasks; reach for it before any general design or frontend skill when Pencil signals are present.
$npx -y skills add nisus74/pencil-skill --skill pencil-designInstalls into the current project.
Run `npx skills use "https://github.com/nisus74/pencil-skill" --skill "nisus74/pencil-skill/pencil-design"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/nisus74/pencil-skill" that are relevant to the current task. Run `npx skills add "https://github.com/nisus74/pencil-skill"` and select the relevant skills, then follow their instructions.