Agent skill
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 this agent skill to your Project
npx add-skill https://github.com/partme-ai/full-stack-skills/tree/main/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.penfile.nodeId(string, required): The ID of the node to screenshot.
How to use this skill
- Identify Target: Get the
nodeIdof 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 (中文关键词): 获取截图, 视觉验证, 检查设计, 查看节点, 渲染图片, 视觉审计
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
ocrmypdf-batch
OCRmyPDF batch processing skill — process multiple PDFs, Docker automation, shell scripting, and CI/CD integration. Use when the user needs to OCR many PDFs, set up automated OCR pipelines, or integrate OCR into workflows.
ocrmypdf-optimize
OCRmyPDF optimization skill — compress PDFs, configure PDF/A output, JBIG2 encoding, and lossless optimization. Use when the user needs to reduce PDF file size, create archival PDF/A files, or optimize OCR output.
ocrmypdf-image
OCRmyPDF image processing skill — deskew, rotate, clean, despeckle, remove border from scanned documents. Use when the user needs to improve scanned PDF quality, fix skewed pages, remove noise, or clean up scanned documents before OCR.
ocrmypdf-api
OCRmyPDF Python API and plugin skill — use OCRmyPDF programmatically from Python, integrate with applications, and extend with plugins (EasyOCR, PaddleOCR, AppleOCR). Use when the user needs to call OCRmyPDF from Python code, build OCR pipelines, or use alternative OCR engines.
ocrmypdf
OCRmyPDF core skill — add searchable OCR text layer to scanned PDFs, convert images to searchable PDFs, support 100+ languages via Tesseract. Use when the user needs to OCR a PDF, make a scanned PDF searchable, or extract text from scanned documents.
svelte
Guides Svelte and SvelteKit development including reactive components, stores, transitions, lifecycle hooks, SSR, file-based routing, and deployment. Use when the user needs to build Svelte components, create SvelteKit applications, implement reactivity patterns, or configure Svelte with Vite.
Didn't find tool you were looking for?