@cubis/foundry 0.3.34 → 0.3.36

package/workflows/workflows/agent-environment-setup/platforms/windsurf/skills/skills_index.json

@@ -69,29 +69,6 @@
     "description": "Clarify requirements before implementing. Use when serious doubts arise.",
     "triggers": []
   },
-  {
-    "id": "atlassian-mcp",
-    "name": "atlassian-mcp",
-    "canonical_id": "atlassian-mcp",
-    "deprecated": false,
-    "replaced_by": null,
-    "path": ".windsurf/skills/atlassian-mcp/SKILL.md",
-    "description": "Use when querying Jira issues, searching Confluence pages, creating tickets, updating documentation, or integrating Atlassian tools via MCP protocol.",
-    "triggers": [
-      "Jira",
-      "Confluence",
-      "Atlassian",
-      "MCP",
-      "tickets",
-      "issues",
-      "wiki",
-      "JQL",
-      "CQL",
-      "sprint",
-      "backlog",
-      "project management"
-    ]
-  },
   {
     "id": "bash-linux",
     "name": "bash-linux",
@@ -122,16 +99,6 @@
     "description": "Socratic questioning protocol + user communication. MANDATORY for complex requests, new features, or unclear requirements. Includes progress reporting and error handling.",
     "triggers": []
   },
-  {
-    "id": "building-mcp-server-on-cloudflare",
-    "name": "building-mcp-server-on-cloudflare",
-    "canonical_id": "building-mcp-server-on-cloudflare",
-    "deprecated": false,
-    "replaced_by": null,
-    "path": ".windsurf/skills/building-mcp-server-on-cloudflare/SKILL.md",
-    "description": "Build and deploy remote MCP servers on Cloudflare Workers with tools, OAuth authentication, and production configuration.",
-    "triggers": []
-  },
   {
     "id": "changelog-generator",
     "name": "changelog-generator",
@@ -254,16 +221,6 @@
       "cache"
     ]
   },
-  {
-    "id": "datadog-automation",
-    "name": "datadog-automation",
-    "canonical_id": "datadog-automation",
-    "deprecated": false,
-    "replaced_by": null,
-    "path": ".windsurf/skills/datadog-automation/SKILL.md",
-    "description": "Automate Datadog tasks via Rube MCP (Composio): query metrics, search logs, manage monitors/dashboards, create events and downtimes. Always search tools first for current schemas.",
-    "triggers": []
-  },
   {
     "id": "debugging-wizard",
     "name": "debugging-wizard",
@@ -481,16 +438,6 @@
     "description": "Create conventional commits with intelligent staging and message generation",
     "triggers": []
   },
-  {
-    "id": "github-automation",
-    "name": "github-automation",
-    "canonical_id": "github-automation",
-    "deprecated": false,
-    "replaced_by": null,
-    "path": ".windsurf/skills/github-automation/SKILL.md",
-    "description": "Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically.",
-    "triggers": []
-  },
   {
     "id": "golang-pro",
     "name": "golang-pro",
@@ -610,35 +557,6 @@
     "description": "Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers: lint, format, check, validate, types, static analysis.",
     "triggers": []
   },
-  {
-    "id": "mcp-builder",
-    "name": "mcp-builder",
-    "canonical_id": "mcp-builder",
-    "deprecated": false,
-    "replaced_by": null,
-    "path": ".windsurf/skills/mcp-builder/SKILL.md",
-    "description": "MCP (Model Context Protocol) server building principles. Tool design, resource patterns, best practices.",
-    "triggers": []
-  },
-  {
-    "id": "mcp-developer",
-    "name": "mcp-developer",
-    "canonical_id": "mcp-developer",
-    "deprecated": false,
-    "replaced_by": null,
-    "path": ".windsurf/skills/mcp-developer/SKILL.md",
-    "description": "Use for implementing, debugging, and maintaining MCP servers/clients with SDKs, protocol compliance, transports, schemas, and security hardening.",
-    "triggers": [
-      "MCP",
-      "Model Context Protocol",
-      "MCP server",
-      "MCP client",
-      "Claude integration",
-      "AI tools",
-      "context protocol",
-      "JSON-RPC"
-    ]
-  },
   {
     "id": "microservices-architect",
     "name": "microservices-architect",
@@ -823,16 +741,6 @@
       "visual testing"
     ]
   },
-  {
-    "id": "postman",
-    "name": "postman",
-    "canonical_id": "postman",
-    "deprecated": false,
-    "replaced_by": null,
-    "path": ".windsurf/skills/postman/SKILL.md",
-    "description": "Automate API testing and collection management with Postman - create workspaces, collections, environments, and run tests programmatically",
-    "triggers": []
-  },
   {
     "id": "powershell-windows",
     "name": "powershell-windows",
@@ -1004,16 +912,6 @@
     "description": "Run Semgrep static analysis scan on a codebase using parallel subagents. Automatically",
     "triggers": []
   },
-  {
-    "id": "sentry-automation",
-    "name": "sentry-automation",
-    "canonical_id": "sentry-automation",
-    "deprecated": false,
-    "replaced_by": null,
-    "path": ".windsurf/skills/sentry-automation/SKILL.md",
-    "description": "Automate Sentry tasks via Rube MCP (Composio): manage issues/events, configure alerts, track releases, monitor projects and teams. Always search tools first for current schemas.",
-    "triggers": []
-  },
   {
     "id": "seo-fundamentals",
     "name": "seo-fundamentals",

package/workflows/workflows/agent-environment-setup/platforms/windsurf/skills/stitch/SKILL.md

@@ -0,0 +1,17 @@
+---
+name: stitch
+description: Automate Stitch workflows through Stitch MCP using mcp-remote transport.
+---
+
+# Stitch MCP
+
+Use this skill when you need to call Stitch tools through MCP passthrough.
+
+## Required Environment Variables
+
+- `STITCH_API_KEY_<PROFILE>` for Stitch API-key mode.
+
+## Notes
+
+- Stitch transport uses `mcp-remote` to `https://stitch.googleapis.com/mcp`.
+- Inject `X-Goog-Api-Key` from environment at runtime. Do not store raw keys in config files.

package/mcp/catalogs/default.json

@@ -1,14 +0,0 @@
-{
-  "profile": "mcp-default",
-  "version": 1,
-  "skills": [
-    "postman",
-    "atlassian-mcp",
-    "github-automation",
-    "sentry-automation",
-    "datadog-automation",
-    "mcp-builder",
-    "mcp-developer",
-    "building-mcp-server-on-cloudflare"
-  ]
-}

package/mcp/powers/atlassian-mcp/POWER.md

@@ -1,91 +0,0 @@
-````markdown
----
-inclusion: manual
-name: atlassian-mcp
-description: Use when querying Jira issues, searching Confluence pages, creating tickets, updating documentation, or integrating Atlassian tools via MCP protocol.
-license: MIT
-metadata:
-  author: https://github.com/Jeffallan
-  version: "1.0.0"
-  domain: platform
-  triggers: Jira, Confluence, Atlassian, MCP, tickets, issues, wiki, JQL, CQL, sprint, backlog, project management
-  role: expert
-  scope: implementation
-  output-format: code
-  related-skills: mcp-developer, api-designer, security-reviewer
----
-
-# Atlassian MCP Expert
-
-Senior integration specialist with deep expertise in connecting Jira, Confluence, and other Atlassian tools to AI systems via Model Context Protocol (MCP).
-
-## Role Definition
-
-You are an expert in Atlassian MCP integration with mastery of both official and open-source MCP servers, JQL/CQL query languages, OAuth 2.0 authentication, and production deployment patterns. You build robust workflows that automate issue triage, documentation sync, sprint planning, and cross-tool integration while respecting permissions and maintaining security.
-
-## When to Use This Skill
-
-- Querying Jira issues with JQL filters
-- Searching or creating Confluence pages
-- Automating sprint workflows and backlog management
-- Setting up MCP server authentication (OAuth/API tokens)
-- Syncing meeting notes to Jira tickets
-- Generating documentation from issue data
-- Debugging Atlassian API integration issues
-- Choosing between official vs open-source MCP servers
-
-## Core Workflow
-
-1. **Select server** - Choose official cloud, open-source, or self-hosted MCP server
-2. **Authenticate** - Configure OAuth 2.1, API tokens, or PAT credentials
-3. **Design queries** - Write JQL for Jira, CQL for Confluence, test filters
-4. **Implement workflow** - Build tool calls, handle pagination, error recovery
-5. **Deploy** - Configure IDE integration, test permissions, monitor rate limits
-
-## Reference Guide
-
-Load detailed guidance based on context:
-
-| Topic | Reference | Load When |
-|-------|-----------|-----------|
-| Server Setup | `references/mcp-server-setup.md` | Installation, choosing servers, configuration |
-| Jira Operations | `references/jira-queries.md` | JQL syntax, issue CRUD, sprints, boards |
-| Confluence Ops | `references/confluence-operations.md` | CQL search, page creation, spaces, comments |
-| Authentication | `references/authentication-patterns.md` | OAuth 2.0, API tokens, permission scopes |
-| Common Workflows | `references/common-workflows.md` | Issue triage, doc sync, sprint automation |
-
-## Constraints
-
-### MUST DO
-- Respect user permissions and workspace access controls
-- Validate JQL/CQL queries before execution
-- Handle rate limits with exponential backoff
-- Use pagination for large result sets (50-100 items per page)
-- Implement error recovery for network failures
-- Log API calls for debugging and audit trails
-- Test with read-only operations first
-- Document required permission scopes
-
-### MUST NOT DO
-- Hardcode API tokens or OAuth secrets in code
-- Ignore rate limit headers from Atlassian APIs
-- Create issues without validating required fields
-- Skip input sanitization on user-provided query strings
-- Deploy without testing permission boundaries
-- Update production data without confirmation prompts
-- Mix different authentication methods in same session
-- Expose sensitive issue data in logs or error messages
-
-## Output Templates
-
-When implementing Atlassian MCP features, provide:
-1. MCP server configuration (JSON/environment vars)
-2. Query examples (JQL/CQL with explanations)
-3. Tool call implementation with error handling
-4. Authentication setup instructions
-5. Brief explanation of permission requirements
-
-## Knowledge Reference
-
-Atlassian MCP Server (official), mcp-atlassian (sooperset), atlassian-mcp (xuanxt), JQL (Jira Query Language), CQL (Confluence Query Language), OAuth 2.1, API tokens, Personal Access Tokens (PAT), Model Context Protocol, JSON-RPC 2.0, rate limiting, pagination, permission scopes, Jira REST API, Confluence REST API
-````

package/mcp/powers/atlassian-mcp/SKILL.md

@@ -1,88 +0,0 @@
----
-name: atlassian-mcp
-description: Use when querying Jira issues, searching Confluence pages, creating tickets, updating documentation, or integrating Atlassian tools via MCP protocol.
-license: MIT
-metadata:
-  author: https://github.com/Jeffallan
-  version: "1.0.0"
-  domain: platform
-  triggers: Jira, Confluence, Atlassian, MCP, tickets, issues, wiki, JQL, CQL, sprint, backlog, project management
-  role: expert
-  scope: implementation
-  output-format: code
-  related-skills: mcp-developer, api-designer, security-reviewer
----
-
-# Atlassian MCP Expert
-
-Senior integration specialist with deep expertise in connecting Jira, Confluence, and other Atlassian tools to AI systems via Model Context Protocol (MCP).
-
-## Role Definition
-
-You are an expert in Atlassian MCP integration with mastery of both official and open-source MCP servers, JQL/CQL query languages, OAuth 2.0 authentication, and production deployment patterns. You build robust workflows that automate issue triage, documentation sync, sprint planning, and cross-tool integration while respecting permissions and maintaining security.
-
-## When to Use This Skill
-
-- Querying Jira issues with JQL filters
-- Searching or creating Confluence pages
-- Automating sprint workflows and backlog management
-- Setting up MCP server authentication (OAuth/API tokens)
-- Syncing meeting notes to Jira tickets
-- Generating documentation from issue data
-- Debugging Atlassian API integration issues
-- Choosing between official vs open-source MCP servers
-
-## Core Workflow
-
-1. **Select server** - Choose official cloud, open-source, or self-hosted MCP server
-2. **Authenticate** - Configure OAuth 2.1, API tokens, or PAT credentials
-3. **Design queries** - Write JQL for Jira, CQL for Confluence, test filters
-4. **Implement workflow** - Build tool calls, handle pagination, error recovery
-5. **Deploy** - Configure IDE integration, test permissions, monitor rate limits
-
-## Reference Guide
-
-Load detailed guidance based on context:
-
-| Topic | Reference | Load When |
-|-------|-----------|-----------|
-| Server Setup | `references/mcp-server-setup.md` | Installation, choosing servers, configuration |
-| Jira Operations | `references/jira-queries.md` | JQL syntax, issue CRUD, sprints, boards |
-| Confluence Ops | `references/confluence-operations.md` | CQL search, page creation, spaces, comments |
-| Authentication | `references/authentication-patterns.md` | OAuth 2.0, API tokens, permission scopes |
-| Common Workflows | `references/common-workflows.md` | Issue triage, doc sync, sprint automation |
-
-## Constraints
-
-### MUST DO
-- Respect user permissions and workspace access controls
-- Validate JQL/CQL queries before execution
-- Handle rate limits with exponential backoff
-- Use pagination for large result sets (50-100 items per page)
-- Implement error recovery for network failures
-- Log API calls for debugging and audit trails
-- Test with read-only operations first
-- Document required permission scopes
-
-### MUST NOT DO
-- Hardcode API tokens or OAuth secrets in code
-- Ignore rate limit headers from Atlassian APIs
-- Create issues without validating required fields
-- Skip input sanitization on user-provided query strings
-- Deploy without testing permission boundaries
-- Update production data without confirmation prompts
-- Mix different authentication methods in same session
-- Expose sensitive issue data in logs or error messages
-
-## Output Templates
-
-When implementing Atlassian MCP features, provide:
-1. MCP server configuration (JSON/environment vars)
-2. Query examples (JQL/CQL with explanations)
-3. Tool call implementation with error handling
-4. Authentication setup instructions
-5. Brief explanation of permission requirements
-
-## Knowledge Reference
-
-Atlassian MCP Server (official), mcp-atlassian (sooperset), atlassian-mcp (xuanxt), JQL (Jira Query Language), CQL (Confluence Query Language), OAuth 2.1, API tokens, Personal Access Tokens (PAT), Model Context Protocol, JSON-RPC 2.0, rate limiting, pagination, permission scopes, Jira REST API, Confluence REST API