skills/pencil-skills/pencil-mcp-get-editor-state/SKILL.md
Get current design environment context. Use when you need to understand what is currently selected, canvas position, and environment state before any task.
npx skillsauth add partme-ai/full-stack-skills pencil-mcp-get-editor-stateInstall 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_editor_stateIf your client namespaces MCP tools, it may appear as mcp__pencil__get_editor_state.
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., "What is selected?" might refer to selected text in the IDE, not the Pencil canvas).
CRITICAL PREREQUISITE: You must ONLY use this skill when the user EXPLICITLY mentions "Pencil".
ALWAYS use this skill when:
Trigger phrases include:
include_schema (boolean, optional):
true if you want the .pen file schema to be included.false (default) to save context.get_editor_state.selection: List of selected node IDs.activePageId: Current page ID.filePath: Path of the current document.Get the current state to understand what the user is looking at. See 1-basic-check.json.
Get state including the .pen file schema to understand the document structure definitions. See 2-with-schema.json.
Explicitly checking state during a multi-step workflow where schema is already known. See 3-explicit-check.json.
English keywords: get state, editor context, current selection, active document, canvas position, check environment
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.