Problem
Three skills cannot work outside an MCP or CLI install:
pipefy-toolkit-setup: it installs the MCP server and the CLI.pipefy-attachments: it uploads local files through file_path, and the presigned-URL path needs the client to do an HTTP PUT.pipefy-ipaas: the four meta-tools use the MCP's own HTTP gateway (packages/mcp/src/pipefy_mcp/core/ipaas_gateway.py). The SDK only mints the token.
A consumer has no field that tells it to skip them.
Proposal
Declare the surfaces in frontmatter. The Agent Skills specification already has compatibility, a free-text field of up to 500 characters. For a machine-readable list, use metadata.surfaces: "mcp cli". A skill with no surfaces value applies to every surface.
Document the field in skills/AGENTS.md, and validate its values in skills-lint.yml.
Non-breaking
Current readers ignore unknown frontmatter keys.
Problem
Three skills cannot work outside an MCP or CLI install:
pipefy-toolkit-setup: it installs the MCP server and the CLI.pipefy-attachments: it uploads local files throughfile_path, and the presigned-URL path needs the client to do an HTTP PUT.pipefy-ipaas: the four meta-tools use the MCP's own HTTP gateway (packages/mcp/src/pipefy_mcp/core/ipaas_gateway.py). The SDK only mints the token.A consumer has no field that tells it to skip them.
Proposal
Declare the surfaces in frontmatter. The Agent Skills specification already has
compatibility, a free-text field of up to 500 characters. For a machine-readable list, usemetadata.surfaces: "mcp cli". A skill with nosurfacesvalue applies to every surface.Document the field in
skills/AGENTS.md, and validate its values inskills-lint.yml.Non-breaking
Current readers ignore unknown frontmatter keys.