← Back to skills
extension
Category: AI Agent CapabilitiesAPI key requirement unconfirmed

Material-Agent-readiness-Eval

帮助设计师检查设计材料(包括figma组件库和markdow)是否已准备好交给 Agent 使用,并给出有依据、可验证的改进方案。

personAuthor: WenjiaWanghubModelScope

Material Agent-readiness Eval Skill

Use the workflows bundled inside this skill to assess and improve existing design-system materials. They are local resources, not separately installed skill dependencies.

Select the workflow

  • For a Figma component library, its Components, Variables, Properties, layout or publication readiness, read and follow Material Agent-readiness Eval Skill · Figma.
  • For preparing, auditing or improving a design-system Markdown contract, read and follow Material Agent-readiness Eval Skill · Markdown.
  • When both are requested, apply each workflow to its own evidence and keep their scores and conclusions separate. Reuse scope and purpose already confirmed by the user.
  • If the input does not identify the material to review, ask whether the user wants to work with a Figma library, Markdown documents, or both.

Read the selected workflow before assessing or modifying materials, then load its references as directed. Opening a bundled SKILL.md is sufficient; do not require the host to discover or invoke a second installed skill.

Environment and paths

Resolve this file's directory as the installed root. The Figma workflow root is skills/material-agent-readiness-eval-figma/; the Markdown workflow root is skills/material-agent-readiness-eval-markdown/, both relative to that installed root. In their instructions, <skill-root> and <this-skill> refer to the selected workflow's directory. Resolve its references/, assets/ and scripts/ from there, regardless of the current working directory or host product.

Before any Figma assessment, follow the bundled host setup. An authenticated official Figma MCP with callable use_figma is required. If missing, install/configure it through the current host's supported mechanism, complete OAuth and verify access first. If the host cannot support the connection or required tool, explain the limitation and stop the Figma workflow. Do not silently fall back to a read-only MCP.

Markdown-only work does not require Figma. Both report workflows require local file access and Node.js 18+; the optional Markdown scanner requires Python 3.10+. The repository's top-level maintenance scripts are not runtime dependencies.

Preserve the workflow contracts

Keep audits read-only. Follow the selected workflow's scope confirmation, evidence, scoring, approval and validation rules before making changes. Preserve Figma component identity and instance references; do not invent missing design decisions or claim external parity without evidence. Deliver the selected workflow's validated HTML report and state the remaining evidence or capability limitations.