skills/pencil-skills/pencil-mcp-get-screenshot/SKILL.md
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.
npx skillsauth add partme-ai/full-stack-skills pencil-mcp-get-screenshotInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill is designed to call the Pencil MCP tool:
get_screenshotIf your client namespaces MCP tools, it may appear as mcp__pencil__get_screenshot.
Even if a trigger phrase matches, you must verify the user's intent:
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:
batch_design) and need to verify the result in Pencil.Trigger phrases include:
filePath (string, optional): Path to access a specific .pen file.nodeId (string, required): The ID of the node to screenshot.nodeId of the element you just modified or created.get_screenshot(nodeId='...').Get a visual verification of a single element. See 1-node-screenshot.json.
Screenshot a whole frame to check layout and composition. See 2-frame-verification.json.
Screenshot a component master to ensure the design system update looks correct. See 3-component-check.json.
English keywords: get screenshot, visual verification, check design, view node, render image, visual audit
Chinese keywords (中文关键词): 获取截图, 视觉验证, 检查设计, 查看节点, 渲染图片, 视觉审计
development
Provides per-component and per-API examples with cross-platform compatibility details for uni-app, covering built-in components, uni-ui components, and APIs (network, storage, device, UI, navigation, media). Use when the user needs official uni-app components or APIs, wants per-component examples with doc links, or needs platform compatibility checks.
tools
Creates new uni-app projects via the official CLI or HBuilderX with Vue 2/Vue 3 template selection, manifest.json and pages.json configuration, and directory structure setup. Use when the user wants to scaffold a new uni-app project, initialize project files with a single command, or set up the development environment.
tools
Browses, installs, configures, and manages plugins from the uni-app plugin market (ext.dcloud.net.cn) including component plugins, API plugins, and template plugins with dependency handling. Use when the user needs to find and install uni-app plugins, configure plugin settings, manage plugin dependencies, or integrate third-party components.
tools
Develops native Android and iOS plugins for uni-app including module creation, JavaScript-to-native communication, and plugin packaging for distribution. Use when the user needs to build custom native modules, extend uni-app with native capabilities (camera, Bluetooth, sensors), or create publishable native plugins.