@cubis/foundry 0.3.31 → 0.3.33

package/workflows/workflows/agent-environment-setup/platforms/cursor/skills/database-skills/skills/vitess/references/operational-safety.md

@@ -0,0 +1,105 @@
+# Vitess — Online DDL and Operational Safety
+
+## Online DDL strategies
+
+Vitess manages schema changes as tracked, non-blocking, revertible migrations. This is the **only recommended approach** for production schema changes.
+
+Set DDL strategy per session or globally:
+```sql
+SET @@ddl_strategy = 'vitess';
+```
+
+| Strategy | Description |
+| --- | --- |
+| `vitess` (**recommended**) | VReplication-based. Non-blocking, revertible, failover-safe. |
+| `online` | Alias for `vitess`. |
+| `mysql` | Native MySQL DDL managed by Vitess scheduler. Blocking depends on the DDL. |
+| `direct` | Unmanaged — direct DDL to MySQL. Not trackable. Avoid in production. |
+
+## Running a migration
+
+```sql
+SET @@ddl_strategy = 'vitess';
+ALTER TABLE orders ADD COLUMN notes TEXT;   -- returns migration UUID immediately
+```
+
+```bash
+vtctldclient ApplySchema --ddl-strategy "vitess" \
+  --sql "ALTER TABLE orders ADD COLUMN notes TEXT" commerce
+```
+
+## Migration lifecycle
+
+```
+queued → ready → running → complete
+                         ↘ failed
+         ↘ cancelled
+```
+
+## Monitor and control migrations
+
+```sql
+SHOW VITESS_MIGRATIONS;                                         -- all migrations
+SHOW VITESS_MIGRATIONS LIKE '<uuid>';                           -- specific migration
+```
+
+Key columns to watch: `migration_status`, `progress`, `started_timestamp`, `completed_timestamp`, `message`.
+
+```sql
+ALTER VITESS_MIGRATION '<uuid>' CANCEL;    -- cancel pending
+ALTER VITESS_MIGRATION '<uuid>' RETRY;     -- retry failed
+ALTER VITESS_MIGRATION '<uuid>' COMPLETE;  -- complete a postponed migration
+ALTER VITESS_MIGRATION '<uuid>' LAUNCH;    -- launch a postponed migration
+REVERT VITESS_MIGRATION '<uuid>';          -- revert a completed migration (non-destructive)
+```
+
+## Key DDL strategy flags
+
+Append flags to strategy string:
+```sql
+SET @@ddl_strategy = 'vitess --postpone-completion --allow-concurrent';
+```
+
+| Flag | Effect |
+| --- | --- |
+| `--postpone-launch` | Queue migration but don't start automatically |
+| `--postpone-completion` | Run migration but don't cut over — you control timing |
+| `--allow-concurrent` | Allow multiple migrations to run simultaneously |
+| `--declarative` | Provide desired `CREATE TABLE`; Vitess computes the ALTER |
+| `--prefer-instant-ddl` | Use MySQL INSTANT DDL when possible |
+| `--singleton` | Only one migration on this table at a time |
+
+## Declarative migrations
+
+Supply the desired schema; Vitess computes the diff and runs the minimal ALTER:
+```sql
+SET @@ddl_strategy = 'vitess --declarative';
+CREATE TABLE demo (id BIGINT UNSIGNED NOT NULL, status VARCHAR(32), PRIMARY KEY (id));
+```
+
+## Throttling and failover safety
+
+- The **tablet throttler** automatically slows migrations when replication lag is high.
+  Enable: `vtctldclient UpdateThrottlerConfig --enable <keyspace>`
+- VReplication-based migrations **auto-resume** after primary reparenting (new primary must come up within 10 min).
+
+## Operational guardrails
+
+- **Stage topology and resharding changes** in maintenance windows; keep blast radius small per operation.
+- **Watch fan-out and replication lag** as release gates — do not proceed if lag is elevated.
+- **Prepare explicit rollback procedures per shard move**: `MoveTables SwitchTraffic --reverse`, then `MoveTables Complete` on the old keyspace.
+- Validate with `VDiff` before completing table moves: `vtctldclient VDiff <keyspace> <workflow>`.
+- Test resharding end-to-end on staging with production-like data volume before production.
+
+## Best practices
+
+1. Always use `vitess` strategy in production — never `direct`.
+2. Use `--postpone-completion` for critical tables to control cut-over timing precisely.
+3. Enable the tablet throttler to prevent replication lag buildup.
+4. Use declarative migrations for desired-state schema management.
+5. Monitor all running migrations with `SHOW VITESS_MIGRATIONS` before and after deployments.
+
+## Sources
+- Online DDL guide: https://vitess.io/docs/user-guides/schema-changes/
+- VReplication reference: https://vitess.io/docs/reference/vreplication/
+- Release notes / lifecycle: https://vitess.io/docs/releases/

package/workflows/workflows/agent-environment-setup/platforms/cursor/skills/database-skills/skills/vitess/references/sharding-routing.md

@@ -0,0 +1,125 @@
+# Vitess — Sharding and VSchema Design
+
+## Core concept
+
+The **VSchema** tells VTGate how to route queries. It defines which tables belong to which keyspace, which column determines shard placement (the **primary vindex**), and how tables relate across shards.
+
+## Shard routing types
+
+| Routing | Condition | Performance |
+| --- | --- | --- |
+| **Single-shard** | `WHERE` on primary vindex with `=` | Best |
+| **Multi-shard (targeted)** | `WHERE` with `IN` on primary vindex | Good |
+| **Scatter** | No primary vindex filter | Expensive — hits all shards |
+
+Always include the primary vindex column in `WHERE` clauses to avoid scatter queries.
+
+## Choosing a primary vindex column
+
+Pick the column that:
+1. Appears in your highest-QPS `WHERE` clauses.
+2. Enables join co-location — tables frequently joined should shard on the same column.
+3. Keeps transactions within a single shard.
+4. Has high cardinality for even distribution.
+5. Is immutable — changing it after insert requires a data migration.
+
+Common choices: `user_id`, `tenant_id`, `org_id`, `account_id`.
+
+## Vindex types
+
+| Type | When to use |
+| --- | --- |
+| `xxhash` | Any column type — most common |
+| `unicode_loose_xxhash` | Text columns needing case-insensitive hashing |
+| `binary_md5` | MD5-based alternative for any column type |
+
+## VSchema structure (sharded keyspace)
+
+```json
+{
+  "sharded": true,
+  "vindexes": {
+    "xxhash": { "type": "xxhash" }
+  },
+  "tables": {
+    "orders": {
+      "column_vindexes": [
+        { "column": "customer_id", "name": "xxhash" }
+      ],
+      "auto_increment": {
+        "column": "id",
+        "sequence": "unsharded_keyspace.orders_seq"
+      }
+    }
+  }
+}
+```
+
+## Sequences — replacing AUTO_INCREMENT
+
+Per-shard `AUTO_INCREMENT` produces duplicate IDs across shards. Use Vitess Sequences instead.
+
+1. Create in an **unsharded** keyspace:
+   ```sql
+   CREATE TABLE orders_seq (id BIGINT, next_id BIGINT, cache BIGINT, PRIMARY KEY(id))
+     COMMENT 'vitess_sequence';
+   INSERT INTO orders_seq (id, next_id, cache) VALUES (0, 1, 1000);
+   ```
+2. Register in unsharded VSchema: `{ "orders_seq": { "type": "sequence" } }`
+3. Link to sharded table via `auto_increment` in sharded VSchema (see above).
+
+Sequence gaps from caching/restarts are expected and harmless.
+
+## Lookup vindexes (secondary routing)
+
+Lookup vindexes let you route by non-primary-vindex columns without scatter. They are backed by a separate mapping table. **They are expensive** — avoid unless scatter on the column is genuinely a problem.
+
+```json
+"customer_email_lookup": {
+  "type": "consistent_lookup",
+  "params": {
+    "table": "product.customer_email_lookup",
+    "from": "email",
+    "to": "keyspace_id"
+  },
+  "owner": "customer"
+}
+```
+
+Use `consistent_lookup_unique` only when uniqueness across shards must be enforced at the DB level (this is a scalability anti-pattern — prefer app-level enforcement).
+
+## Discover existing VSchema
+
+```bash
+vtctldclient GetVSchema <keyspace>                     # full JSON
+vtctldclient GetVSchema <keyspace> | jq '.vindexes'   # just vindexes
+```
+
+```sql
+SHOW VSCHEMA TABLES;        -- tables known to VTGate
+SHOW VSCHEMA VINDEXES;      -- vindexes and types
+```
+
+## Troubleshoot scatter queries
+
+```sql
+VEXPLAIN PLAN SELECT * FROM orders WHERE customer_id = 42;
+-- Look for Route variant: EqualUnique (single-shard) vs Scatter (all shards)
+
+VEXPLAIN ALL SELECT ...;    -- includes MySQL plans from each tablet
+VEXPLAIN TRACE SELECT ...;  -- shows row counts passed between query parts
+```
+
+If a query scatters:
+1. Is `WHERE` filtering on the primary vindex column? If not, add it.
+2. Is a lookup vindex configured for that column? If needed, add one.
+3. Primary vindex column updates are blocked — use `MoveTables` to re-shard if needed.
+
+## Reference tables
+
+Small, rarely-changing lookup data (countries, currencies, enums) can use `"type": "reference"` — they are replicated to all shards and never scatter.
+
+## Sources
+- VSchema guide: https://vitess.io/docs/user-guides/vschema-guide/
+- Vindexes reference: https://vitess.io/docs/reference/features/vschema/
+- Sharding key selection: https://vitess.io/docs/faq/advanced-configuration/vschema/how-do-you-select-your-sharding-key-for-vitess/

package/workflows/workflows/agent-environment-setup/platforms/cursor/skills/datadog-automation/SKILL.md

@@ -0,0 +1,235 @@
+---
+name: datadog-automation
+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."
+requires:
+  mcp: [rube]
+---
+
+# Datadog Automation via Rube MCP
+
+Automate Datadog monitoring and observability operations through Composio's Datadog toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Datadog connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `datadog`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `datadog`
+3. If connection is not ACTIVE, follow the returned auth link to complete Datadog authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Query and Explore Metrics
+
+**When to use**: User wants to query metric data or list available metrics
+
+**Tool sequence**:
+1. `DATADOG_LIST_METRICS` - List available metric names [Optional]
+2. `DATADOG_QUERY_METRICS` - Query metric time series data [Required]
+
+**Key parameters**:
+- `query`: Datadog metric query string (e.g., `avg:system.cpu.user{host:web01}`)
+- `from`: Start timestamp (Unix epoch seconds)
+- `to`: End timestamp (Unix epoch seconds)
+- `q`: Search string for listing metrics
+
+**Pitfalls**:
+- Query syntax follows Datadog's metric query format: `aggregation:metric_name{tag_filters}`
+- `from` and `to` are Unix epoch timestamps in seconds, not milliseconds
+- Valid aggregations: `avg`, `sum`, `min`, `max`, `count`
+- Tag filters use curly braces: `{host:web01,env:prod}`
+- Time range should not exceed Datadog's retention limits for the metric type
+
+### 2. Search and Analyze Logs
+
+**When to use**: User wants to search log entries or list log indexes
+
+**Tool sequence**:
+1. `DATADOG_LIST_LOG_INDEXES` - List available log indexes [Optional]
+2. `DATADOG_SEARCH_LOGS` - Search logs with query and filters [Required]
+
+**Key parameters**:
+- `query`: Log search query using Datadog log query syntax
+- `from`: Start time (ISO 8601 or Unix timestamp)
+- `to`: End time (ISO 8601 or Unix timestamp)
+- `sort`: Sort order ('asc' or 'desc')
+- `limit`: Number of log entries to return
+
+**Pitfalls**:
+- Log queries use Datadog's log search syntax: `service:web status:error`
+- Search is limited to retained logs within the configured retention period
+- Large result sets require pagination; check for cursor/page tokens
+- Log indexes control routing and retention; filter by index if known
+
+### 3. Manage Monitors
+
+**When to use**: User wants to create, update, mute, or inspect monitors
+
+**Tool sequence**:
+1. `DATADOG_LIST_MONITORS` - List all monitors with filters [Required]
+2. `DATADOG_GET_MONITOR` - Get specific monitor details [Optional]
+3. `DATADOG_CREATE_MONITOR` - Create a new monitor [Optional]
+4. `DATADOG_UPDATE_MONITOR` - Update monitor configuration [Optional]
+5. `DATADOG_MUTE_MONITOR` - Silence a monitor temporarily [Optional]
+6. `DATADOG_UNMUTE_MONITOR` - Re-enable a muted monitor [Optional]
+
+**Key parameters**:
+- `monitor_id`: Numeric monitor ID
+- `name`: Monitor display name
+- `type`: Monitor type ('metric alert', 'service check', 'log alert', 'query alert', etc.)
+- `query`: Monitor query defining the alert condition
+- `message`: Notification message with @mentions
+- `tags`: Array of tag strings
+- `thresholds`: Alert threshold values (`critical`, `warning`, `ok`)
+
+**Pitfalls**:
+- Monitor `type` must match the query type; mismatches cause creation failures
+- `message` supports @mentions for notifications (e.g., `@slack-channel`, `@pagerduty`)
+- Thresholds vary by monitor type; metric monitors need `critical` at minimum
+- Muting a monitor suppresses notifications but the monitor still evaluates
+- Monitor IDs are numeric integers
+
+### 4. Manage Dashboards
+
+**When to use**: User wants to list, view, update, or delete dashboards
+
+**Tool sequence**:
+1. `DATADOG_LIST_DASHBOARDS` - List all dashboards [Required]
+2. `DATADOG_GET_DASHBOARD` - Get full dashboard definition [Optional]
+3. `DATADOG_UPDATE_DASHBOARD` - Update dashboard layout or widgets [Optional]
+4. `DATADOG_DELETE_DASHBOARD` - Remove a dashboard (irreversible) [Optional]
+
+**Key parameters**:
+- `dashboard_id`: Dashboard identifier string
+- `title`: Dashboard title
+- `layout_type`: 'ordered' (grid) or 'free' (freeform positioning)
+- `widgets`: Array of widget definition objects
+- `description`: Dashboard description
+
+**Pitfalls**:
+- Dashboard IDs are alphanumeric strings (e.g., 'abc-def-ghi'), not numeric
+- `layout_type` cannot be changed after creation; must recreate the dashboard
+- Widget definitions are complex nested objects; get existing dashboard first to understand structure
+- DELETE is permanent; there is no undo
+
+### 5. Create Events and Manage Downtimes
+
+**When to use**: User wants to post events or schedule maintenance downtimes
+
+**Tool sequence**:
+1. `DATADOG_LIST_EVENTS` - List existing events [Optional]
+2. `DATADOG_CREATE_EVENT` - Post a new event [Required]
+3. `DATADOG_CREATE_DOWNTIME` - Schedule a maintenance downtime [Optional]
+
+**Key parameters for events**:
+- `title`: Event title
+- `text`: Event body text (supports markdown)
+- `alert_type`: Event severity ('error', 'warning', 'info', 'success')
+- `tags`: Array of tag strings
+
+**Key parameters for downtimes**:
+- `scope`: Tag scope for the downtime (e.g., `host:web01`)
+- `start`: Start time (Unix epoch)
+- `end`: End time (Unix epoch; omit for indefinite)
+- `message`: Downtime description
+- `monitor_id`: Specific monitor to downtime (optional, omit for scope-based)
+
+**Pitfalls**:
+- Event `text` supports Datadog's markdown format including @mentions
+- Downtimes scope uses tag syntax: `host:web01`, `env:staging`
+- Omitting `end` creates an indefinite downtime; always set an end time for maintenance
+- Downtime `monitor_id` narrows to a single monitor; scope applies to all matching monitors
+
+### 6. Manage Hosts and Traces
+
+**When to use**: User wants to list infrastructure hosts or inspect distributed traces
+
+**Tool sequence**:
+1. `DATADOG_LIST_HOSTS` - List all reporting hosts [Required]
+2. `DATADOG_GET_TRACE_BY_ID` - Get a specific distributed trace [Optional]
+
+**Key parameters**:
+- `filter`: Host search filter string
+- `sort_field`: Sort hosts by field (e.g., 'name', 'apps', 'cpu')
+- `sort_dir`: Sort direction ('asc' or 'desc')
+- `trace_id`: Distributed trace ID for trace lookup
+
+**Pitfalls**:
+- Host list includes all hosts reporting to Datadog within the retention window
+- Trace IDs are long numeric strings; ensure exact match
+- Hosts that stop reporting are retained for a configured period before removal
+
+## Common Patterns
+
+### Monitor Query Syntax
+
+**Metric alerts**:
+```
+avg(last_5m):avg:system.cpu.user{env:prod} > 90
+```
+
+**Log alerts**:
+```
+logs("service:web status:error").index("main").rollup("count").last("5m") > 10
+```
+
+### Tag Filtering
+
+- Tags use `key:value` format: `host:web01`, `env:prod`, `service:api`
+- Multiple tags: `{host:web01,env:prod}` (AND logic)
+- Wildcard: `host:web*`
+
+### Pagination
+
+- Use `page` and `page_size` or offset-based pagination depending on endpoint
+- Check response for total count to determine if more pages exist
+- Continue until all results are retrieved
+
+## Known Pitfalls
+
+**Timestamps**:
+- Most endpoints use Unix epoch seconds (not milliseconds)
+- Some endpoints accept ISO 8601; check tool schema
+- Time ranges should be reasonable (not years of data)
+
+**Query Syntax**:
+- Metric queries: `aggregation:metric{tags}`
+- Log queries: `field:value` pairs
+- Monitor queries vary by type; check Datadog documentation
+
+**Rate Limits**:
+- Datadog API has per-endpoint rate limits
+- Implement backoff on 429 responses
+- Batch operations where possible
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Query metrics | DATADOG_QUERY_METRICS | query, from, to |
+| List metrics | DATADOG_LIST_METRICS | q |
+| Search logs | DATADOG_SEARCH_LOGS | query, from, to, limit |
+| List log indexes | DATADOG_LIST_LOG_INDEXES | (none) |
+| List monitors | DATADOG_LIST_MONITORS | tags |
+| Get monitor | DATADOG_GET_MONITOR | monitor_id |
+| Create monitor | DATADOG_CREATE_MONITOR | name, type, query, message |
+| Update monitor | DATADOG_UPDATE_MONITOR | monitor_id |
+| Mute monitor | DATADOG_MUTE_MONITOR | monitor_id |
+| Unmute monitor | DATADOG_UNMUTE_MONITOR | monitor_id |
+| List dashboards | DATADOG_LIST_DASHBOARDS | (none) |
+| Get dashboard | DATADOG_GET_DASHBOARD | dashboard_id |
+| Update dashboard | DATADOG_UPDATE_DASHBOARD | dashboard_id, title, widgets |
+| Delete dashboard | DATADOG_DELETE_DASHBOARD | dashboard_id |
+| List events | DATADOG_LIST_EVENTS | start, end |
+| Create event | DATADOG_CREATE_EVENT | title, text, alert_type |
+| Create downtime | DATADOG_CREATE_DOWNTIME | scope, start, end |
+| List hosts | DATADOG_LIST_HOSTS | filter, sort_field |
+| Get trace | DATADOG_GET_TRACE_BY_ID | trace_id |

package/workflows/workflows/agent-environment-setup/platforms/cursor/skills/debugging-wizard/SKILL.md

@@ -1,87 +1,21 @@
 ---
-name: "debugging-wizard"
-description: "Use when investigating errors, analyzing stack traces, or finding root causes of unexpected behavior. Invoke for error investigation, troubleshooting, log analysis, root cause analysis."
+name: debugging-wizard
+description: "Compatibility alias skill. Deprecated: use systematic-debugging."
+metadata:
+  deprecated: true
+  replaced_by: systematic-debugging
+  removal_target: v0.6.0
 ---
 
-
 # Debugging Wizard
 
-## Overview
-
-Expert debugger applying systematic methodology to isolate and resolve issues in any codebase.
-
-## Role Definition
-
-You are a senior engineer with 15+ years debugging experience across multiple languages and frameworks. You apply scientific methodology to isolate root causes efficiently. You never guess - you test hypotheses systematically.
-
-## When to Use This Skill
-
-- Investigating errors, exceptions, or unexpected behavior
-- Analyzing stack traces and error messages
-- Finding root causes of intermittent issues
-- Performance debugging and profiling
-- Memory leak investigation
-- Race condition diagnosis
-
-## Core Workflow
-
-1. **Reproduce** - Establish consistent reproduction steps
-2. **Isolate** - Narrow down to smallest failing case
-3. **Hypothesize** - Form testable theories about cause
-4. **Test** - Verify/disprove each hypothesis
-5. **Fix** - Implement and verify solution
-6. **Prevent** - Add tests/safeguards against regression
-
-## Available Steering Files
-
-Load detailed guidance on-demand:
-
-| Topic           | Reference                     | Load When                              |
-| --------------- | ----------------------------- | -------------------------------------- |
-| Debugging Tools | `references/debugging-tools.md` | Setting up debuggers by language       |
-| Common Patterns | `references/common-patterns.md` | Recognizing bug patterns               |
-| Strategies      | `references/strategies.md`      | Binary search, git bisect, time travel |
-| Quick Fixes     | `references/quick-fixes.md`     | Common error solutions                 |
-
-<!-- Row below adapted from obra/superpowers by Jesse Vincent (@obra), MIT License -->
-
-| Systematic Debugging | `references/systematic-debugging.md` | Complex bugs, multiple failed fixes, root cause analysis |
-
-## Constraints
-
-### MUST DO
-
-- Reproduce the issue first
-- Gather complete error messages and stack traces
-- Test one hypothesis at a time
-- Document findings for future reference
-- Add regression tests after fixing
-- Remove all debug code before committing
-
-### MUST NOT DO
-
-- Guess without testing
-- Make multiple changes at once
-- Skip reproduction steps
-- Assume you know the cause
-- Debug in production without safeguards
-- Leave console.log/debugger statements in code
-
-## Output Templates
-
-When debugging, provide:
-
-1. **Root Cause**: What specifically caused the issue
-2. **Evidence**: Stack trace, logs, or test that proves it
-3. **Fix**: Code change that resolves it
-4. **Prevention**: Test or safeguard to prevent recurrence
+## Compatibility Alias
 
-## Knowledge Reference
+This skill is deprecated and kept for backward compatibility.
 
-Debuggers (Chrome DevTools, VS Code, pdb, delve), profilers, log aggregation, distributed tracing, memory analysis, git bisect, error tracking (Sentry)
+Use `systematic-debugging` as the canonical skill.
 
-## Related Powers
+## Migration
 
-- **Test Master** - Writing regression tests
-- **Fullstack Guardian** - Implementing fixes
-- **Monitoring Expert** - Setting up alerting
+1. Replace direct references to `debugging-wizard` with `systematic-debugging`.
+2. Apply the full workflow from `systematic-debugging` for new work.