skills/pencil-skills/pencil-mcp-get-variables/SKILL.md
Read design token variables (colors, fonts, spacing) from a Pencil .pen file via the get_variables MCP tool. Use when the user explicitly mentions Pencil and needs to list design tokens, check the current theme, or retrieve variable IDs for use in batch_design operations.
npx skillsauth add partme-ai/full-stack-skills pencil-mcp-get-variablesInstall 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_variablesIf your client namespaces MCP tools, it may appear as mcp__pencil__get_variables.
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 variables" might refer to environment variables or code variables).
CRITICAL PREREQUISITE: You must ONLY use this skill when the user EXPLICITLY mentions "Pencil".
ALWAYS use this skill when:
primary-color) instead of hardcoded hex codes.Trigger phrases include:
filePath (string, optional): Path to the .pen file.get_variables().batch_design operations (e.g., fill: { type: "var", id: "var_123" }).Retrieve all variables defined in the current document.
{}
Read variables from a different design file (e.g., a shared library).
{
"filePath": "/Users/design/system/tokens.pen"
}
Same as simple, but used when auditing themes.
{}
English keywords: get variables, read tokens, design system, theme values, color palette, typography tokens
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.