Skill

pencil-mcp-get-screenshot

Captures a visual screenshot of a specific node in a Pencil .pen file via get_screenshot MCP tool. Use to verify design operations, check alignment or spacing issues, or review components after batch_design changes.

design

Install

npx claudepluginhub partme-ai/full-stack-skills --plugin t2ui-skills

Tool Access

This skill uses the workspace's default tool permissions.

Preview

This skill is designed to call the Pencil MCP tool:

Supporting Assets

LICENSE.txtexamples/1-node-screenshot.jsonexamples/2-frame-verification.jsonexamples/3-component-check.json

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

168.3k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

168.3k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

168.3k

Stats

Stars328

Forks62

Last CommitMar 25, 2026

Actions

View Source View Plugin View on GitHub View README

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 (中文关键词): 获取截图, 视觉验证, 检查设计, 查看节点, 渲染图片, 视觉审计