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.

261 stars

bypartme-ai

View on GitHub Installation ↓

Best use case

pencil-mcp-get-screenshot is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. 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.

Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.

Practical example

Example input

Use the "pencil-mcp-get-screenshot" skill to help with this workflow task. Context: 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.

Example output

A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.

When to use this skill

Use this skill when you want a reusable workflow rather than writing the same prompt again and again.

When not to use this skill

Do not use this when you only need a one-off answer and do not need a reusable workflow.
Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/pencil-mcp-get-screenshot/SKILL.md --create-dirs "https://raw.githubusercontent.com/partme-ai/full-stack-skills/main/skills/pencil-skills/pencil-mcp-get-screenshot/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/pencil-mcp-get-screenshot/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How pencil-mcp-get-screenshot Compares

Feature / Agent	pencil-mcp-get-screenshot	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

AI Agents for Coding

Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.

SKILL.md Source

## 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**:
1.  Is the user explicitly asking to use "Pencil"?
2.  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

1.  **Identify Target**: Get the `nodeId` of the element you just modified or created.
2.  **Call Tool**: `get_screenshot(nodeId='...')`.
3.  **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](examples/1-node-screenshot.json).

### 2. Medium: Frame Verification
Screenshot a whole frame to check layout and composition.
See [2-frame-verification.json](examples/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](examples/3-component-check.json).

## Keywords

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

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

Related Skills

pencil

261

from partme-ai/full-stack-skills

用于通过 Pencil MCP 读取/修改 .pen 设计文件并校验布局。用户提到 pencil/.pen/设计稿编辑、需要列出工具或执行 batch_get/batch_design 时调用。

pencil-ui-designer

261

from partme-ai/full-stack-skills

Orchestrates Pencil design system initialization by routing framework requests to the correct pencil-ui-design-system-* skill. Use when the user explicitly mentions Pencil and wants to initialize a design system (antd, Bootstrap, Element Plus, Layui, uView, Vant, uCharts, ECharts), set up component libraries, or create design tokens in a .pen file.

pencil-ui-design-system-vant

261

from partme-ai/full-stack-skills

Initialize Vant 4 design tokens and component overview frames in a Pencil .pen file. Use when the user mentions Pencil with Vant or Vant 4, needs to set up Vant color palette and typography variables, or wants to create component library frames for Button, Cell, Form, Dialog, and other Vant components.

pencil-ui-design-system-uviewpro

261

from partme-ai/full-stack-skills

Initialize uView Pro design tokens and component overview frames in a Pencil .pen file. Use when the user mentions Pencil with uView Pro or uviewpro, needs to set up uView Pro color palette and typography variables, or wants to create component library frames for Button, Form, Tabs, Navbar, and other uView Pro components.

pencil-ui-design-system-uview

261

from partme-ai/full-stack-skills

Initialize uView 2.x design tokens and component overview frames in a Pencil .pen file. Use when the user mentions Pencil with uView 2.x (not uView Pro), needs to set up uView color palette and typography variables, or wants to create component library frames for Button, Form, Cell, Tabs, and other uView components.

pencil-ui-design-system-ucharts

261

from partme-ai/full-stack-skills

Initialize uCharts chart theme tokens and data visualization placeholder frames in a Pencil .pen file. Use when the user mentions Pencil with uCharts or qiun-data-charts, needs to set up chart series colors and axis tokens, or wants to create placeholder frames for Line, Bar, Pie, Radar, and other uCharts chart types.

pencil-ui-design-system-layui

261

from partme-ai/full-stack-skills

Initialize Layui design tokens and component overview frames in a Pencil .pen file. Use when the user mentions Pencil with Layui or layui-vue, needs to set up Layui color palette and typography variables, or wants to create component library frames for Button, Table, Form, Menu, and other Layui components.

pencil-ui-design-system-element

261

from partme-ai/full-stack-skills

Initialize Element Plus design tokens and component overview frames in a Pencil .pen file. Use when the user mentions Pencil with Element Plus or Element UI, needs to set up Element color palette and typography variables, or wants to create component library frames for Button, Table, Form, Dialog, and other Element components.

pencil-ui-design-system-echarts

261

from partme-ai/full-stack-skills

Initialize ECharts chart theme tokens and data visualization placeholder frames in a Pencil .pen file. Use when the user mentions Pencil with ECharts, needs to set up chart color palette and axis tokens, or wants to create placeholder frames for Line, Bar, Pie, Radar, and other ECharts chart types.

pencil-ui-design-system-bootstrap

261

from partme-ai/full-stack-skills

Initialize Bootstrap design tokens and component overview frames in a Pencil .pen file. Use when the user mentions Pencil with Bootstrap, needs to set up Bootstrap color palette and typography variables, or wants to create component library frames for Grid, Card, Modal, Navbar, and other Bootstrap components.

pencil-ui-design-system-antd

261

from partme-ai/full-stack-skills

Initialize Ant Design (antd) design tokens and component overview frames in a Pencil .pen file. Use when the user mentions Pencil with Ant Design or antd, needs to set up antd color palette and typography variables, or wants to create component library frames for Button, Form, Table, Modal, and other antd components.

pencil-ui-design-spec-generator

261

from partme-ai/full-stack-skills

Translates high-level user requirements into a PENCIL_PLAN: a strict sequence of Pencil MCP tool calls (open_document, set_variables, batch_design, get_screenshot). Use when the user explicitly mentions Pencil and wants to plan a design task, generate a step-by-step design spec, or create a login form, dashboard, or design system initialization plan.