npm - @cubis/foundry - Versions diffs - 0.3.32 → 0.3.33 - Mend

@cubis/foundry 0.3.32 → 0.3.33

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (460) hide show

package/workflows/powers/mcp-builder/POWER.md CHANGED Viewed

@@ -1,179 +1,21 @@
 ````markdown
 ---
 inclusion: manual
-name: mcp-builder
-description: MCP (Model Context Protocol) server building principles. Tool design, resource patterns, best practices.
-allowed-tools: Read, Write, Edit, Glob, Grep
+name: "mcp-builder"
+description: "Compatibility wrapper skill. Canonical MCP skill moved to mcp/skills/mcp-builder."
+metadata:
+  deprecated: true
+  replaced_by: "mcp-builder"
+  moved_to: "mcp/skills/mcp-builder/SKILL.md"
+  removal_target: "v0.6.0"
 ---
-# MCP Builder
+# mcp-builder (Compatibility Wrapper)
-> Principles for building MCP servers.
+This legacy workflow-path skill is kept for backward compatibility.
----
-## 1. MCP Overview
-### What is MCP?
-Model Context Protocol - standard for connecting AI systems with external tools and data sources.
-### Core Concepts
-| Concept | Purpose |
-|---------|---------|
-| **Tools** | Functions AI can call |
-| **Resources** | Data AI can read |
-| **Prompts** | Pre-defined prompt templates |
----
-## 2. Server Architecture
-### Project Structure
-```
-my-mcp-server/
-├── src/
-│   └── index.ts      # Main entry
-├── package.json
-└── tsconfig.json
-```
-### Transport Types
-| Type | Use |
-|------|-----|
-| **Stdio** | Local, CLI-based |
-| **SSE** | Web-based, streaming |
-| **WebSocket** | Real-time, bidirectional |
----
-## 3. Tool Design Principles
-### Good Tool Design
-| Principle | Description |
-|-----------|-------------|
-| Clear name | Action-oriented (get_weather, create_user) |
-| Single purpose | One thing well |
-| Validated input | Schema with types and descriptions |
-| Structured output | Predictable response format |
-### Input Schema Design
-| Field | Required? |
-|-------|-----------|
-| Type | Yes - object |
-| Properties | Define each param |
-| Required | List mandatory params |
-| Description | Human-readable |
----
-## 4. Resource Patterns
-### Resource Types
-| Type | Use |
-|------|-----|
-| Static | Fixed data (config, docs) |
-| Dynamic | Generated on request |
-| Template | URI with parameters |
-### URI Patterns
-| Pattern | Example |
-|---------|---------|
-| Fixed | `docs://readme` |
-| Parameterized | `users://{userId}` |
-| Collection | `files://project/*` |
----
-## 5. Error Handling
-### Error Types
-| Situation | Response |
-|-----------|----------|
-| Invalid params | Validation error message |
-| Not found | Clear "not found" |
-| Server error | Generic error, log details |
-### Best Practices
-- Return structured errors
-- Don't expose internal details
-- Log for debugging
-- Provide actionable messages
----
-## 6. Multimodal Handling
-### Supported Types
-| Type | Encoding |
-|------|----------|
-| Text | Plain text |
-| Images | Base64 + MIME type |
-| Files | Base64 + MIME type |
----
-## 7. Security Principles
-### Input Validation
-- Validate all tool inputs
-- Sanitize user-provided data
-- Limit resource access
-### API Keys
-- Use environment variables
-- Don't log secrets
-- Validate permissions
----
-## 8. Configuration
-### Claude Desktop Config
-| Field | Purpose |
-|-------|---------|
-| command | Executable to run |
-| args | Command arguments |
-| env | Environment variables |
----
-## 9. Testing
-### Test Categories
-| Type | Focus |
-|------|-------|
-| Unit | Tool logic |
-| Integration | Full server |
-| Contract | Schema validation |
----
-## 10. Best Practices Checklist
-- [ ] Clear, action-oriented tool names
-- [ ] Complete input schemas with descriptions
-- [ ] Structured JSON output
-- [ ] Error handling for all cases
-- [ ] Input validation
-- [ ] Environment-based configuration
-- [ ] Logging for debugging
----
+Canonical MCP skill path:
+- mcp/skills/mcp-builder/SKILL.md
-> **Remember:** MCP tools should be simple, focused, and well-documented. The AI relies on descriptions to use them correctly.
+Install MCP skills with: cbx workflows install --include-mcp
 ````

package/workflows/powers/mcp-builder/SKILL.md CHANGED Viewed

@@ -1,176 +1,18 @@
 ---
-name: mcp-builder
-description: MCP (Model Context Protocol) server building principles. Tool design, resource patterns, best practices.
-allowed-tools: Read, Write, Edit, Glob, Grep
+name: "mcp-builder"
+description: "Compatibility wrapper skill. Canonical MCP skill moved to mcp/skills/mcp-builder."
+metadata:
+  deprecated: true
+  replaced_by: "mcp-builder"
+  moved_to: "mcp/skills/mcp-builder/SKILL.md"
+  removal_target: "v0.6.0"
 ---
-# MCP Builder
+# mcp-builder (Compatibility Wrapper)
-> Principles for building MCP servers.
+This legacy workflow-path skill is kept for backward compatibility.
----
-## 1. MCP Overview
-### What is MCP?
-Model Context Protocol - standard for connecting AI systems with external tools and data sources.
-### Core Concepts
-| Concept | Purpose |
-|---------|---------|
-| **Tools** | Functions AI can call |
-| **Resources** | Data AI can read |
-| **Prompts** | Pre-defined prompt templates |
----
-## 2. Server Architecture
-### Project Structure
-```
-my-mcp-server/
-├── src/
-│   └── index.ts      # Main entry
-├── package.json
-└── tsconfig.json
-```
-### Transport Types
-| Type | Use |
-|------|-----|
-| **Stdio** | Local, CLI-based |
-| **SSE** | Web-based, streaming |
-| **WebSocket** | Real-time, bidirectional |
----
-## 3. Tool Design Principles
-### Good Tool Design
-| Principle | Description |
-|-----------|-------------|
-| Clear name | Action-oriented (get_weather, create_user) |
-| Single purpose | One thing well |
-| Validated input | Schema with types and descriptions |
-| Structured output | Predictable response format |
-### Input Schema Design
-| Field | Required? |
-|-------|-----------|
-| Type | Yes - object |
-| Properties | Define each param |
-| Required | List mandatory params |
-| Description | Human-readable |
----
-## 4. Resource Patterns
-### Resource Types
-| Type | Use |
-|------|-----|
-| Static | Fixed data (config, docs) |
-| Dynamic | Generated on request |
-| Template | URI with parameters |
-### URI Patterns
-| Pattern | Example |
-|---------|---------|
-| Fixed | `docs://readme` |
-| Parameterized | `users://{userId}` |
-| Collection | `files://project/*` |
----
-## 5. Error Handling
-### Error Types
-| Situation | Response |
-|-----------|----------|
-| Invalid params | Validation error message |
-| Not found | Clear "not found" |
-| Server error | Generic error, log details |
-### Best Practices
-- Return structured errors
-- Don't expose internal details
-- Log for debugging
-- Provide actionable messages
----
-## 6. Multimodal Handling
-### Supported Types
-| Type | Encoding |
-|------|----------|
-| Text | Plain text |
-| Images | Base64 + MIME type |
-| Files | Base64 + MIME type |
----
-## 7. Security Principles
-### Input Validation
-- Validate all tool inputs
-- Sanitize user-provided data
-- Limit resource access
-### API Keys
-- Use environment variables
-- Don't log secrets
-- Validate permissions
----
-## 8. Configuration
-### Claude Desktop Config
-| Field | Purpose |
-|-------|---------|
-| command | Executable to run |
-| args | Command arguments |
-| env | Environment variables |
----
-## 9. Testing
-### Test Categories
-| Type | Focus |
-|------|-------|
-| Unit | Tool logic |
-| Integration | Full server |
-| Contract | Schema validation |
----
-## 10. Best Practices Checklist
-- [ ] Clear, action-oriented tool names
-- [ ] Complete input schemas with descriptions
-- [ ] Structured JSON output
-- [ ] Error handling for all cases
-- [ ] Input validation
-- [ ] Environment-based configuration
-- [ ] Logging for debugging
----
+Canonical MCP skill path:
+- mcp/skills/mcp-builder/SKILL.md
-> **Remember:** MCP tools should be simple, focused, and well-documented. The AI relies on descriptions to use them correctly.
+Install MCP skills with: cbx workflows install --include-mcp

package/workflows/powers/mcp-developer/POWER.md CHANGED Viewed

@@ -1,88 +1,21 @@
 ````markdown
 ---
 inclusion: manual
-name: mcp-developer
-description: "Use for implementing, debugging, and maintaining MCP servers/clients with SDKs, protocol compliance, transports, schemas, and security hardening."
-license: MIT
+name: "mcp-developer"
+description: "Compatibility wrapper skill. Canonical MCP skill moved to mcp/skills/mcp-developer."
 metadata:
-  author: https://github.com/Jeffallan
-  version: "1.0.0"
-  domain: api-architecture
-  triggers: MCP, Model Context Protocol, MCP server, MCP client, Claude integration, AI tools, context protocol, JSON-RPC
-  role: specialist
-  scope: implementation
-  output-format: code
-  related-skills: fastapi-expert, typescript-pro, security-reviewer, devops-engineer
+  deprecated: true
+  replaced_by: "mcp-developer"
+  moved_to: "mcp/skills/mcp-developer/SKILL.md"
+  removal_target: "v0.6.0"
 ---
-# MCP Developer
+# mcp-developer (Compatibility Wrapper)
-Senior MCP (Model Context Protocol) developer with deep expertise in building servers and clients that connect AI systems with external tools and data sources.
+This legacy workflow-path skill is kept for backward compatibility.
-## Role Definition
+Canonical MCP skill path:
+- mcp/skills/mcp-developer/SKILL.md
-You are a senior MCP developer with expertise in protocol implementation, SDK usage (TypeScript/Python), and production deployment. You build robust MCP servers that expose resources, tools, and prompts to Claude and other AI systems while maintaining security, performance, and developer experience standards.
-## When to Use This Skill
-- Building MCP servers for data source integration
-- Implementing tool functions for AI assistants
-- Creating resource providers with URI schemes
-- Setting up MCP clients for Claude integration
-- Debugging protocol compliance issues
-- Optimizing MCP performance and security
-## Core Workflow
-1. **Analyze requirements** - Identify data sources, tools needed, client apps
-2. **Design protocol** - Define resources, tools, prompts, schemas
-3. **Implement** - Build server/client with SDK, add security controls
-4. **Test** - Verify protocol compliance, performance, error handling
-5. **Deploy** - Package, configure, monitor in production
-## Reference Guide
-Load detailed guidance based on context:
-| Topic | Reference | Load When |
-|-------|-----------|-----------|
-| Protocol | `references/protocol.md` | Message types, lifecycle, JSON-RPC 2.0 |
-| TypeScript SDK | `references/typescript-sdk.md` | Building servers/clients in Node.js |
-| Python SDK | `references/python-sdk.md` | Building servers/clients in Python |
-| Tools | `references/tools.md` | Tool definitions, schemas, execution |
-| Resources | `references/resources.md` | Resource providers, URIs, templates |
-## Constraints
-### MUST DO
-- Implement JSON-RPC 2.0 protocol correctly
-- Validate all inputs with schemas (Zod/Pydantic)
-- Use proper transport mechanisms (stdio/HTTP/SSE)
-- Implement comprehensive error handling
-- Add authentication and authorization
-- Log protocol messages for debugging
-- Test protocol compliance thoroughly
-- Document server capabilities
-### MUST NOT DO
-- Skip input validation on tool inputs
-- Expose sensitive data in resource content
-- Ignore protocol version compatibility
-- Mix synchronous code with async transports
-- Hardcode credentials or secrets
-- Return unstructured errors to clients
-- Deploy without rate limiting
-- Skip security controls
-## Output Templates
-When implementing MCP features, provide:
-1. Server/client implementation file
-2. Schema definitions (tools, resources, prompts)
-3. Configuration file (transport, auth, etc.)
-4. Brief explanation of design decisions
-## Knowledge Reference
-Model Context Protocol (MCP), JSON-RPC 2.0, TypeScript SDK (@modelcontextprotocol/sdk), Python SDK (mcp), Zod schemas, Pydantic validation, stdio transport, SSE transport, resource URIs, tool functions, prompt templates, authentication, rate limiting
+Install MCP skills with: cbx workflows install --include-mcp
 ````

package/workflows/powers/mcp-developer/SKILL.md CHANGED Viewed

@@ -1,85 +1,18 @@
 ---
-name: mcp-developer
-description: "Use for implementing, debugging, and maintaining MCP servers/clients with SDKs, protocol compliance, transports, schemas, and security hardening."
-license: MIT
+name: "mcp-developer"
+description: "Compatibility wrapper skill. Canonical MCP skill moved to mcp/skills/mcp-developer."
 metadata:
-  author: https://github.com/Jeffallan
-  version: "1.0.0"
-  domain: api-architecture
-  triggers: MCP, Model Context Protocol, MCP server, MCP client, Claude integration, AI tools, context protocol, JSON-RPC
-  role: specialist
-  scope: implementation
-  output-format: code
-  related-skills: fastapi-expert, typescript-pro, security-reviewer, devops-engineer
+  deprecated: true
+  replaced_by: "mcp-developer"
+  moved_to: "mcp/skills/mcp-developer/SKILL.md"
+  removal_target: "v0.6.0"
 ---
-# MCP Developer
+# mcp-developer (Compatibility Wrapper)
-Senior MCP (Model Context Protocol) developer with deep expertise in building servers and clients that connect AI systems with external tools and data sources.
+This legacy workflow-path skill is kept for backward compatibility.
-## Role Definition
+Canonical MCP skill path:
+- mcp/skills/mcp-developer/SKILL.md
-You are a senior MCP developer with expertise in protocol implementation, SDK usage (TypeScript/Python), and production deployment. You build robust MCP servers that expose resources, tools, and prompts to Claude and other AI systems while maintaining security, performance, and developer experience standards.
-## When to Use This Skill
-- Building MCP servers for data source integration
-- Implementing tool functions for AI assistants
-- Creating resource providers with URI schemes
-- Setting up MCP clients for Claude integration
-- Debugging protocol compliance issues
-- Optimizing MCP performance and security
-## Core Workflow
-1. **Analyze requirements** - Identify data sources, tools needed, client apps
-2. **Design protocol** - Define resources, tools, prompts, schemas
-3. **Implement** - Build server/client with SDK, add security controls
-4. **Test** - Verify protocol compliance, performance, error handling
-5. **Deploy** - Package, configure, monitor in production
-## Reference Guide
-Load detailed guidance based on context:
-| Topic | Reference | Load When |
-|-------|-----------|-----------|
-| Protocol | `references/protocol.md` | Message types, lifecycle, JSON-RPC 2.0 |
-| TypeScript SDK | `references/typescript-sdk.md` | Building servers/clients in Node.js |
-| Python SDK | `references/python-sdk.md` | Building servers/clients in Python |
-| Tools | `references/tools.md` | Tool definitions, schemas, execution |
-| Resources | `references/resources.md` | Resource providers, URIs, templates |
-## Constraints
-### MUST DO
-- Implement JSON-RPC 2.0 protocol correctly
-- Validate all inputs with schemas (Zod/Pydantic)
-- Use proper transport mechanisms (stdio/HTTP/SSE)
-- Implement comprehensive error handling
-- Add authentication and authorization
-- Log protocol messages for debugging
-- Test protocol compliance thoroughly
-- Document server capabilities
-### MUST NOT DO
-- Skip input validation on tool inputs
-- Expose sensitive data in resource content
-- Ignore protocol version compatibility
-- Mix synchronous code with async transports
-- Hardcode credentials or secrets
-- Return unstructured errors to clients
-- Deploy without rate limiting
-- Skip security controls
-## Output Templates
-When implementing MCP features, provide:
-1. Server/client implementation file
-2. Schema definitions (tools, resources, prompts)
-3. Configuration file (transport, auth, etc.)
-4. Brief explanation of design decisions
-## Knowledge Reference
-Model Context Protocol (MCP), JSON-RPC 2.0, TypeScript SDK (@modelcontextprotocol/sdk), Python SDK (mcp), Zod schemas, Pydantic validation, stdio transport, SSE transport, resource URIs, tool functions, prompt templates, authentication, rate limiting
+Install MCP skills with: cbx workflows install --include-mcp