@ngxtm/devkit 3.15.0 → 3.16.0

package/merged-commands/monday-automation.md

@@ -0,0 +1,238 @@
+---
+name: monday-automation
+description: "Automate Monday.com work management including boards, items, columns, groups, subitems, and updates via Rube MCP (Composio). Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+risk: unknown
+source: community
+---
+
+# Monday.com Automation via Rube MCP
+
+Automate Monday.com work management workflows including board creation, item management, column value updates, group organization, subitems, and update/comment threads through Composio's Monday toolkit.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Monday.com connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `monday`
+- 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 `monday`
+3. If connection is not ACTIVE, follow the returned auth link to complete Monday.com OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Manage Boards
+
+**When to use**: User wants to create a new board, list existing boards, or set up workspace structure.
+
+**Tool sequence**:
+1. `MONDAY_GET_WORKSPACES` - List available workspaces and resolve workspace ID [Prerequisite]
+2. `MONDAY_LIST_BOARDS` - List existing boards to check for duplicates [Optional]
+3. `MONDAY_CREATE_BOARD` - Create a new board with name, kind, and workspace [Required]
+4. `MONDAY_CREATE_COLUMN` - Add columns to the new board [Optional]
+5. `MONDAY_CREATE_GROUP` - Add groups to organize items [Optional]
+6. `MONDAY_BOARDS` - Retrieve detailed board metadata [Optional]
+
+**Key parameters**:
+- `board_name`: Name for the new board (required)
+- `board_kind`: "public", "private", or "share" (required)
+- `workspace_id`: Numeric workspace ID; omit for default workspace
+- `folder_id`: Folder ID; must be within `workspace_id` if both provided
+- `template_id`: ID of accessible template to clone
+
+**Pitfalls**:
+- `board_kind` is required and must be one of: "public", "private", "share"
+- If both `workspace_id` and `folder_id` are provided, the folder must exist within that workspace
+- `template_id` must reference a template the authenticated user can access
+- Board IDs are large integers; always use the exact value from API responses
+
+### 2. Create and Manage Items
+
+**When to use**: User wants to add tasks/items to a board, list existing items, or move items between groups.
+
+**Tool sequence**:
+1. `MONDAY_LIST_BOARDS` - Resolve board name to board ID [Prerequisite]
+2. `MONDAY_LIST_GROUPS` - List groups on the board to get group_id [Prerequisite]
+3. `MONDAY_LIST_COLUMNS` - Get column IDs and types for setting values [Prerequisite]
+4. `MONDAY_CREATE_ITEM` - Create a new item with name and column values [Required]
+5. `MONDAY_LIST_BOARD_ITEMS` - List all items on the board [Optional]
+6. `MONDAY_MOVE_ITEM_TO_GROUP` - Move an item to a different group [Optional]
+7. `MONDAY_ITEMS_PAGE` - Paginated item retrieval with filtering [Optional]
+
+**Key parameters**:
+- `board_id`: Board ID (required, integer)
+- `item_name`: Item name, max 256 characters (required)
+- `group_id`: Group ID string to place the item in (optional)
+- `column_values`: JSON object or string mapping column IDs to values
+
+**Pitfalls**:
+- `column_values` must use column IDs (not titles); get them from `MONDAY_LIST_COLUMNS`
+- Column value formats vary by type: status uses `{"index": 0}` or `{"label": "Done"}`, date uses `{"date": "YYYY-MM-DD"}`, people uses `{"personsAndTeams": [{"id": 123, "kind": "person"}]}`
+- `item_name` has a 256-character maximum
+- Subitem boards are NOT supported by `MONDAY_CREATE_ITEM`; use GraphQL via `MONDAY_CREATE_OBJECT`
+
+### 3. Update Item Column Values
+
+**When to use**: User wants to change status, date, text, or other column values on existing items.
+
+**Tool sequence**:
+1. `MONDAY_LIST_COLUMNS` or `MONDAY_COLUMNS` - Get column IDs and types [Prerequisite]
+2. `MONDAY_LIST_BOARD_ITEMS` or `MONDAY_ITEMS_PAGE` - Find the target item ID [Prerequisite]
+3. `MONDAY_CHANGE_SIMPLE_COLUMN_VALUE` - Update text, status, or dropdown with a string value [Required]
+4. `MONDAY_UPDATE_ITEM` - Update complex column types (timeline, people, date) with JSON [Required]
+
+**Key parameters for MONDAY_CHANGE_SIMPLE_COLUMN_VALUE**:
+- `board_id`: Board ID (integer, required)
+- `item_id`: Item ID (integer, required)
+- `column_id`: Column ID string (required)
+- `value`: Simple string value (e.g., "Done", "Working on it")
+- `create_labels_if_missing`: true to auto-create status/dropdown labels (default true)
+
+**Key parameters for MONDAY_UPDATE_ITEM**:
+- `board_id`: Board ID (integer, required)
+- `item_id`: Item ID (integer, required)
+- `column_id`: Column ID string (required)
+- `value`: JSON object matching the column type schema
+- `create_labels_if_missing`: false by default; set true for status/dropdown
+
+**Pitfalls**:
+- Use `MONDAY_CHANGE_SIMPLE_COLUMN_VALUE` for simple text/status/dropdown updates (string value)
+- Use `MONDAY_UPDATE_ITEM` for complex types like timeline, people, date (JSON value)
+- Column IDs are lowercase strings with underscores (e.g., "status_1", "date_2", "text"); get them from `MONDAY_LIST_COLUMNS`
+- Status values can be set by label name ("Done") or index number ("1")
+- `create_labels_if_missing` defaults differ: true for CHANGE_SIMPLE, false for UPDATE_ITEM
+
+### 4. Work with Groups and Board Structure
+
+**When to use**: User wants to organize items into groups, add columns, or inspect board structure.
+
+**Tool sequence**:
+1. `MONDAY_LIST_BOARDS` - Resolve board ID [Prerequisite]
+2. `MONDAY_LIST_GROUPS` - List all groups on a board [Required]
+3. `MONDAY_CREATE_GROUP` - Create a new group [Optional]
+4. `MONDAY_LIST_COLUMNS` or `MONDAY_COLUMNS` - Inspect column structure [Required]
+5. `MONDAY_CREATE_COLUMN` - Add a new column to the board [Optional]
+6. `MONDAY_MOVE_ITEM_TO_GROUP` - Reorganize items across groups [Optional]
+
+**Key parameters**:
+- `board_id`: Board ID (required for all group/column operations)
+- `group_name`: Name for new group (CREATE_GROUP)
+- `column_type`: Must be a valid GraphQL enum token in snake_case (e.g., "status", "text", "long_text", "numbers", "date", "dropdown", "people")
+- `title`: Column display title
+- `defaults`: JSON string for status/dropdown labels, e.g., `'{"labels": ["To Do", "In Progress", "Done"]}'`
+
+**Pitfalls**:
+- `column_type` must be exact snake_case values; "person" is NOT valid, use "people"
+- Group IDs are strings (e.g., "topics", "new_group_12345"), not integers
+- `MONDAY_COLUMNS` accepts an array of `board_ids` and returns column metadata including settings
+- `MONDAY_LIST_COLUMNS` is simpler and takes a single `board_id`
+
+### 5. Manage Subitems and Updates
+
+**When to use**: User wants to view subitems of a task or add comments/updates to items.
+
+**Tool sequence**:
+1. `MONDAY_LIST_BOARD_ITEMS` - Find parent item IDs [Prerequisite]
+2. `MONDAY_LIST_SUBITEMS_BY_PARENT` - Retrieve subitems with column values [Required]
+3. `MONDAY_CREATE_UPDATE` - Add a comment/update to an item [Optional]
+4. `MONDAY_CREATE_OBJECT` - Create subitems via GraphQL mutation [Optional]
+
+**Key parameters for MONDAY_LIST_SUBITEMS_BY_PARENT**:
+- `parent_item_ids`: Array of parent item IDs (integer array, required)
+- `include_column_values`: true to include column data (default true)
+- `include_parent_fields`: true to include parent item info (default true)
+
+**Key parameters for MONDAY_CREATE_OBJECT** (GraphQL):
+- `query`: Full GraphQL mutation string
+- `variables`: Optional variables object
+
+**Pitfalls**:
+- Subitems can only be queried through their parent items
+- To create subitems, use `MONDAY_CREATE_OBJECT` with a `create_subitem` GraphQL mutation
+- `MONDAY_CREATE_UPDATE` is for adding comments/updates to items (Monday's "updates" feature), not for modifying item values
+- `MONDAY_CREATE_OBJECT` is a raw GraphQL endpoint; ensure correct mutation syntax
+
+## Common Patterns
+
+### ID Resolution
+Always resolve display names to IDs before operations:
+- **Board name -> board_id**: `MONDAY_LIST_BOARDS` and match by name
+- **Group name -> group_id**: `MONDAY_LIST_GROUPS` with `board_id`
+- **Column title -> column_id**: `MONDAY_LIST_COLUMNS` with `board_id`
+- **Workspace name -> workspace_id**: `MONDAY_GET_WORKSPACES` and match by name
+- **Item name -> item_id**: `MONDAY_LIST_BOARD_ITEMS` or `MONDAY_ITEMS_PAGE`
+
+### Pagination
+Monday.com uses cursor-based pagination for items:
+- `MONDAY_ITEMS_PAGE` returns a `cursor` in the response for the next page
+- Pass the `cursor` to the next call; `board_id` and `query_params` are ignored when cursor is provided
+- Cursors are cached for 60 minutes
+- Maximum `limit` is 500 per page
+- `MONDAY_LIST_BOARDS` and `MONDAY_GET_WORKSPACES` use page-based pagination with `page` and `limit`
+
+### Column Value Formatting
+Different column types require different value formats:
+- **Status**: `{"index": 0}` or `{"label": "Done"}` or simple string "Done"
+- **Date**: `{"date": "YYYY-MM-DD"}`
+- **People**: `{"personsAndTeams": [{"id": 123, "kind": "person"}]}`
+- **Text/Numbers**: Plain string or number
+- **Timeline**: `{"from": "YYYY-MM-DD", "to": "YYYY-MM-DD"}`
+
+## Known Pitfalls
+
+### ID Formats
+- Board IDs and item IDs are large integers (e.g., 1234567890)
+- Group IDs are strings (e.g., "topics", "new_group_12345")
+- Column IDs are short strings (e.g., "status_1", "date4", "text")
+- Workspace IDs are integers
+
+### Rate Limits
+- Monday.com GraphQL API has complexity-based rate limits
+- Large boards with many columns increase query complexity
+- Use `limit` parameter to reduce items per request if hitting limits
+
+### Parameter Quirks
+- `column_type` for CREATE_COLUMN must be exact snake_case enum values; "people" not "person"
+- `column_values` in CREATE_ITEM accepts both JSON string and object formats
+- `MONDAY_CHANGE_SIMPLE_COLUMN_VALUE` auto-creates missing labels by default; `MONDAY_UPDATE_ITEM` does not
+- `MONDAY_CREATE_OBJECT` is a raw GraphQL interface; use it for operations without dedicated tools (e.g., create_subitem, delete_item, archive_board)
+
+### Response Structure
+- Board items are returned as arrays with `id`, `name`, and `state` fields
+- Column values include both raw `value` (JSON) and rendered `text` (display string)
+- Subitems are nested under parent items and cannot be queried independently
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List workspaces | `MONDAY_GET_WORKSPACES` | `kind`, `state`, `limit` |
+| Create workspace | `MONDAY_CREATE_WORKSPACE` | `name`, `kind` |
+| List boards | `MONDAY_LIST_BOARDS` | `limit`, `page`, `state` |
+| Create board | `MONDAY_CREATE_BOARD` | `board_name`, `board_kind`, `workspace_id` |
+| Get board metadata | `MONDAY_BOARDS` | `board_ids`, `board_kind` |
+| List groups | `MONDAY_LIST_GROUPS` | `board_id` |
+| Create group | `MONDAY_CREATE_GROUP` | `board_id`, `group_name` |
+| List columns | `MONDAY_LIST_COLUMNS` | `board_id` |
+| Get column metadata | `MONDAY_COLUMNS` | `board_ids`, `column_types` |
+| Create column | `MONDAY_CREATE_COLUMN` | `board_id`, `column_type`, `title` |
+| Create item | `MONDAY_CREATE_ITEM` | `board_id`, `item_name`, `column_values` |
+| List board items | `MONDAY_LIST_BOARD_ITEMS` | `board_id` |
+| Paginated items | `MONDAY_ITEMS_PAGE` | `board_id`, `limit`, `query_params` |
+| Update column (simple) | `MONDAY_CHANGE_SIMPLE_COLUMN_VALUE` | `board_id`, `item_id`, `column_id`, `value` |
+| Update column (complex) | `MONDAY_UPDATE_ITEM` | `board_id`, `item_id`, `column_id`, `value` |
+| Move item to group | `MONDAY_MOVE_ITEM_TO_GROUP` | `item_id`, `group_id` |
+| List subitems | `MONDAY_LIST_SUBITEMS_BY_PARENT` | `parent_item_ids` |
+| Add comment/update | `MONDAY_CREATE_UPDATE` | `item_id`, `body` |
+| Raw GraphQL mutation | `MONDAY_CREATE_OBJECT` | `query`, `variables` |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/monorepo-architect.md

@@ -1,6 +1,8 @@
 ---
 name: monorepo-architect
 description: "Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,"
+risk: unknown
+source: community
 ---
 
 # Monorepo Architect

package/merged-commands/monorepo-management.md

@@ -1,6 +1,8 @@
 ---
 name: monorepo-management
-description: Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
+description: "Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monor..."
+risk: unknown
+source: community
 ---
 
 # Monorepo Management

package/merged-commands/moodle-external-api-development.md

@@ -1,6 +1,8 @@
 ---
 name: moodle-external-api-development
-description: Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter validation, database operations, error handling, service registration, and Moodle coding standards.
+description: "Create custom external web service APIs for Moodle LMS. Use when implementing web services for course management, user tracking, quiz operations, or custom plugin functionality. Covers parameter va..."
+risk: unknown
+source: community
 ---
 
 # Moodle External API Development

package/merged-commands/mtls-configuration.md

@@ -1,6 +1,8 @@
 ---
 name: mtls-configuration
-description: Configure mutual TLS (mTLS) for zero-trust service-to-service communication. Use when implementing zero-trust networking, certificate management, or securing internal service communication.
+description: "Configure mutual TLS (mTLS) for zero-trust service-to-service communication. Use when implementing zero-trust networking, certificate management, or securing internal service communication."
+risk: unknown
+source: community
 ---
 
 # mTLS Configuration

package/merged-commands/multi-agent-brainstorming.md

@@ -1,11 +1,13 @@
 ---
 name: multi-agent-brainstorming
-description: >
+description: 
   Use this skill when a design or idea requires higher confidence,
   risk reduction, or formal review. This skill orchestrates a
   structured, sequential multi-agent design review where each agent
   has a strict, non-overlapping role. It prevents blind spots,
   false confidence, and premature convergence.
+risk: unknown
+source: community
 ---
 
 # Multi-Agent Brainstorming (Structured Design Review)
@@ -254,3 +256,6 @@ This skill exists to answer one question with confidence:
 
 If the answer is unclear, **do not exit this skill**.
 
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/multi-agent-patterns.md

@@ -239,7 +239,7 @@ This skill builds on context-fundamentals and context-degradation. It connects t
 ## References
 
 Internal reference:
-- [Frameworks Reference](./references/frameworks.md) - Detailed framework implementation patterns
+- Frameworks Reference - Detailed framework implementation patterns
 
 Related skills in this collection:
 - context-fundamentals - Context basics

package/merged-commands/multi-cloud-architecture.md

@@ -1,6 +1,8 @@
 ---
 name: multi-cloud-architecture
-description: Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, and GCP. Use when building multi-cloud systems, avoiding vendor lock-in, or leveraging best-of-breed services from multiple providers.
+description: "Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, and GCP. Use when building multi-cloud systems, avoiding vendor lock-in, or leveragin..."
+risk: unknown
+source: community
 ---
 
 # Multi-Cloud Architecture

package/merged-commands/multi-platform-apps-multi-platform.md

@@ -1,6 +1,8 @@
 ---
 name: multi-platform-apps-multi-platform
 description: "Build and deploy the same feature consistently across web, mobile, and desktop platforms using API-first architecture and parallel implementation strategies."
+risk: unknown
+source: community
 ---
 
 # Multi-Platform Feature Development Workflow

package/merged-commands/n8n-code-python.md

@@ -233,7 +233,7 @@ return [{
 }]
 ```
 
-**See**: [DATA_ACCESS.md](DATA_ACCESS.md) for comprehensive guide
+**See**: DATA_ACCESS.md for comprehensive guide
 
 ---
 
@@ -257,7 +257,7 @@ name = webhook_data.get("name")
 
 **Why**: Webhook node wraps all request data under `body` property. This includes POST data, query parameters, and JSON payloads.
 
-**See**: [DATA_ACCESS.md](DATA_ACCESS.md) for full webhook structure details
+**See**: DATA_ACCESS.md for full webhook structure details
 
 ---
 
@@ -320,7 +320,7 @@ return [{"data": value}]  # Should be {"json": value}
 
 **Why it matters**: Next nodes expect list format. Incorrect format causes workflow execution to fail.
 
-**See**: [ERROR_PATTERNS.md](ERROR_PATTERNS.md) #2 for detailed error solutions
+**See**: ERROR_PATTERNS.md #2 for detailed error solutions
 
 ---
 
@@ -370,7 +370,7 @@ import statistics  # ✅ Statistical functions
 - ✅ Use **HTTP Request node** + **HTML Extract node**
 - ✅ Or switch to **JavaScript** with regex/string methods
 
-**See**: [STANDARD_LIBRARY.md](STANDARD_LIBRARY.md) for complete reference
+**See**: STANDARD_LIBRARY.md for complete reference
 
 ---
 
@@ -490,7 +490,7 @@ else:
     return [{"json": {"error": "No values found"}}]
 ```
 
-**See**: [COMMON_PATTERNS.md](COMMON_PATTERNS.md) for 10 detailed Python patterns
+**See**: COMMON_PATTERNS.md for 10 detailed Python patterns
 
 ---
 
@@ -554,7 +554,7 @@ email = _json["body"]["email"]
 email = _json.get("body", {}).get("email", "no-email")
 ```
 
-**See**: [ERROR_PATTERNS.md](ERROR_PATTERNS.md) for comprehensive error guide
+**See**: ERROR_PATTERNS.md for comprehensive error guide
 
 ---
 
@@ -598,7 +598,7 @@ from statistics import mean, median, stdev
 average = mean([1, 2, 3, 4, 5])
 ```
 
-**See**: [STANDARD_LIBRARY.md](STANDARD_LIBRARY.md) for complete reference
+**See**: STANDARD_LIBRARY.md for complete reference
 
 ---
 
@@ -736,10 +736,10 @@ Before deploying Python Code nodes, verify:
 ## Additional Resources
 
 ### Related Files
-- [DATA_ACCESS.md](DATA_ACCESS.md) - Comprehensive Python data access patterns
-- [COMMON_PATTERNS.md](COMMON_PATTERNS.md) - 10 Python patterns for n8n
-- [ERROR_PATTERNS.md](ERROR_PATTERNS.md) - Top 5 errors and solutions
-- [STANDARD_LIBRARY.md](STANDARD_LIBRARY.md) - Complete standard library reference
+- DATA_ACCESS.md - Comprehensive Python data access patterns
+- COMMON_PATTERNS.md - 10 Python patterns for n8n
+- ERROR_PATTERNS.md - Top 5 errors and solutions
+- STANDARD_LIBRARY.md - Complete standard library reference
 
 ### n8n Documentation
 - Code Node Guide: https://docs.n8n.io/code/code-node/

package/merged-commands/n8n-mcp-tools-expert.md

@@ -1,6 +1,6 @@
 ---
 name: n8n-mcp-tools-expert
-description: "Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, or using any n8n-mcp tool. Provides tool selection guidance, parameter formats, and common patterns."
+description: "Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, or using any n8n-mcp tool. Provides tool sele..."
 source: "https://github.com/czlonkowski/n8n-skills/tree/main/skills/n8n-mcp-tools-expert"
 risk: safe
 ---
@@ -25,9 +25,9 @@ Use this skill when:
 
 n8n-mcp provides tools organized into categories:
 
-1. **Node Discovery** → [SEARCH_GUIDE.md](SEARCH_GUIDE.md)
-2. **Configuration Validation** → [VALIDATION_GUIDE.md](VALIDATION_GUIDE.md)
-3. **Workflow Management** → [WORKFLOW_GUIDE.md](WORKFLOW_GUIDE.md)
+1. **Node Discovery** → SEARCH_GUIDE.md
+2. **Configuration Validation** → VALIDATION_GUIDE.md
+3. **Workflow Management** → WORKFLOW_GUIDE.md
 4. **Template Library** - Search and deploy 2,700+ real workflows
 5. **Documentation & Guides** - Tool docs, AI agent guide, Code node guides
 
@@ -375,13 +375,13 @@ await n8n_update_partial_workflow({
 ## Detailed Guides
 
 ### Node Discovery Tools
-See [SEARCH_GUIDE.md](SEARCH_GUIDE.md) for:
+See SEARCH_GUIDE.md for:
 - search_nodes
 - get_node with detail levels (minimal, standard, full)
 - get_node modes (info, docs, search_properties, versions)
 
 ### Validation Tools
-See [VALIDATION_GUIDE.md](VALIDATION_GUIDE.md) for:
+See VALIDATION_GUIDE.md for:
 - Validation profiles explained
 - validate_node with modes (minimal, full)
 - validate_workflow complete structure
@@ -389,7 +389,7 @@ See [VALIDATION_GUIDE.md](VALIDATION_GUIDE.md) for:
 - Handling validation errors
 
 ### Workflow Management
-See [WORKFLOW_GUIDE.md](WORKFLOW_GUIDE.md) for:
+See WORKFLOW_GUIDE.md for:
 - n8n_create_workflow
 - n8n_update_partial_workflow (17 operation types!)
 - Smart parameters (branch, case)
@@ -639,9 +639,9 @@ validate_node({nodeType: "nodes-base.webhook", config: {}, mode: "minimal"})
 7. activateWorkflow → go live!
 
 For details, see:
-- [SEARCH_GUIDE.md](SEARCH_GUIDE.md) - Node discovery
-- [VALIDATION_GUIDE.md](VALIDATION_GUIDE.md) - Configuration validation
-- [WORKFLOW_GUIDE.md](WORKFLOW_GUIDE.md) - Workflow management
+- SEARCH_GUIDE.md - Node discovery
+- VALIDATION_GUIDE.md - Configuration validation
+- WORKFLOW_GUIDE.md - Workflow management
 
 ---
 

package/merged-commands/n8n-node-configuration.md

@@ -1,6 +1,6 @@
 ---
 name: n8n-node-configuration
-description: "Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning common configuration patterns by node type."
+description: "Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning commo..."
 source: "https://github.com/czlonkowski/n8n-skills/tree/main/skills/n8n-node-configuration"
 risk: safe
 ---
@@ -768,8 +768,8 @@ get_node({
 
 For comprehensive guides on specific topics:
 
-- **[DEPENDENCIES.md](DEPENDENCIES.md)** - Deep dive into property dependencies and displayOptions
-- **[OPERATION_PATTERNS.md](OPERATION_PATTERNS.md)** - Common configuration patterns by node type
+- **DEPENDENCIES.md** - Deep dive into property dependencies and displayOptions
+- **OPERATION_PATTERNS.md** - Common configuration patterns by node type
 
 ---
 

package/merged-commands/neon-postgres.md

@@ -1,7 +1,8 @@
 ---
 name: neon-postgres
-description: "Expert patterns for Neon serverless Postgres, branching, connection pooling, and Prisma/Drizzle integration Use when: neon database, serverless postgres, database branching, neon postgres, postgres serverless."
+description: "Expert patterns for Neon serverless Postgres, branching, connection pooling, and Prisma/Drizzle integration Use when: neon database, serverless postgres, database branching, neon postgres, postgres..."
 source: vibeship-spawner-skills (Apache 2.0)
+risk: unknown
 ---
 
 # Neon Postgres
@@ -54,3 +55,6 @@ Use pooled endpoint for application, direct for migrations.
 | Issue | low | See docs |
 | Issue | medium | See docs |
 | Issue | high | See docs |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/nerdzao-elite-gemini-high.md

@@ -0,0 +1,50 @@
+---
+name: nerdzao-elite-gemini-high
+description: "Modo Elite Coder + UX Pixel-Perfect otimizado especificamente para Gemini 3.1 Pro High. Workflow completo com foco em qualidade máxima e eficiência de tokens."
+risk: "safe"
+source: "community"
+---
+
+# @nerdzao-elite-gemini-high
+
+Você é um Engenheiro de Software Sênior Elite (15+ anos) + Designer de Produto Senior, operando no modo Gemini 3.1 Pro (High).
+
+Ative automaticamente este workflow completo em TODA tarefa:
+
+1. **Planejamento ultra-rápido**  
+   @concise-planning + @brainstorming
+
+2. **Arquitetura sólida**  
+   @senior-architect + @architecture
+
+3. **Implementação TDD**  
+   @test-driven-development + @testing-patterns
+
+4. **Código produção-grade**  
+   @refactor-clean-code + @clean-code
+
+5. **Validação técnica**  
+   @lint-and-validate + @production-code-audit + @code-reviewer
+
+6. **Validação Visual & UX OBRIGATÓRIA (High priority)**  
+   @ui-visual-validator + @ui-ux-pro-max + @frontend-design  
+
+   Analise e corrija IMEDIATAMENTE: duplicação de elementos, inconsistência de cores/labels, formatação de moeda (R$ XX,XX com vírgula), alinhamento, spacing, hierarquia visual e responsividade.  
+   Se qualquer coisa estiver quebrada, conserte antes de mostrar o código final.
+
+7. **Verificação final**  
+   @verification-before-completion + @kaizen
+
+**Regras específicas para Gemini 3.1 Pro High:**
+
+- Sempre pense passo a passo de forma clara e numerada (chain-of-thought).
+- Seja extremamente preciso com UI/UX — nunca entregue interface com qualquer quebra visual.
+- Responda de forma concisa: mostre apenas o código final + explicação breve de mudanças visuais corrigidas.
+- Nunca adicione comentários ou texto longo desnecessário.
+- Priorize: pixel-perfect + código limpo + performance + segurança.
+
+Você está no modo High: máximo de qualidade com mínimo de tokens desperdiçados.
+
+## When to Use
+
+Use when you need maximum quality output with Gemini 3.1 Pro High, pixel-perfect UI, and token-efficient workflow.

package/merged-commands/nerdzao-elite.md

@@ -0,0 +1,31 @@
+---
+name: nerdzao-elite
+description: "Senior Elite Software Engineer (15+) and Senior Product Designer. Full workflow with planning, architecture, TDD, clean code, and pixel-perfect UX validation."
+risk: safe
+source: community
+---
+
+# @nerdzao-elite
+
+Você é um Engenheiro de Software Sênior Elite (15+ anos) + Designer de Produto Senior.
+
+Ative automaticamente TODAS as skills abaixo em toda tarefa:
+
+@concise-planning @brainstorming @senior-architect @architecture @test-driven-development @testing-patterns @refactor-clean-code @clean-code @lint-and-validate @ui-visual-validator @ui-ux-pro-max @frontend-design @web-design-guidelines @production-code-audit @code-reviewer @systematic-debugging @error-handling-patterns @kaizen @verification-before-completion
+
+Workflow obrigatório (sempre na ordem):
+
+1. Planejamento (@concise-planning + @brainstorming)
+2. Arquitetura sólida
+3. Implementação com TDD completo
+4. Código limpo
+5. Validação técnica
+6. Validação visual UX OBRIGATÓRIA (@ui-visual-validator + @ui-ux-pro-max) → corrija imediatamente qualquer duplicação, inconsistência de cor/label, formatação de moeda, alinhamento etc.
+7. Revisão de produção
+8. Verificação final
+
+Nunca entregue UI quebrada. Priorize sempre pixel-perfect + produção-grade.
+
+## When to Use
+
+Use when you need a full senior engineering workflow with planning, architecture, TDD, clean code, and pixel-perfect UX validation in Portuguese (Brazil).

package/merged-commands/nestjs-expert.md

@@ -1,9 +1,11 @@
 ---
 name: nestjs-expert
-description: Nest.js framework expert specializing in module architecture, dependency injection, middleware, guards, interceptors, testing with Jest/Supertest, TypeORM/Mongoose integration, and Passport.js authentication. Use PROACTIVELY for any Nest.js application issues including architecture decisions, testing strategies, performance optimization, or debugging complex dependency injection problems. If a specialized expert is a better fit, I will recommend switching and stop.
+description: "Nest.js framework expert specializing in module architecture, dependency injection, middleware, guards, interceptors, testing with Jest/Supertest, TypeORM/Mongoose integration, and Passport.js auth..."
 category: framework
 displayName: Nest.js Framework Expert
 color: red
+risk: unknown
+source: community
 ---
 
 # Nest.js Expert
@@ -549,4 +551,7 @@ export class ConfigModule {
 - ✅ Code follows established project conventions
 - ✅ Proper error handling implemented
 - ✅ Security best practices applied
-- ✅ Documentation updated for API changes
+- ✅ Documentation updated for API changes
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/network-101.md

@@ -1,9 +1,11 @@
 ---
-name: Network 101
-description: This skill should be used when the user asks to "set up a web server", "configure HTTP or HTTPS", "perform SNMP enumeration", "configure SMB shares", "test network services", or needs guidance on configuring and testing network services for penetration testing labs.
+name: network-101
+description: "This skill should be used when the user asks to \"set up a web server\", \"configure HTTP or HTTPS\", \"perform SNMP enumeration\", \"configure SMB shares\", \"test network services\", or ne..."
 metadata:
   author: zebbern
   version: "1.1"
+risk: unknown
+source: community
 ---
 
 # Network 101
@@ -340,3 +342,6 @@ smbclient //localhost/anonymous -N
 | SMB access denied | Verify share permissions and user credentials |
 | HTTPS certificate error | Accept self-signed cert or add to trusted store |
 | Cannot connect remotely | Bind service to 0.0.0.0 instead of localhost |
+
+## When to Use
+This skill is applicable to execute the workflow or actions described in the overview.

package/merged-commands/network-engineer.md

@@ -1,6 +1,6 @@
 ---
 name: network-engineer
-description: Expert network engineer specializing in modern cloud networking,
+description: "Expert network engineer specializing in modern cloud networking,"
   security architectures, and performance optimization. Masters multi-cloud
   connectivity, service mesh, zero-trust networking, SSL/TLS, global load
   balancing, and advanced troubleshooting. Handles CDN optimization, network
@@ -8,6 +8,8 @@ description: Expert network engineer specializing in modern cloud networking,
   issues, or performance optimization.
 metadata:
   model: sonnet
+risk: unknown
+source: community
 ---
 
 ## Use this skill when