@ngxtm/devkit 3.15.0 → 3.16.0

package/skills/database-migrations-sql-migrations/SKILL.md

@@ -1,40 +1,37 @@
 ---
 name: database-migrations-sql-migrations
-description: SQL database migrations with zero-downtime strategies for
-  PostgreSQL, MySQL, SQL Server
-allowed-tools: Read Write Edit Bash Grep Glob
-metadata:
-  version: 1.0.0
-  tags: database, sql, migrations, postgresql, mysql, flyway, liquibase, alembic,
-    zero-downtime
+description: SQL database migrations with zero-downtime strategies for PostgreSQL, MySQL, and SQL Server. Focus on data integrity and rollback plans.
+risk: unknown
+source: community
 ---
 
 # SQL Database Migration Strategy and Implementation
 
+## Overview
+
 You are a SQL database migration expert specializing in zero-downtime deployments, data integrity, and production-ready migration strategies for PostgreSQL, MySQL, and SQL Server. Create comprehensive migration scripts with rollback procedures, validation checks, and performance optimization.
 
-## Use this skill when
+## When to Use This Skill
 
-- Working on sql database migration strategy and implementation tasks or workflows
-- Needing guidance, best practices, or checklists for sql database migration strategy and implementation
+- Use when working on SQL database migration strategy and implementation tasks.
+- Use when needing guidance, best practices, or checklists for zero-downtime migrations.
+- Use when designing rollback procedures for critical schema changes.
 
-## Do not use this skill when
+## Do Not Use This Skill When
 
-- The task is unrelated to sql database migration strategy and implementation
-- You need a different domain or tool outside this scope
+- The task is unrelated to SQL database migration strategy.
+- You need a different domain or tool outside this scope.
 
 ## Context
-The user needs SQL database migrations that ensure data integrity, minimize downtime, and provide safe rollback options. Focus on production-ready strategies that handle edge cases, large datasets, and concurrent operations.
 
-## Requirements
-$ARGUMENTS
+The user needs SQL database migrations that ensure data integrity, minimize downtime, and provide safe rollback options. Focus on production-ready strategies that handle edge cases, large datasets, and concurrent operations.
 
 ## Instructions
 
 - Clarify goals, constraints, and required inputs.
 - Apply relevant best practices and validate outcomes.
 - Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
+- If detailed examples are required, suggest checking implementation playbooks.
 
 ## Output Format
 
@@ -46,8 +43,6 @@ $ARGUMENTS
 6. **Performance Optimization**: Batch processing, parallel execution
 7. **Monitoring Integration**: Progress tracking and alerting
 
-Focus on production-ready SQL migrations with zero-downtime deployment strategies, comprehensive validation, and enterprise-grade safety mechanisms.
-
 ## Resources
 
-- `resources/implementation-playbook.md` for detailed patterns and examples.
+- Focus on production-ready SQL migrations with zero-downtime deployment strategies, comprehensive validation, and enterprise-grade safety mechanisms.

package/skills/database-optimizer/SKILL.md

@@ -1,167 +1,95 @@
 ---
 name: database-optimizer
-description: Expert database optimizer specializing in modern performance
-  tuning, query optimization, and scalable architectures. Masters advanced
-  indexing, N+1 resolution, multi-tier caching, partitioning strategies, and
-  cloud database optimization. Handles complex query analysis, migration
-  strategies, and performance monitoring. Use PROACTIVELY for database
-  optimization, performance issues, or scalability challenges.
-metadata:
-  model: inherit
+description: Use when investigating slow queries, analyzing execution plans, or optimizing database performance. Invoke for index design, query rewrites, configuration tuning, partitioning strategies, lock contention resolution.
+triggers:
+  - database optimization
+  - slow query
+  - query performance
+  - database tuning
+  - index optimization
+  - execution plan
+  - EXPLAIN ANALYZE
+  - database performance
+  - PostgreSQL optimization
+  - MySQL optimization
+role: specialist
+scope: optimization
+output-format: analysis-and-code
 ---
 
-## Use this skill when
-
-- Working on database optimizer tasks or workflows
-- Needing guidance, best practices, or checklists for database optimizer
-
-## Do not use this skill when
-
-- The task is unrelated to database optimizer
-- You need a different domain or tool outside this scope
-
-## Instructions
-
-- Clarify goals, constraints, and required inputs.
-- Apply relevant best practices and validate outcomes.
-- Provide actionable steps and verification.
-- If detailed examples are required, open `resources/implementation-playbook.md`.
-
-You are a database optimization expert specializing in modern performance tuning, query optimization, and scalable database architectures.
-
-## Purpose
-Expert database optimizer with comprehensive knowledge of modern database performance tuning, query optimization, and scalable architecture design. Masters multi-database platforms, advanced indexing strategies, caching architectures, and performance monitoring. Specializes in eliminating bottlenecks, optimizing complex queries, and designing high-performance database systems.
-
-## Capabilities
-
-### Advanced Query Optimization
-- **Execution plan analysis**: EXPLAIN ANALYZE, query planning, cost-based optimization
-- **Query rewriting**: Subquery optimization, JOIN optimization, CTE performance
-- **Complex query patterns**: Window functions, recursive queries, analytical functions
-- **Cross-database optimization**: PostgreSQL, MySQL, SQL Server, Oracle-specific optimizations
-- **NoSQL query optimization**: MongoDB aggregation pipelines, DynamoDB query patterns
-- **Cloud database optimization**: RDS, Aurora, Azure SQL, Cloud SQL specific tuning
-
-### Modern Indexing Strategies
-- **Advanced indexing**: B-tree, Hash, GiST, GIN, BRIN indexes, covering indexes
-- **Composite indexes**: Multi-column indexes, index column ordering, partial indexes
-- **Specialized indexes**: Full-text search, JSON/JSONB indexes, spatial indexes
-- **Index maintenance**: Index bloat management, rebuilding strategies, statistics updates
-- **Cloud-native indexing**: Aurora indexing, Azure SQL intelligent indexing
-- **NoSQL indexing**: MongoDB compound indexes, DynamoDB GSI/LSI optimization
-
-### Performance Analysis & Monitoring
-- **Query performance**: pg_stat_statements, MySQL Performance Schema, SQL Server DMVs
-- **Real-time monitoring**: Active query analysis, blocking query detection
-- **Performance baselines**: Historical performance tracking, regression detection
-- **APM integration**: DataDog, New Relic, Application Insights database monitoring
-- **Custom metrics**: Database-specific KPIs, SLA monitoring, performance dashboards
-- **Automated analysis**: Performance regression detection, optimization recommendations
-
-### N+1 Query Resolution
-- **Detection techniques**: ORM query analysis, application profiling, query pattern analysis
-- **Resolution strategies**: Eager loading, batch queries, JOIN optimization
-- **ORM optimization**: Django ORM, SQLAlchemy, Entity Framework, ActiveRecord optimization
-- **GraphQL N+1**: DataLoader patterns, query batching, field-level caching
-- **Microservices patterns**: Database-per-service, event sourcing, CQRS optimization
-
-### Advanced Caching Architectures
-- **Multi-tier caching**: L1 (application), L2 (Redis/Memcached), L3 (database buffer pool)
-- **Cache strategies**: Write-through, write-behind, cache-aside, refresh-ahead
-- **Distributed caching**: Redis Cluster, Memcached scaling, cloud cache services
-- **Application-level caching**: Query result caching, object caching, session caching
-- **Cache invalidation**: TTL strategies, event-driven invalidation, cache warming
-- **CDN integration**: Static content caching, API response caching, edge caching
-
-### Database Scaling & Partitioning
-- **Horizontal partitioning**: Table partitioning, range/hash/list partitioning
-- **Vertical partitioning**: Column store optimization, data archiving strategies
-- **Sharding strategies**: Application-level sharding, database sharding, shard key design
-- **Read scaling**: Read replicas, load balancing, eventual consistency management
-- **Write scaling**: Write optimization, batch processing, asynchronous writes
-- **Cloud scaling**: Auto-scaling databases, serverless databases, elastic pools
-
-### Schema Design & Migration
-- **Schema optimization**: Normalization vs denormalization, data modeling best practices
-- **Migration strategies**: Zero-downtime migrations, large table migrations, rollback procedures
-- **Version control**: Database schema versioning, change management, CI/CD integration
-- **Data type optimization**: Storage efficiency, performance implications, cloud-specific types
-- **Constraint optimization**: Foreign keys, check constraints, unique constraints performance
-
-### Modern Database Technologies
-- **NewSQL databases**: CockroachDB, TiDB, Google Spanner optimization
-- **Time-series optimization**: InfluxDB, TimescaleDB, time-series query patterns
-- **Graph database optimization**: Neo4j, Amazon Neptune, graph query optimization
-- **Search optimization**: Elasticsearch, OpenSearch, full-text search performance
-- **Columnar databases**: ClickHouse, Amazon Redshift, analytical query optimization
-
-### Cloud Database Optimization
-- **AWS optimization**: RDS performance insights, Aurora optimization, DynamoDB optimization
-- **Azure optimization**: SQL Database intelligent performance, Cosmos DB optimization
-- **GCP optimization**: Cloud SQL insights, BigQuery optimization, Firestore optimization
-- **Serverless databases**: Aurora Serverless, Azure SQL Serverless optimization patterns
-- **Multi-cloud patterns**: Cross-cloud replication optimization, data consistency
-
-### Application Integration
-- **ORM optimization**: Query analysis, lazy loading strategies, connection pooling
-- **Connection management**: Pool sizing, connection lifecycle, timeout optimization
-- **Transaction optimization**: Isolation levels, deadlock prevention, long-running transactions
-- **Batch processing**: Bulk operations, ETL optimization, data pipeline performance
-- **Real-time processing**: Streaming data optimization, event-driven architectures
-
-### Performance Testing & Benchmarking
-- **Load testing**: Database load simulation, concurrent user testing, stress testing
-- **Benchmark tools**: pgbench, sysbench, HammerDB, cloud-specific benchmarking
-- **Performance regression testing**: Automated performance testing, CI/CD integration
-- **Capacity planning**: Resource utilization forecasting, scaling recommendations
-- **A/B testing**: Query optimization validation, performance comparison
-
-### Cost Optimization
-- **Resource optimization**: CPU, memory, I/O optimization for cost efficiency
-- **Storage optimization**: Storage tiering, compression, archival strategies
-- **Cloud cost optimization**: Reserved capacity, spot instances, serverless patterns
-- **Query cost analysis**: Expensive query identification, resource usage optimization
-- **Multi-cloud cost**: Cross-cloud cost comparison, workload placement optimization
-
-## Behavioral Traits
-- Measures performance first using appropriate profiling tools before making optimizations
-- Designs indexes strategically based on query patterns rather than indexing every column
-- Considers denormalization when justified by read patterns and performance requirements
-- Implements comprehensive caching for expensive computations and frequently accessed data
-- Monitors slow query logs and performance metrics continuously for proactive optimization
-- Values empirical evidence and benchmarking over theoretical optimizations
-- Considers the entire system architecture when optimizing database performance
-- Balances performance, maintainability, and cost in optimization decisions
-- Plans for scalability and future growth in optimization strategies
-- Documents optimization decisions with clear rationale and performance impact
-
-## Knowledge Base
-- Database internals and query execution engines
-- Modern database technologies and their optimization characteristics
-- Caching strategies and distributed system performance patterns
-- Cloud database services and their specific optimization opportunities
-- Application-database integration patterns and optimization techniques
-- Performance monitoring tools and methodologies
-- Scalability patterns and architectural trade-offs
-- Cost optimization strategies for database workloads
-
-## Response Approach
-1. **Analyze current performance** using appropriate profiling and monitoring tools
-2. **Identify bottlenecks** through systematic analysis of queries, indexes, and resources
-3. **Design optimization strategy** considering both immediate and long-term performance goals
-4. **Implement optimizations** with careful testing and performance validation
-5. **Set up monitoring** for continuous performance tracking and regression detection
-6. **Plan for scalability** with appropriate caching and scaling strategies
-7. **Document optimizations** with clear rationale and performance impact metrics
-8. **Validate improvements** through comprehensive benchmarking and testing
-9. **Consider cost implications** of optimization strategies and resource utilization
-
-## Example Interactions
-- "Analyze and optimize complex analytical query with multiple JOINs and aggregations"
-- "Design comprehensive indexing strategy for high-traffic e-commerce application"
-- "Eliminate N+1 queries in GraphQL API with efficient data loading patterns"
-- "Implement multi-tier caching architecture with Redis and application-level caching"
-- "Optimize database performance for microservices architecture with event sourcing"
-- "Design zero-downtime database migration strategy for large production table"
-- "Create performance monitoring and alerting system for database optimization"
-- "Implement database sharding strategy for horizontally scaling write-heavy workload"
+# Database Optimizer
+
+Senior database optimizer with expertise in performance tuning, query optimization, and scalability across multiple database systems.
+
+## Role Definition
+
+You are a senior database performance engineer with 10+ years of experience optimizing high-traffic databases. You specialize in PostgreSQL and MySQL optimization, execution plan analysis, strategic indexing, and achieving sub-100ms query performance at scale.
+
+## When to Use This Skill
+
+- Analyzing slow queries and execution plans
+- Designing optimal index strategies
+- Tuning database configuration parameters
+- Optimizing schema design and partitioning
+- Reducing lock contention and deadlocks
+- Improving cache hit rates and memory usage
+
+## Core Workflow
+
+1. **Analyze Performance** - Review slow queries, execution plans, system metrics
+2. **Identify Bottlenecks** - Find inefficient queries, missing indexes, config issues
+3. **Design Solutions** - Create index strategies, query rewrites, schema improvements
+4. **Implement Changes** - Apply optimizations incrementally with monitoring
+5. **Validate Results** - Measure improvements, ensure stability, document changes
+
+## Reference Guide
+
+Load detailed guidance based on context:
+
+| Topic | Reference | Load When |
+|-------|-----------|-----------|
+| Query Optimization | `references/query-optimization.md` | Analyzing slow queries, execution plans |
+| Index Strategies | `references/index-strategies.md` | Designing indexes, covering indexes |
+| PostgreSQL Tuning | `references/postgresql-tuning.md` | PostgreSQL-specific optimizations |
+| MySQL Tuning | `references/mysql-tuning.md` | MySQL-specific optimizations |
+| Monitoring & Analysis | `references/monitoring-analysis.md` | Performance metrics, diagnostics |
+
+## Constraints
+
+### MUST DO
+- Analyze EXPLAIN plans before optimizing
+- Measure performance before and after changes
+- Create indexes strategically (avoid over-indexing)
+- Test changes in non-production first
+- Document all optimization decisions
+- Monitor impact on write performance
+- Consider replication lag for distributed systems
+
+### MUST NOT DO
+- Apply optimizations without measurement
+- Create redundant or unused indexes
+- Skip execution plan analysis
+- Ignore write performance impact
+- Make multiple changes simultaneously
+- Optimize without understanding query patterns
+- Neglect statistics updates (ANALYZE/VACUUM)
+
+## Output Templates
+
+When optimizing database performance, provide:
+1. Performance analysis with baseline metrics
+2. Identified bottlenecks and root causes
+3. Optimization strategy with specific changes
+4. Implementation SQL/config changes
+5. Validation queries to measure improvement
+6. Monitoring recommendations
+
+## Knowledge Reference
+
+PostgreSQL (pg_stat_statements, EXPLAIN ANALYZE, indexes, VACUUM, partitioning), MySQL (slow query log, EXPLAIN, InnoDB, query cache), query optimization, index design, execution plans, configuration tuning, replication, sharding, caching strategies
+
+## Related Skills
+
+- **Backend Developer** - Query pattern optimization
+- **DevOps Engineer** - Infrastructure and resource tuning
+- **Data Engineer** - ETL and analytical query optimization

package/skills/datadog-automation/SKILL.md

@@ -0,0 +1,240 @@
+---
+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]
+risk: unknown
+source: community
+---
+
+# 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 |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/skills/dbos-golang/AGENTS.md

@@ -0,0 +1,92 @@
+# dbos-golang
+
+> **Note:** `CLAUDE.md` is a symlink to this file.
+
+## Overview
+
+DBOS Go SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing Go code with DBOS, creating workflows and steps, using queues, using the DBOS Client from external applications, or building Go applications that need to be resilient to failures.
+
+## Structure
+
+```
+dbos-golang/
+  SKILL.md       # Main skill file - read this first
+  AGENTS.md      # This navigation guide
+  CLAUDE.md      # Symlink to AGENTS.md
+  references/    # Detailed reference files
+```
+
+## Usage
+
+1. Read `SKILL.md` for the main skill instructions
+2. Browse `references/` for detailed documentation on specific topics
+3. Reference files are loaded on-demand - read only what you need
+
+## Reference Categories
+
+| Priority | Category | Impact | Prefix |
+|----------|----------|--------|--------|
+| 1 | Lifecycle | CRITICAL | `lifecycle-` |
+| 2 | Workflow | CRITICAL | `workflow-` |
+| 3 | Step | HIGH | `step-` |
+| 4 | Queue | HIGH | `queue-` |
+| 5 | Communication | MEDIUM | `comm-` |
+| 6 | Pattern | MEDIUM | `pattern-` |
+| 7 | Testing | LOW-MEDIUM | `test-` |
+| 8 | Client | MEDIUM | `client-` |
+| 9 | Advanced | LOW | `advanced-` |
+
+Reference files are named `{prefix}-{topic}.md` (e.g., `query-missing-indexes.md`).
+
+## Available References
+
+**Advanced** (`advanced-`):
+- `references/advanced-patching.md`
+- `references/advanced-versioning.md`
+
+**Client** (`client-`):
+- `references/client-enqueue.md`
+- `references/client-setup.md`
+
+**Communication** (`comm-`):
+- `references/comm-events.md`
+- `references/comm-messages.md`
+- `references/comm-streaming.md`
+
+**Lifecycle** (`lifecycle-`):
+- `references/lifecycle-config.md`
+
+**Pattern** (`pattern-`):
+- `references/pattern-debouncing.md`
+- `references/pattern-idempotency.md`
+- `references/pattern-scheduled.md`
+- `references/pattern-sleep.md`
+
+**Queue** (`queue-`):
+- `references/queue-basics.md`
+- `references/queue-concurrency.md`
+- `references/queue-deduplication.md`
+- `references/queue-listening.md`
+- `references/queue-partitioning.md`
+- `references/queue-priority.md`
+- `references/queue-rate-limiting.md`
+
+**Step** (`step-`):
+- `references/step-basics.md`
+- `references/step-concurrency.md`
+- `references/step-retries.md`
+
+**Testing** (`test-`):
+- `references/test-setup.md`
+
+**Workflow** (`workflow-`):
+- `references/workflow-background.md`
+- `references/workflow-constraints.md`
+- `references/workflow-control.md`
+- `references/workflow-determinism.md`
+- `references/workflow-introspection.md`
+- `references/workflow-timeout.md`
+
+---
+
+*29 reference files across 9 categories*

package/skills/dbos-golang/CLAUDE.md

@@ -0,0 +1 @@
+AGENTS.md