Add Figma agent skills for the Figma MCP server - #871
Closed
danbarr wants to merge 1 commit into
Closed
Conversation
Package all 12 skills from figma/mcp-server-guide (figma-use and its mode-specific companions, figma-generate-design/library/diagram, figma-code-connect, figma-create-new-file, figma-design-to-code, figma-implement-motion, figma-swiftui, figma-use-figjam/motion/slides) at commit 22b2c566d98880ebdb5a8e48eb2c66c596a6d990. Names already carry a figma- prefix upstream, so no additional namespacing was needed. spec.version starts at 0.1.0 per Dockyard's versioning policy. The upstream repo declares no OSS license; the README states usage of the Figma MCP server and these skills is governed by the Figma Developer Terms (https://www.figma.com/legal/developer-terms/), which is reflected in spec.yaml comments and the MANIFEST_MISSING_LICENSE allowlist reason rather than treated as an SPDX license gap. security.allowed_issues entries triage the false positives surfaced by skill-scanner, several distinct from prior batches given these skills' heavy MANDATORY/MUST/NEVER imperative style and JS/Swift code examples: agent-directed workflow instructions read by the scanner as authority-claiming/injected text, backtick-quoted inline code misread as shell subshell substitution, and one coincidental substring match against an unrelated CVE signature. Source: https://github.com/figma/mcp-server-guide Signed-off-by: Dan Barr <6922515+danbarr@users.noreply.github.com>
Contributor
🛡️ Skill Security Scan Results✅ figma-code-connect
✅ figma-create-new-file
✅ figma-design-to-code
✅ figma-generate-design
✅ figma-generate-diagram
✅ figma-generate-library
✅ figma-implement-motion
✅ figma-swiftui
✅ figma-use
✅ figma-use-figjam
✅ figma-use-motion
✅ figma-use-slides
Summary: Scanned 12 skill(s), all passed security checks. ✅ |
Contributor
Author
|
Closing due to licensing uncertainty. The upstream Figma skills do not declare an OSS license, and the Figma Developer Terms grant limited access and use rights but do not expressly permit third-party repackaging or public redistribution. We should only publish these artifacts after receiving explicit permission from Figma or an applicable redistribution license. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
figma-useand its mode-specific companionsfigma-use-figjam/figma-use-motion/figma-use-slides,figma-generate-design/figma-generate-library/figma-generate-diagram,figma-code-connect,figma-create-new-file,figma-design-to-code,figma-implement-motion,figma-swiftui) at commit22b2c566d98880ebdb5a8e48eb2c66c596a6d990.figma-prefix upstream, so no additional namespacing was needed (no collisions with the existing catalog).spec.versionstarts at0.1.0for all 12, per Dockyard's own-your-semver policy.spec.yaml's header comment and itsMANIFEST_MISSING_LICENSEallowlist reason rather than treated like a missing-SPDX-field gap.security.allowed_issuesentries triage the false positives surfaced byskill-scanner. This batch skewed differently from prior ones (HashiCorp, Datadog) because these skills are written in a heavy MANDATORY/MUST/NEVER imperative style with first-party "instruction to the agent" language and lots of JS/Swift code — several findings were the scanner reading the skill's own workflow instructions as authority-claiming/injected text, backtick-quoted inline code misread as shell subshell substitution, and one coincidental substring match against an unrelated CVE signature for a different MCP server package. Each was manually verified against the actual upstream source before allowlisting.Test plan
dockhand validate-skillpasses for all 12 spec.yaml filestask scan-skillpasses cleanly (no unallowlisted findings) for all 12dockhand build-skillbuilt successfully for a sample skill (figma-use)