@ngxtm/devkit 3.15.0 → 3.17.0

package/merged-commands/slo-implementation.md

@@ -1,6 +1,8 @@
 ---
 name: slo-implementation
-description: Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or measuring service performance.
+description: "Define and implement Service Level Indicators (SLIs) and Service Level Objectives (SLOs) with error budgets and alerting. Use when establishing reliability targets, implementing SRE practices, or m..."
+risk: unknown
+source: community
 ---
 
 # SLO Implementation

package/merged-commands/smtp-penetration-testing.md

@@ -1,9 +1,11 @@
 ---
-name: SMTP Penetration Testing
-description: This skill should be used when the user asks to "perform SMTP penetration testing", "enumerate email users", "test for open mail relays", "grab SMTP banners", "brute force email credentials", or "assess mail server security". It provides comprehensive techniques for testing SMTP server security.
+name: smtp-penetration-testing
+description: "This skill should be used when the user asks to \"perform SMTP penetration testing\", \"enumerate email users\", \"test for open mail relays\", \"grab SMTP banners\", \"brute force email cre..."
 metadata:
   author: zebbern
   version: "1.1"
+risk: unknown
+source: community
 ---
 
 # SMTP Penetration Testing
@@ -498,3 +500,6 @@ nmap -p 25 --script smtp-open-relay --script-args smtp-open-relay.from=test@atta
 8. **Log Monitoring** - Alert on suspicious activity
 9. **Patch Management** - Keep SMTP software updated
 10. **Access Controls** - Restrict SMTP to authorized IPs
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/social-content.md

@@ -1,6 +1,8 @@
 ---
 name: social-content
-description: "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' or 'viral content.' This skill covers content creation, repurposing, and platform-specific strategies."
+description: "When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn..."
+risk: unknown
+source: community
 ---
 
 # Social Content
@@ -805,3 +807,6 @@ If you need more context:
 - **launch-strategy**: For coordinating social with launches
 - **email-sequence**: For nurturing social audience via email
 - **marketing-psychology**: For understanding what drives engagement
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/software-architecture.md

@@ -1,6 +1,8 @@
 ---
 name: software-architecture
-description: Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
+description: "Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development."
+risk: unknown
+source: community
 ---
 
 # Software Architecture Development Skill
@@ -73,3 +75,6 @@ This skill provides guidance for quality focused software development and archit
 - Avoid deep nesting (max 3 levels)
 - Keep functions focused and under 50 lines when possible
 - Keep files focused and under 200 lines of code when possible
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/solidity-security.md

@@ -1,6 +1,8 @@
 ---
 name: solidity-security
-description: Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementing security measures for blockchain applications.
+description: "Master smart contract security best practices to prevent common vulnerabilities and implement secure Solidity patterns. Use when writing smart contracts, auditing existing contracts, or implementin..."
+risk: unknown
+source: community
 ---
 
 # Solidity Security

package/merged-commands/spark-optimization.md

@@ -1,6 +1,8 @@
 ---
 name: spark-optimization
-description: Optimize Apache Spark jobs with partitioning, caching, shuffle optimization, and memory tuning. Use when improving Spark performance, debugging slow jobs, or scaling data processing pipelines.
+description: "Optimize Apache Spark jobs with partitioning, caching, shuffle optimization, and memory tuning. Use when improving Spark performance, debugging slow jobs, or scaling data processing pipelines."
+risk: unknown
+source: community
 ---
 
 # Apache Spark Optimization

package/merged-commands/sql-injection-testing.md

@@ -1,9 +1,11 @@
 ---
-name: SQL Injection Testing
-description: This skill should be used when the user asks to "test for SQL injection vulnerabilities", "perform SQLi attacks", "bypass authentication using SQL injection", "extract database information through injection", "detect SQL injection flaws", or "exploit database query vulnerabilities". It provides comprehensive techniques for identifying, exploiting, and understanding SQL injection attack vectors across different database systems.
+name: sql-injection-testing
+description: "This skill should be used when the user asks to \"test for SQL injection vulnerabilities\", \"perform SQLi attacks\", \"bypass authentication using SQL injection\", \"extract database inform..."
 metadata:
   author: zebbern
   version: "1.1"
+risk: unknown
+source: community
 ---
 
 # SQL Injection Testing
@@ -446,3 +448,6 @@ SELECT * FROM users WHERE username='administrator'--' AND password='anything'
 - Use longer delays (10+ seconds) for clarity
 - Run multiple tests to confirm pattern
 - Consider server-side caching effects
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/sql-optimization-patterns.md

@@ -1,6 +1,8 @@
 ---
 name: sql-optimization-patterns
-description: Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.
+description: "Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database..."
+risk: unknown
+source: community
 ---
 
 # SQL Optimization Patterns

package/merged-commands/sql-pro.md

@@ -1,173 +1,97 @@
 ---
 name: sql-pro
-description: Master modern SQL with cloud-native databases, OLTP/OLAP
-  optimization, and advanced query techniques. Expert in performance tuning,
-  data modeling, and hybrid analytical systems. Use PROACTIVELY for database
-  optimization or complex analysis.
-metadata:
-  model: inherit
+description: Use when optimizing SQL queries, designing database schemas, or tuning database performance. Invoke for complex queries, window functions, CTEs, indexing strategies, query plan analysis.
+triggers:
+  - SQL optimization
+  - query performance
+  - database design
+  - PostgreSQL
+  - MySQL
+  - SQL Server
+  - window functions
+  - CTEs
+  - query tuning
+  - EXPLAIN plan
+  - database indexing
+role: specialist
+scope: implementation
+output-format: code
 ---
-You are an expert SQL specialist mastering modern database systems, performance optimization, and advanced analytical techniques across cloud-native and hybrid OLTP/OLAP environments.
-
-## Use this skill when
-
-- Writing complex SQL queries or analytics
-- Tuning query performance with indexes or plans
-- Designing SQL patterns for OLTP/OLAP workloads
-
-## Do not use this skill when
-
-- You only need ORM-level guidance
-- The system is non-SQL or document-only
-- You cannot access query plans or schema details
-
-## Instructions
-
-1. Define query goals, constraints, and expected outputs.
-2. Inspect schema, statistics, and access paths.
-3. Optimize queries and validate with EXPLAIN.
-4. Verify correctness and performance under load.
-
-## Safety
-
-- Avoid heavy queries on production without safeguards.
-- Use read replicas or limits for exploratory analysis.
-
-## Purpose
-Expert SQL professional focused on high-performance database systems, advanced query optimization, and modern data architecture. Masters cloud-native databases, hybrid transactional/analytical processing (HTAP), and cutting-edge SQL techniques to deliver scalable and efficient data solutions for enterprise applications.
-
-## Capabilities
-
-### Modern Database Systems and Platforms
-- Cloud-native databases: Amazon Aurora, Google Cloud SQL, Azure SQL Database
-- Data warehouses: Snowflake, Google BigQuery, Amazon Redshift, Databricks
-- Hybrid OLTP/OLAP systems: CockroachDB, TiDB, MemSQL, VoltDB
-- NoSQL integration: MongoDB, Cassandra, DynamoDB with SQL interfaces
-- Time-series databases: InfluxDB, TimescaleDB, Apache Druid
-- Graph databases: Neo4j, Amazon Neptune with Cypher/Gremlin
-- Modern PostgreSQL features and extensions
-
-### Advanced Query Techniques and Optimization
-- Complex window functions and analytical queries
-- Recursive Common Table Expressions (CTEs) for hierarchical data
-- Advanced JOIN techniques and optimization strategies
-- Query plan analysis and execution optimization
-- Parallel query processing and partitioning strategies
-- Statistical functions and advanced aggregations
-- JSON/XML data processing and querying
-
-### Performance Tuning and Optimization
-- Comprehensive index strategy design and maintenance
-- Query execution plan analysis and optimization
-- Database statistics management and auto-updating
-- Partitioning strategies for large tables and time-series data
-- Connection pooling and resource management optimization
-- Memory configuration and buffer pool tuning
-- I/O optimization and storage considerations
-
-### Cloud Database Architecture
-- Multi-region database deployment and replication strategies
-- Auto-scaling configuration and performance monitoring
-- Cloud-native backup and disaster recovery planning
-- Database migration strategies to cloud platforms
-- Serverless database configuration and optimization
-- Cross-cloud database integration and data synchronization
-- Cost optimization for cloud database resources
-
-### Data Modeling and Schema Design
-- Advanced normalization and denormalization strategies
-- Dimensional modeling for data warehouses and OLAP systems
-- Star schema and snowflake schema implementation
-- Slowly Changing Dimensions (SCD) implementation
-- Data vault modeling for enterprise data warehouses
-- Event sourcing and CQRS pattern implementation
-- Microservices database design patterns
-
-### Modern SQL Features and Syntax
-- ANSI SQL 2016+ features including row pattern recognition
-- Database-specific extensions and advanced features
-- JSON and array processing capabilities
-- Full-text search and spatial data handling
-- Temporal tables and time-travel queries
-- User-defined functions and stored procedures
-- Advanced constraints and data validation
-
-### Analytics and Business Intelligence
-- OLAP cube design and MDX query optimization
-- Advanced statistical analysis and data mining queries
-- Time-series analysis and forecasting queries
-- Cohort analysis and customer segmentation
-- Revenue recognition and financial calculations
-- Real-time analytics and streaming data processing
-- Machine learning integration with SQL
-
-### Database Security and Compliance
-- Row-level security and column-level encryption
-- Data masking and anonymization techniques
-- Audit trail implementation and compliance reporting
-- Role-based access control and privilege management
-- SQL injection prevention and secure coding practices
-- GDPR and data privacy compliance implementation
-- Database vulnerability assessment and hardening
-
-### DevOps and Database Management
-- Database CI/CD pipeline design and implementation
-- Schema migration strategies and version control
-- Database testing and validation frameworks
-- Monitoring and alerting for database performance
-- Automated backup and recovery procedures
-- Database deployment automation and configuration management
-- Performance benchmarking and load testing
-
-### Integration and Data Movement
-- ETL/ELT process design and optimization
-- Real-time data streaming and CDC implementation
-- API integration and external data source connectivity
-- Cross-database queries and federation
-- Data lake and data warehouse integration
-- Microservices data synchronization patterns
-- Event-driven architecture with database triggers
-
-## Behavioral Traits
-- Focuses on performance and scalability from the start
-- Writes maintainable and well-documented SQL code
-- Considers both read and write performance implications
-- Applies appropriate indexing strategies based on usage patterns
-- Implements proper error handling and transaction management
-- Follows database security and compliance best practices
-- Optimizes for both current and future data volumes
-- Balances normalization with performance requirements
-- Uses modern SQL features when appropriate for readability
-- Tests queries thoroughly with realistic data volumes
-
-## Knowledge Base
-- Modern SQL standards and database-specific extensions
-- Cloud database platforms and their unique features
-- Query optimization techniques and execution plan analysis
-- Data modeling methodologies and design patterns
-- Database security and compliance frameworks
-- Performance monitoring and tuning strategies
-- Modern data architecture patterns and best practices
-- OLTP vs OLAP system design considerations
-- Database DevOps and automation tools
-- Industry-specific database requirements and solutions
-
-## Response Approach
-1. **Analyze requirements** and identify optimal database approach
-2. **Design efficient schema** with appropriate data types and constraints
-3. **Write optimized queries** using modern SQL techniques
-4. **Implement proper indexing** based on usage patterns
-5. **Test performance** with realistic data volumes
-6. **Document assumptions** and provide maintenance guidelines
-7. **Consider scalability** for future data growth
-8. **Validate security** and compliance requirements
-
-## Example Interactions
-- "Optimize this complex analytical query for a billion-row table in Snowflake"
-- "Design a database schema for a multi-tenant SaaS application with GDPR compliance"
-- "Create a real-time dashboard query that updates every second with minimal latency"
-- "Implement a data migration strategy from Oracle to cloud-native PostgreSQL"
-- "Build a cohort analysis query to track customer retention over time"
-- "Design an HTAP system that handles both transactions and analytics efficiently"
-- "Create a time-series analysis query for IoT sensor data in TimescaleDB"
-- "Optimize database performance for a high-traffic e-commerce platform"
+
+# SQL Pro
+
+Senior SQL developer with mastery across major database systems, specializing in complex query design, performance optimization, and database architecture.
+
+## Role Definition
+
+You are a senior SQL developer with 10+ years of experience across PostgreSQL, MySQL, SQL Server, and Oracle. You specialize in complex query optimization, advanced SQL patterns (CTEs, window functions, recursive queries), indexing strategies, and performance tuning. You build efficient, scalable database solutions with sub-100ms query targets.
+
+## When to Use This Skill
+
+- Optimizing slow queries and execution plans
+- Designing complex queries with CTEs, window functions, recursive patterns
+- Creating and optimizing database indexes
+- Implementing data warehousing and ETL patterns
+- Migrating queries between database platforms
+- Analyzing and tuning database performance
+
+## Core Workflow
+
+1. **Schema Analysis** - Review database structure, indexes, query patterns, performance bottlenecks
+2. **Design** - Create set-based operations using CTEs, window functions, appropriate joins
+3. **Optimize** - Analyze execution plans, implement covering indexes, eliminate table scans
+4. **Verify** - Test with production data volume, ensure linear scalability, confirm sub-100ms targets
+5. **Document** - Provide query explanations, index rationale, performance metrics
+
+## Reference Guide
+
+Load detailed guidance based on context:
+
+| Topic | Reference | Load When |
+|-------|-----------|-----------|
+| Query Patterns | `references/query-patterns.md` | JOINs, CTEs, subqueries, recursive queries |
+| Window Functions | `references/window-functions.md` | ROW_NUMBER, RANK, LAG/LEAD, analytics |
+| Optimization | `references/optimization.md` | EXPLAIN plans, indexes, statistics, tuning |
+| Database Design | `references/database-design.md` | Normalization, keys, constraints, schemas |
+| Dialect Differences | `references/dialect-differences.md` | PostgreSQL vs MySQL vs SQL Server specifics |
+
+## Constraints
+
+### MUST DO
+- Analyze execution plans before optimization
+- Use set-based operations over row-by-row processing
+- Apply filtering early in query execution
+- Use EXISTS over COUNT for existence checks
+- Handle NULLs explicitly
+- Create covering indexes for frequent queries
+- Test with production-scale data volumes
+- Document query intent and performance targets
+
+### MUST NOT DO
+- Use SELECT * in production queries
+- Create queries without analyzing execution plans
+- Ignore index usage and table scans
+- Use cursors when set-based operations work
+- Skip NULL handling in comparisons
+- Implement solutions without considering data volume
+- Ignore platform-specific optimizations
+- Leave queries undocumented
+
+## Output Templates
+
+When implementing SQL solutions, provide:
+1. Optimized query with inline comments
+2. Required indexes with rationale
+3. Execution plan analysis
+4. Performance metrics (before/after)
+5. Platform-specific notes if applicable
+
+## Knowledge Reference
+
+CTEs, window functions, recursive queries, EXPLAIN/ANALYZE, covering indexes, query hints, partitioning, materialized views, OLAP patterns, star schema, slowly changing dimensions, isolation levels, deadlock prevention, temporal tables, JSONB operations
+
+## Related Skills
+
+- **Backend Developer** - Optimize application-level database queries
+- **Data Engineer** - ETL patterns and data pipeline optimization
+- **DevOps Engineer** - Database monitoring and performance dashboards

package/merged-commands/sqlmap-database-pentesting.md

@@ -1,9 +1,11 @@
 ---
-name: SQLMap Database Penetration Testing
-description: This skill should be used when the user asks to "automate SQL injection testing," "enumerate database structure," "extract database credentials using sqlmap," "dump tables and columns from a vulnerable database," or "perform automated database penetration testing." It provides comprehensive guidance for using SQLMap to detect and exploit SQL injection vulnerabilities.
+name: sqlmap-database-pentesting
+description: "This skill should be used when the user asks to \"automate SQL injection testing,\" \"enumerate database structure,\" \"extract database credentials using sqlmap,\" \"dump tables and columns..."
 metadata:
   author: zebbern
   version: "1.1"
+risk: unknown
+source: community
 ---
 
 # SQLMap Database Penetration Testing
@@ -398,3 +400,6 @@ sqlmap -u "URL" --dbs --batch --resume
 # Use persistent HTTP connection
 sqlmap -u "URL" --dbs --batch --keep-alive
 ```
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/square-automation.md

@@ -0,0 +1,181 @@
+---
+name: square-automation
+description: "Automate Square tasks via Rube MCP (Composio): payments, orders, invoices, locations. Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+risk: unknown
+source: community
+---
+
+# Square Automation via Rube MCP
+
+Automate Square payment processing, order management, and invoicing through Composio's Square toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Square connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `square`
+- 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 `square`
+3. If connection is not ACTIVE, follow the returned auth link to complete Square OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. List and Monitor Payments
+
+**When to use**: User wants to view payment history or check payment status
+
+**Tool sequence**:
+1. `SQUARE_LIST_PAYMENTS` - Retrieve payments with optional filters [Required]
+2. `SQUARE_CANCEL_PAYMENT` - Cancel a pending payment if needed [Optional]
+
+**Key parameters**:
+- `begin_time` / `end_time`: RFC 3339 timestamps for date range filtering
+- `sort_order`: 'ASC' or 'DESC' for chronological ordering
+- `cursor`: Pagination cursor from previous response
+- `location_id`: Filter payments by specific location
+
+**Pitfalls**:
+- Timestamps must be RFC 3339 format (e.g., '2024-01-01T00:00:00Z')
+- Pagination required for large result sets; follow `cursor` until absent
+- Only pending payments can be cancelled; completed payments require refunds
+- `SQUARE_CANCEL_PAYMENT` requires exact `payment_id` from list results
+
+### 2. Search and Manage Orders
+
+**When to use**: User wants to find orders by criteria or update order details
+
+**Tool sequence**:
+1. `SQUARE_LIST_LOCATIONS` - Get location IDs for filtering [Prerequisite]
+2. `SQUARE_SEARCH_ORDERS` - Search orders with filters [Required]
+3. `SQUARE_RETRIEVE_ORDER` - Get full details of a specific order [Optional]
+4. `SQUARE_UPDATE_ORDER` - Modify order state or details [Optional]
+
+**Key parameters**:
+- `location_ids`: Array of location IDs to search within (required for search)
+- `query`: Search filter object with date ranges, states, fulfillment types
+- `order_id`: Specific order ID for retrieve/update operations
+- `cursor`: Pagination cursor for search results
+
+**Pitfalls**:
+- `location_ids` is required for SEARCH_ORDERS; get IDs from LIST_LOCATIONS first
+- Order states include: OPEN, COMPLETED, CANCELED, DRAFT
+- UPDATE_ORDER requires the current `version` field to prevent conflicts
+- Search results are paginated; follow `cursor` until absent
+
+### 3. Manage Locations
+
+**When to use**: User wants to view business locations or get location details
+
+**Tool sequence**:
+1. `SQUARE_LIST_LOCATIONS` - List all business locations [Required]
+
+**Key parameters**:
+- No required parameters; returns all accessible locations
+- Response includes `id`, `name`, `address`, `status`, `timezone`
+
+**Pitfalls**:
+- Location IDs are required for most other Square operations (orders, payments)
+- Always cache location IDs after first retrieval to avoid redundant calls
+- Inactive locations may still appear in results; check `status` field
+
+### 4. Invoice Management
+
+**When to use**: User wants to list, view, or cancel invoices
+
+**Tool sequence**:
+1. `SQUARE_LIST_LOCATIONS` - Get location ID for filtering [Prerequisite]
+2. `SQUARE_LIST_INVOICES` - List invoices for a location [Required]
+3. `SQUARE_GET_INVOICE` - Get detailed invoice information [Optional]
+4. `SQUARE_CANCEL_INVOICE` - Cancel a scheduled or unpaid invoice [Optional]
+
+**Key parameters**:
+- `location_id`: Required for listing invoices
+- `invoice_id`: Required for get/cancel operations
+- `cursor`: Pagination cursor for list results
+- `limit`: Number of results per page
+
+**Pitfalls**:
+- `location_id` is required for LIST_INVOICES; resolve via LIST_LOCATIONS first
+- Only SCHEDULED, UNPAID, or PARTIALLY_PAID invoices can be cancelled
+- CANCEL_INVOICE requires the invoice `version` to prevent race conditions
+- Cancelled invoices cannot be uncancelled
+
+## Common Patterns
+
+### ID Resolution
+
+**Location name -> Location ID**:
+```
+1. Call SQUARE_LIST_LOCATIONS
+2. Find location by name in response
+3. Extract id field (e.g., 'L1234ABCD')
+```
+
+**Order lookup**:
+```
+1. Call SQUARE_SEARCH_ORDERS with location_ids and query filters
+2. Extract order_id from results
+3. Use order_id for RETRIEVE_ORDER or UPDATE_ORDER
+```
+
+### Pagination
+
+- Check response for `cursor` field
+- Pass cursor value in next request's `cursor` parameter
+- Continue until `cursor` is absent or empty
+- Use `limit` to control page size
+
+### Date Range Filtering
+
+- Use RFC 3339 format: `2024-01-01T00:00:00Z`
+- For payments: `begin_time` and `end_time` parameters
+- For orders: Use query filter with date_time_filter
+- All timestamps are in UTC
+
+## Known Pitfalls
+
+**ID Formats**:
+- Location IDs are alphanumeric strings (e.g., 'L1234ABCD')
+- Payment IDs and Order IDs are longer alphanumeric strings
+- Always resolve location names to IDs before other operations
+
+**Versioning**:
+- UPDATE_ORDER and CANCEL_INVOICE require current `version` field
+- Fetch the resource first to get its current version
+- Version mismatch returns a 409 Conflict error
+
+**Rate Limits**:
+- Square API has per-endpoint rate limits
+- Implement backoff for bulk operations
+- Pagination should include brief delays for large datasets
+
+**Response Parsing**:
+- Responses may nest data under `data` key
+- Money amounts are in smallest currency unit (cents for USD)
+- Parse defensively with fallbacks for optional fields
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List payments | SQUARE_LIST_PAYMENTS | begin_time, end_time, location_id, cursor |
+| Cancel payment | SQUARE_CANCEL_PAYMENT | payment_id |
+| Search orders | SQUARE_SEARCH_ORDERS | location_ids, query, cursor |
+| Get order | SQUARE_RETRIEVE_ORDER | order_id |
+| Update order | SQUARE_UPDATE_ORDER | order_id, version |
+| List locations | SQUARE_LIST_LOCATIONS | (none) |
+| List invoices | SQUARE_LIST_INVOICES | location_id, cursor |
+| Get invoice | SQUARE_GET_INVOICE | invoice_id |
+| Cancel invoice | SQUARE_CANCEL_INVOICE | invoice_id, version |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/ssh-penetration-testing.md

@@ -1,9 +1,11 @@
 ---
-name: SSH Penetration Testing
-description: This skill should be used when the user asks to "pentest SSH services", "enumerate SSH configurations", "brute force SSH credentials", "exploit SSH vulnerabilities", "perform SSH tunneling", or "audit SSH security". It provides comprehensive SSH penetration testing methodologies and techniques.
+name: ssh-penetration-testing
+description: "This skill should be used when the user asks to \"pentest SSH services\", \"enumerate SSH configurations\", \"brute force SSH credentials\", \"exploit SSH vulnerabilities\", \"perform SSH tu..."
 metadata:
   author: zebbern
   version: "1.1"
+risk: unknown
+source: community
 ---
 
 # SSH Penetration Testing
@@ -486,3 +488,6 @@ sessions -i 1
 | Connection Refused | Verify SSH running; check firewall; confirm port; test from different IP |
 | Authentication Failures | Verify username; check password policy; key permissions (600); authorized_keys format |
 | Tunnel Not Working | Check GatewayPorts/AllowTcpForwarding in sshd_config; verify firewall; use `ssh -v` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/startup-analyst.md

@@ -1,6 +1,6 @@
 ---
 name: startup-analyst
-description: Expert startup business analyst specializing in market sizing,
+description: "Expert startup business analyst specializing in market sizing,"
   financial modeling, competitive analysis, and strategic planning for
   early-stage companies. Use PROACTIVELY when the user asks about market
   opportunity, TAM/SAM/SOM, financial projections, unit economics, competitive
@@ -8,6 +8,8 @@ description: Expert startup business analyst specializing in market sizing,
   through Series A startups.
 metadata:
   model: inherit
+risk: unknown
+source: community
 ---
 
 ## Use this skill when

package/merged-commands/startup-business-analyst-business-case.md

@@ -1,8 +1,10 @@
 ---
 name: startup-business-analyst-business-case
-description: Generate comprehensive investor-ready business case document with
+description: "Generate comprehensive investor-ready business case document with"
   market, solution, financials, and strategy
 allowed-tools: Read Write Edit Glob Grep Bash WebSearch WebFetch
+risk: unknown
+source: community
 ---
 
 # Business Case Generator