Full-stack-skills pencil-mcp-get-screenshot

Capture a visual screenshot of a specific node in a Pencil .pen file via the get_screenshot MCP tool. Use when the user explicitly mentions Pencil and needs to visually verify a design operation, check for alignment or spacing issues, or review a component after batch_design changes.

install

source · Clone the upstream repo

git clone https://github.com/partme-ai/full-stack-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/partme-ai/full-stack-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/pencil-skills/pencil-mcp-get-screenshot" ~/.claude/skills/partme-ai-full-stack-skills-pencil-mcp-get-screenshot && rm -rf "$T"

manifest: skills/pencil-skills/pencil-mcp-get-screenshot/SKILL.md

Tools

This skill is designed to call the Pencil MCP tool:

```
get_screenshot
```

If your client namespaces MCP tools, it may appear as

mcp__pencil__get_screenshot

When to use this skill

Intent Recognition (CRITICAL)

Even if a trigger phrase matches, you must verify the user's intent:

Is the user explicitly asking to use "Pencil"?
Is the current conversation context clearly about "Pencil" design tasks?

If the answer is NO, do NOT use this skill. (e.g., "Get screenshot" might refer to a browser screenshot via Puppeteer).

CRITICAL PREREQUISITE: You must ONLY use this skill when the user EXPLICITLY mentions "Pencil".

ALWAYS use this skill when:

You have completed a design operation (
```
batch_design
```
) and need to verify the result in Pencil.
The user asks to "Show me" or "Take a look" at the Pencil design.
You need to check for visual bugs (text overflow, alignment, contrast).
This is the Verify step in the Design Loop.

Trigger phrases include:

"Get Pencil screenshot" (获取 Pencil 截图)
"Pencil visual check" (Pencil 视觉检查)
"Verify Pencil design" (验证 Pencil 设计)
"Show me the button in Pencil" (给我看 Pencil 里的那个按钮)

Input Parameters

filePath
(string, optional): Path to access a specific
```
.pen
```
file.
nodeId
(string, required): The ID of the node to screenshot.

How to use this skill

Identify Target: Get the
```
nodeId
```
of the element you just modified or created.
Call Tool:
```
get_screenshot(nodeId='...')
```
.
Analyze Result:
- The tool returns an image URL or data.
- CRITICAL: You must "look" at the image (if capabilities allow) or present it to the user for feedback.
- Check for: Alignment, Spacing, Text Truncation, Color correctness.

Examples

1. Simple: Node Screenshot

Get a visual verification of a single element. See 1-node-screenshot.json.

2. Medium: Frame Verification

Screenshot a whole frame to check layout and composition. See 2-frame-verification.json.

3. Complex: Design System Check

Screenshot a component master to ensure the design system update looks correct. See 3-component-check.json.

Keywords

English keywords: get screenshot, visual verification, check design, view node, render image, visual audit

Chinese keywords (中文关键词): 获取截图, 视觉验证, 检查设计, 查看节点, 渲染图片, 视觉审计