skills/pencil-skills/pencil-mcp-batch-get/SKILL.md
Batch search and read node information. The Agent's 'Eyes'. Use to find specific components e.g. all nodes named 'Button' or get child structure within a container.
npx skillsauth add partme-ai/full-stack-skills pencil-mcp-batch-getInstall 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:
batch_getIf your client namespaces MCP tools, it may appear as mcp__pencil__batch_get.
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., if the user just says "Find the button" in a general context, they might mean simple text search or other tools).
CRITICAL PREREQUISITE: You must ONLY use this skill when the user EXPLICITLY mentions "Pencil".
ALWAYS use this skill when:
Trigger phrases include:
filePath (string, optional): Path to file.patterns (array, optional): Search patterns (e.g., ["name=Button"]).nodeIds (array, optional): Specific IDs to read.searchDepth (integer, optional): Depth for search.readDepth (integer, optional): Depth for reading children structure. Keep low (<3).includePathGeometry (boolean, optional): Include vector path data.resolveVariables (boolean, optional): Return computed values instead of variable refs.... (truncated children), make a new call with those specific child IDs.Get the top-level nodes of the document to understand the general structure. See 1-get-root.json.
Find all nodes that contain "Button" in their name. See 2-search-name.json.
Search for specific nodes by ID and name pattern, resolving variables to see actual values, and getting full geometry. See 3-detailed-search.json.
English keywords: batch get, search nodes, find elements, read properties, inspect structure, get components
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.