AI SummaryReference documentation for Prismatic platform operations and the standardized API access hierarchy. Prismatic API access follows a two-tier priority system for interactive agents (e.g., Orby). Builder agents (cni-builder, component-builder) use their own script-based pipelines and should not use MC
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "prismatic-api" skill in my project. Please run this command in my terminal: # Install skill into your project mkdir -p .claude/skills/prismatic-api && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/prismatic-api/SKILL.md "https://raw.githubusercontent.com/prismatic-io/prismatic-skills/main/skills/prismatic-api/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Prismatic API access patterns and GraphQL reference. Covers the two-tier access hierarchy (MCP tools → Prism CLI), CLI usage rules, GraphQL query patterns, pagination, authentication, and managing platform resources programmatically.
Priority 1: MCP Tools (Interactive Agents Only)
Use MCP tools when operating within an interactive agent conversation (e.g., Orby). These handle auth, retries, and output formatting automatically. | MCP Tool | Operation | |----------|-----------| | mcp__plugin_prismatic-skills_prism__prism_me | Check auth / user profile | | mcp__plugin_prismatic-skills_prism__prism_components_list | List / search components | | mcp__plugin_prismatic-skills_prism__prism_components_init | Initialize new component | | mcp__plugin_prismatic-skills_prism__prism_components_publish | Publish component | | mcp__plugin_prismatic-skills_prism__prism_components_generate_manifest | Generate component manifest | | mcp__plugin_prismatic-skills_prism__prism_integrations_list | List / search integrations | | mcp__plugin_prismatic-skills_prism__prism_integrations_init | Initialize new CNI | | mcp__plugin_prismatic-skills_prism__prism_integrations_import | Import / update CNI | | mcp__plugin_prismatic-skills_prism__prism_integrations_convert | Convert YAML to CNI | | mcp__plugin_prismatic-skills_prism__prism_integrations_flows_list | List flows for integration | | mcp__plugin_prismatic-skills_prism__prism_integrations_flows_test | Test a flow | | mcp__plugin_prismatic-skills_prism__prism_integrations_flows_listen | Listen for webhook payloads | | mcp__plugin_prismatic-skills_prism__prism_integrations_generate_flow | Generate flow boilerplate | | mcp__plugin_prismatic-skills_prism__prism_integrations_generate_config_page | Generate config page | | mcp__plugin_prismatic-skills_prism__prism_integrations_generate_config_var | Generate config variable | | mcp__plugin_prismatic-skills_prism__prism_integrations_add_connection_config_var | Add connection config var | | mcp__plugin_prismatic-skills_prism__prism_integrations_add_datasource_config_var | Add datasource config var | | mcp__plugin_prismatic-skills_prism__prism_install_component_manifest | Install component manifest in CNI | | mcp__plugin_prismatic-skills_prism__prism_install_legacy_component_manifest | Legacy manifest install |
CLI Usage Rules
• prism must be installed globally (npm install -g @prismatic-io/prism) — never use npx prism • All list commands: always use --extended --output json • --extended and --columns are mutually exclusive — always prefer --extended • For graphql:query: always use --variables flag, never string interpolation • Auth is handled by the CLI — no custom token exchange needed
Prismatic API
Reference documentation for Prismatic platform operations and the standardized API access hierarchy.
API Access Method Hierarchy
Prismatic API access follows a two-tier priority system for interactive agents (e.g., Orby). Builder agents (cni-builder, component-builder) use their own script-based pipelines and should not use MCP tools directly — see their agent docs for details.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster