[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F3MFSRCE65MSG0YZ1QP92J":3,"skill-same:01M7F3MFSRCE65MSG0YZ1QP92J":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7F3MFSRCE65MSG0YZ1QP92J","n8n-node-configuration",null,"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. Always use this skill when setting up node parameters — it explains which fields are required for each operation, how displayOptions control field visibility, and when to use patchNodeField for surgical edits vs full node updates.","26BB\u002Fagent-fleet-os","26BB","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113676969?v=4","01M7F3AVX9MTTAHCYTANRGEE52","Bhushan Vijay Bhosale","01M7F3AVY15DJBX1CE4H25P52T",0,"MIT","https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002FN8N agent\u002Fplaybooks\u002Fn8n-node-configuration\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: n8n-node-configuration\ndescription: 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. Always use this skill when setting up node parameters — it explains which fields are required for each operation, how displayOptions control field visibility, and when to use patchNodeField for surgical edits vs full node updates.\n---\n\n# n8n Node Configuration\n\nExpert guidance for operation-aware node configuration with property dependencies.\n\n---\n\n## Configuration Philosophy\n\n**Progressive disclosure**: Start minimal, add complexity as needed\n\nConfiguration best practices:\n- `get_node` with `detail: \"standard\"` is the most used discovery pattern\n- 56 seconds average between configuration edits\n- Covers 95% of use cases with 1-2K tokens response\n\n**Key insight**: Most configurations need only standard detail, not full schema!\n\n---\n\n## Core Concepts\n\n### 1. Operation-Aware Configuration\n\n**Not all fields are always required** - it depends on operation!\n\n**Example**: Slack node\n```javascript\n\u002F\u002F For operation='post'\n{\n  \"resource\": \"message\",\n  \"operation\": \"post\",\n  \"channel\": \"#general\",  \u002F\u002F Required for post\n  \"text\": \"Hello!\"        \u002F\u002F Required for post\n}\n\n\u002F\u002F For operation='update'\n{\n  \"resource\": \"message\",\n  \"operation\": \"update\",\n  \"messageId\": \"123\",     \u002F\u002F Required for update (different!)\n  \"text\": \"Updated!\"      \u002F\u002F Required for update\n  \u002F\u002F channel NOT required for update\n}\n```\n\n**Key**: Resource + operation determine which fields are required!\n\n### 2. Property Dependencies\n\n**Fields appear\u002Fdisappear based on other field values**\n\n**Example**: HTTP Request node\n```javascript\n\u002F\u002F When method='GET'\n{\n  \"method\": \"GET\",\n  \"url\": \"https:\u002F\u002Fapi.example.com\"\n  \u002F\u002F sendBody not shown (GET doesn't have body)\n}\n\n\u002F\u002F When method='POST'\n{\n  \"method\": \"POST\",\n  \"url\": \"https:\u002F\u002Fapi.example.com\",\n  \"sendBody\": true,       \u002F\u002F Now visible!\n  \"body\": {               \u002F\u002F Required when sendBody=true\n    \"contentType\": \"json\",\n    \"content\": {...}\n  }\n}\n```\n\n**Mechanism**: displayOptions control field visibility\n\n### 3. Progressive Discovery\n\n**Use the right detail level**:\n\n1. **get_node({detail: \"standard\"})** - DEFAULT\n   - Quick overview (~1-2K tokens)\n   - Required fields + common options\n   - **Use first** - covers 95% of needs\n\n2. **get_node({mode: \"search_properties\", propertyQuery: \"...\"})** (for finding specific fields)\n   - Find properties by name\n   - Use when looking for auth, body, headers, etc.\n\n3. **get_node({detail: \"full\"})** (complete schema)\n   - All properties (~3-8K tokens)\n   - Use only when standard detail is insufficient\n\n---\n\n## Configuration Workflow\n\n### Standard Process\n\n1. Identify node type and operation.\n2. Use `get_node` (standard detail is default).\n3. Configure required fields.\n4. Validate configuration.\n5. If a field is unclear → `get_node({mode: \"search_properties\"})`.\n6. Add optional fields as needed.\n7. Validate again.\n8. Deploy.\n\n### Example: Configuring HTTP Request\n\nThe validate-driven loop in practice: start minimal (`method`, `url`, `authentication`), then let each `validate_node` error surface the next required field (`sendBody` for POST → `body` when `sendBody=true`) until valid. Full step-by-step walkthrough in **[OPERATION_PATTERNS.md](OPERATION_PATTERNS.md#worked-example-configuring-http-request-step-by-step)**.\n\n---\n\n## get_node Detail Levels\n\n### Standard Detail (DEFAULT - Use This!)\n\n**✅ Starting configuration**\n```javascript\nget_node({\n  nodeType: \"nodes-base.slack\"\n});\n\u002F\u002F detail=\"standard\" is the default\n```\n\n**Returns** (~1-2K tokens):\n- Required fields\n- Common options\n- Operation list\n- Metadata\n\n**Use**: 95% of configuration needs\n\n### Full Detail (Use Sparingly)\n\n**✅ When standard isn't enough**\n```javascript\nget_node({\n  nodeType: \"nodes-base.slack\",\n  detail: \"full\"\n});\n```\n\n**Returns** (~3-8K tokens):\n- Complete schema\n- All properties\n- All nested options\n\n**Warning**: Large response, use only when standard insufficient\n\n### Search Properties Mode\n\n**✅ Looking for specific field**\n```javascript\nget_node({\n  nodeType: \"nodes-base.httpRequest\",\n  mode: \"search_properties\",\n  propertyQuery: \"auth\"\n});\n```\n\n**Use**: Find authentication, headers, body fields, etc.\n\n### Decision Tree\n\n1. Starting a new node config → `get_node` (standard).\n2. Standard has what you need → configure with it. Otherwise continue.\n3. Looking for a specific field → `search_properties` mode. Otherwise continue.\n4. Still need more → `get_node({detail: \"full\"})`.\n\n**Dynamic properties**: when `standard` detail marks a property with `dynamicOptions: {methodName, methodType, dependsOn}`, its real values come from a live `loadOptions`\u002F`listSearch` method, not from bundled docs — don't guess an ID for it. Resolve it with `n8n_explore_node_resources` (needs `N8N_MCP_ACCESS_TOKEN`, n8n 2.34+) and put the returned `value` in the config; `name` is display text only.\n\nAll six parameters are required and none are inferred from each other:\n\n```javascript\nn8n_explore_node_resources({\n  nodeType: \"n8n-nodes-base.googleSheets\",  \u002F\u002F LONG form\n  version: 4.5,                              \u002F\u002F the node typeVersion the method belongs to\n  methodName: \"getSheets\",                   \u002F\u002F copied verbatim from dynamicOptions\n  methodType: \"listSearch\",                  \u002F\u002F \"listSearch\" for resource locators, \"loadOptions\" for plain dropdowns\n  credentialType: \"googleSheetsOAuth2Api\",\n  credentialId: \"c2\",                        \u002F\u002F from n8n_manage_credentials({action: \"list\"})\n  currentNodeParameters: {                   \u002F\u002F whatever dependsOn names, in its real shape\n    documentId: {__rl: true, mode: \"id\", value: \"1AbC…\"}\n  }\n})\n```\n\n`dependsOn` names the parameters the method needs already chosen — pass them in `currentNodeParameters`, keeping resource-locator values in their `{__rl: true, mode, value}` shape, or the method returns nothing useful. `methodName` is case-sensitive and specific to the `nodeType` + `version` pair; a mismatch returns `OFFICIAL_MCP_ERROR` rather than an empty list.\n\n---\n\n## Property Dependencies Deep Dive\n\nFields have `displayOptions` visibility rules: `show`\u002F`hide` blocks where multiple conditions are AND'd and multiple values are OR'd (e.g. `body` shows when `sendBody=true` AND `method IN (POST, PUT, PATCH)`). The three recurring patterns are the boolean toggle (sendBody → body), the operation switch (post vs update show different fields), and type selection (string vs boolean conditions). To find what controls a field, use `get_node({mode: \"search_properties\", propertyQuery: \"...\"})` or `get_node({detail: \"full\"})` — especially when validation flags a field you don't see.\n\nMechanism details, all four dependency patterns, complex flows, nested dependencies, and troubleshooting are in **[DEPENDENCIES.md](DEPENDENCIES.md)** (quick-reference recap under [Quick Reference: displayOptions and Common Dependency Patterns](DEPENDENCIES.md#quick-reference-displayoptions-and-common-dependency-patterns)).\n\n---\n\n## Common Node Patterns\n\n### Pattern 1: Resource\u002FOperation Nodes\n\n**Examples**: Slack, Google Sheets, Airtable\n\n**Structure**:\n```javascript\n{\n  \"resource\": \"\u003Centity>\",      \u002F\u002F What type of thing\n  \"operation\": \"\u003Caction>\",     \u002F\u002F What to do with it\n  \u002F\u002F ... operation-specific fields\n}\n```\n\n**How to configure**:\n1. Choose resource\n2. Choose operation\n3. Use get_node to see operation-specific requirements\n4. Configure required fields\n\n### Pattern 2: HTTP-Based Nodes\n\n**Examples**: HTTP Request, Webhook\n\n**Structure**:\n```javascript\n{\n  \"method\": \"\u003CHTTP_METHOD>\",\n  \"url\": \"\u003Cendpoint>\",\n  \"authentication\": \"\u003Ctype>\",\n  \u002F\u002F ... method-specific fields\n}\n```\n\n**Dependencies**:\n- POST\u002FPUT\u002FPATCH → sendBody available\n- sendBody=true → body required\n- authentication != \"none\" → credentials required\n\n**Critical: credentials block, node id, typeVersion**\n- **Never set a placeholder credential ID** (e.g. `\"id\": \"REPLACE_ME\"`) — n8n's UI renders a permanently disabled credential selector for unknown IDs. Omit the `credentials` block when the real ID is unknown; the user then gets a normal clickable dropdown.\n- **Node `id` must be a UUID v4**, not a readable slug — the frontend binds forms and the credential component to it.\n- **Don't hardcode old `typeVersion` values** — verify the current version with `get_node` (httpRequest is 4.4+).\n\n### Pattern 3: Database Nodes\n\n**Examples**: Postgres, MySQL, MongoDB\n\n**Structure**:\n```javascript\n{\n  \"operation\": \"\u003Cquery|insert|update|delete>\",\n  \u002F\u002F ... operation-specific fields\n}\n```\n\n**Dependencies**:\n- operation=\"executeQuery\" → query required\n- operation=\"insert\" → table + values required\n- operation=\"update\" → table + values + where required\n\n**Critical: Write operations may return 0 items**\n- INSERT, UPDATE, DELETE can produce 0 n8n output items, depending on the node and operation (raw query execution reliably returns 0 result rows; some database nodes return the affected rows)\n- Set `alwaysOutputData: true` on write-operation nodes to keep downstream chains alive\n- Downstream nodes should use `$('UpstreamNode').all()` instead of `$input` if they need data\n\n### Pattern 4: Conditional Logic Nodes\n\n**Examples**: IF, Switch, Merge\n\n**Structure**:\n```javascript\n{\n  \"conditions\": {\n    \"\u003Ctype>\": [\n      {\n        \"operation\": \"\u003Coperator>\",\n        \"value1\": \"...\",\n        \"value2\": \"...\"  \u002F\u002F Only for binary operators\n      }\n    ]\n  }\n}\n```\n\n**Dependencies**:\n- Binary operators (equals, contains, etc.) → value1 + value2\n- Unary operators (isEmpty, isNotEmpty) → value1 only + singleValue: true\n\n---\n\n## Operation-Specific Configuration\n\nRequired fields shift with resource + operation: Slack `post` needs `channel`+`text`, but `update` needs `messageId`+`text` (channel optional) and `channel\u002Fcreate` needs `name`. HTTP `GET` uses `sendQuery`+`queryParameters`; `POST` needs `sendBody`+`body`. IF binary operators (`equals`) need `value1`+`value2`; unary (`isEmpty`) need only `value1` plus auto-added `singleValue: true`. Concrete minimal configs for each in **[OPERATION_PATTERNS.md](OPERATION_PATTERNS.md#operation-specific-configuration-examples)**.\n\n---\n\n## Handling Conditional Requirements\n\nSome fields are required only under certain conditions: HTTP `body` is required when `sendBody=true` AND `method IN (POST, PUT, PATCH, DELETE)`; IF `singleValue` should be `true` when the operator is unary (`isEmpty`, `isNotEmpty`, `true`, `false`) — and auto-sanitization sets it for you. Discover conditional requirements by reading the validation error, searching the property (`get_node({mode: \"search_properties\"})`), or iterating from a minimal config. Worked discovery examples in **[DEPENDENCIES.md](DEPENDENCIES.md#handling-conditional-requirements)**.\n\n---\n\n## Node-Specific Configuration Notes\n\n### SplitInBatches v3\n\n```javascript\n{\n  \"batchSize\": 100,  \u002F\u002F Number of items per batch\n  \"options\": {}\n}\n```\n\n**Output wiring**:\n- `main[0]` (done) → Connect to downstream processing (add Limit 1 first)\n- `main[1]` (each batch) → Connect to loop body, then loop back to SplitInBatches input\n\nSee the n8n Workflow Patterns skill for detailed loop and nested loop patterns.\n\n### Google Sheets Node\n\n**Per-item execution**: Each input item triggers a separate API call. If you have 100 items and use a Google Sheets \"Append Row\" node, it makes 100 API calls. To write in bulk, aggregate items in a Code node first, then use a single HTTP Request with the Sheets API.\n\n**Formula columns**: Never use `append` on sheets with formula columns — it overwrites formulas. Instead, use HTTP Request with Google Sheets API `values.update` (PUT) method and a `googleApi` credential.\n\n---\n\n## Configuration Anti-Patterns\n\n### ❌ Don't: Over-configure Upfront\n\n**Bad**:\n```javascript\n\u002F\u002F Adding every possible field\n{\n  \"method\": \"GET\",\n  \"url\": \"...\",\n  \"sendQuery\": false,\n  \"sendHeaders\": false,\n  \"sendBody\": false,\n  \"timeout\": 10000,\n  \"ignoreResponseCode\": false,\n  \u002F\u002F ... 20 more optional fields\n}\n```\n\n**Good**:\n```javascript\n\u002F\u002F Start minimal\n{\n  \"method\": \"GET\",\n  \"url\": \"...\",\n  \"authentication\": \"none\"\n}\n\u002F\u002F Add fields only when needed\n```\n\n### ❌ Don't: Skip Validation\n\n**Bad**:\n```javascript\n\u002F\u002F Configure and deploy without validating\nconst config = {...};\nn8n_update_partial_workflow({...});  \u002F\u002F YOLO\n```\n\n**Good**:\n```javascript\n\u002F\u002F Validate before deploying\nconst config = {...};\nconst result = validate_node({...});\nif (result.valid) {\n  n8n_update_partial_workflow({...});\n}\n```\n\n### ❌ Don't: Ignore Operation Context\n\n**Bad**:\n```javascript\n\u002F\u002F Same config for all Slack operations\n{\n  \"resource\": \"message\",\n  \"operation\": \"post\",\n  \"channel\": \"#general\",\n  \"text\": \"...\"\n}\n\n\u002F\u002F Then switching operation without updating config\n{\n  \"resource\": \"message\",\n  \"operation\": \"update\",  \u002F\u002F Changed\n  \"channel\": \"#general\",  \u002F\u002F Wrong field for update!\n  \"text\": \"...\"\n}\n```\n\n**Good**:\n```javascript\n\u002F\u002F Check requirements when changing operation\nget_node({\n  nodeType: \"nodes-base.slack\"\n});\n\u002F\u002F See what update operation needs (messageId, not channel)\n```\n\n---\n\n## Surgical Field Edits with patchNodeField\n\nWhen you need to edit a specific string inside a node field — rather than replacing the whole field — use `patchNodeField` in `n8n_update_partial_workflow`. This is especially useful for:\n\n- Editing code inside Code nodes without re-transmitting the full code block\n- Updating URLs or text in large HTML email templates\n- Fixing typos in JSON bodies or long text fields\n\n```javascript\n\u002F\u002F Instead of replacing the entire jsCode field:\nn8n_update_partial_workflow({\n  id: \"wf-123\",\n  operations: [{\n    type: \"patchNodeField\",\n    nodeName: \"Code\",\n    fieldPath: \"parameters.jsCode\",\n    patches: [{find: \"const limit = 10;\", replace: \"const limit = 50;\"}]\n  }]\n})\n```\n\n`patchNodeField` is strict — it errors if the find string isn't found or matches multiple times (unless `replaceAll: true`). This prevents accidental silent failures during configuration updates. See the n8n MCP Tools Expert skill for full syntax and examples.\n\n---\n\n## Best Practices\n\n### Do\n\n1. **Start with get_node (standard detail)**\n   - ~1-2K tokens response\n   - Covers 95% of configuration needs\n   - Default detail level\n\n2. **Validate iteratively**\n   - Configure → Validate → Fix → Repeat\n   - Average 2-3 iterations is normal\n   - Read validation errors carefully\n\n3. **Use search_properties mode when stuck**\n   - If field seems missing, search for it\n   - Understand what controls field visibility\n   - `get_node({mode: \"search_properties\", propertyQuery: \"...\"})`\n\n4. **Respect operation context**\n   - Different operations = different requirements\n   - Always check get_node when changing operation\n   - Don't assume configs are transferable\n\n5. **Trust auto-sanitization**\n   - Operator structure fixed automatically\n   - Don't manually add\u002Fremove singleValue\n   - IF\u002FSwitch metadata added on save\n\n### ❌ Don't\n\n1. **Jump to detail=\"full\" immediately**\n   - Try standard detail first\n   - Only escalate if needed\n   - Full schema is 3-8K tokens\n\n2. **Configure blindly**\n   - Always validate before deploying\n   - Understand why fields are required\n   - Use search_properties for conditional fields\n\n3. **Copy configs without understanding**\n   - Different operations need different fields\n   - Validate after copying\n   - Adjust for new context\n\n4. **Manually fix auto-sanitization issues**\n   - Let auto-sanitization handle operator structure\n   - Focus on business logic\n   - Save and let system fix structure\n\n---\n\n## Silent-Failure Gotchas by Node Family\n\nSome misconfigurations pass `validate_node` and `validate_workflow` clean, run without error, and quietly do the wrong thing — `get_node` shows the fields exist but not what happens when you omit them. The high-frequency ones:\n\n- **Switch** — no `options.fallbackOutput` ⇒ unmatched items silently dropped.\n- **Merge** — `numberOfInputs` defaults to 2 (extra sources drop); `useDataOfInput` is 1-indexed vs the 0-indexed `connections.\u003Csrc>.main[idx]` slot (`useDataOfInput: \"N\"` → `main[N-1]`).\n- **Database** — `{{ }}` interpolation into `parameters.query` is SQL injection; use `$1\u002F$2` placeholders + `options.queryReplacement`.\n- **Slack** — Block Kit must be wrapped `={{ { \"blocks\": ... } }}` or it posts as plain text.\n- **Webhook \u002F Respond** — `responseCode` defaults to 200 even on error branches.\n- **Schedule Trigger** — timezone is workflow-level (Workflow Settings), not per-rule.\n\nFull symptom\u002Fcause\u002Ffix detail (in JSON + `n8n_update_partial_workflow` terms) in **[NODE_FAMILY_GOTCHAS.md](NODE_FAMILY_GOTCHAS.md)**.\n\n---\n\n## Detailed References\n\nFor comprehensive guides on specific topics:\n\n- **[DEPENDENCIES.md](DEPENDENCIES.md)** - Deep dive into property dependencies and displayOptions\n- **[OPERATION_PATTERNS.md](OPERATION_PATTERNS.md)** - Common configuration patterns by node type\n- **[NODE_FAMILY_GOTCHAS.md](NODE_FAMILY_GOTCHAS.md)** - Silent runtime traps by family (Switch, Merge, Database, Slack, Webhook, Schedule)\n\n---\n\n## Summary\n\n**Configuration Strategy**:\n1. Start with `get_node` (standard detail is default)\n2. Configure required fields for operation\n3. Validate configuration\n4. Search properties if stuck\n5. Iterate until valid (avg 2-3 cycles)\n6. Deploy with confidence\n\n**Key Principles**:\n- **Operation-aware**: Different operations = different requirements\n- **Progressive disclosure**: Start minimal, add as needed\n- **Dependency-aware**: Understand field visibility rules\n- **Validation-driven**: Let validation guide configuration\n\n**Related Skills**:\n- **n8n MCP Tools Expert** - How to use discovery tools correctly\n- **n8n Validation Expert** - Interpret validation errors\n- **n8n Expression Syntax** - Configure expression fields\n- **n8n Workflow Patterns** - Apply patterns with proper configuration\n","# n8n Node Configuration\n\nExpert guidance for operation-aware node configuration with property dependencies.\n\n---\n\n## Configuration Philosophy\n\n**Progressive disclosure**: Start minimal, add complexity as needed\n\nConfiguration best practices:\n- `get_node` with `detail: \"standard\"` is the most used discovery pattern\n- 56 seconds average between configuration edits\n- Covers 95% of use cases with 1-2K tokens response\n\n**Key insight**: Most configurations need only standard detail, not full schema!\n\n---\n\n## Core Concepts\n\n### 1. Operation-Aware Configuration\n\n**Not all fields are always required** - it depends on operation!\n\n**Example**: Slack node\n```javascript\n\u002F\u002F For operation='post'\n{\n  \"resource\": \"message\",\n  \"operation\": \"post\",\n  \"channel\": \"#general\",  \u002F\u002F Required for post\n  \"text\": \"Hello!\"        \u002F\u002F Required for post\n}\n\n\u002F\u002F For operation='update'\n{\n  \"resource\": \"message\",\n  \"operation\": \"update\",\n  \"messageId\": \"123\",     \u002F\u002F Required for update (different!)\n  \"text\": \"Updated!\"      \u002F\u002F Required for update\n  \u002F\u002F channel NOT required for update\n}\n```\n\n**Key**: Resource + operation determine which fields are required!\n\n### 2. Property Dependencies\n\n**Fields appear\u002Fdisappear based on other field values**\n\n**Example**: HTTP Request node\n```javascript\n\u002F\u002F When method='GET'\n{\n  \"method\": \"GET\",\n  \"url\": \"https:\u002F\u002Fapi.example.com\"\n  \u002F\u002F sendBody not shown (GET doesn't have body)\n}\n\n\u002F\u002F When method='POST'\n{\n  \"method\": \"POST\",\n  \"url\": \"https:\u002F\u002Fapi.example.com\",\n  \"sendBody\": true,       \u002F\u002F Now visible!\n  \"body\": {               \u002F\u002F Required when sendBody=true\n    \"contentType\": \"json\",\n    \"content\": {...}\n  }\n}\n```\n\n**Mechanism**: displayOptions control field visibility\n\n### 3. Progressive Discovery\n\n**Use the right detail level**:\n\n1. **get_node({detail: \"standard\"})** - DEFAULT\n   - Quick overview (~1-2K tokens)\n   - Required fields + common options\n   - **Use first** - covers 95% of needs\n\n2. **get_node({mode: \"search_properties\", propertyQuery: \"...\"})** (for finding specific fields)\n   - Find properties by name\n   - Use when looking for auth, body, headers, etc.\n\n3. **get_node({detail: \"full\"})** (complete schema)\n   - All properties (~3-8K tokens)\n   - Use only when standard detail is insufficient\n\n---\n\n## Configuration Workflow\n\n### Standard Process\n\n1. Identify node type and operation.\n2. Use `get_node` (standard detail is default).\n3. Configure required fields.\n4. Validate configuration.\n5. If a field is unclear → `get_node({mode: \"search_properties\"})`.\n6. Add optional fields as needed.\n7. Validate again.\n8. Deploy.\n\n### Example: Configuring HTTP Request\n\nThe validate-driven loop in practice: start minimal (`method`, `url`, `authentication`), then let each `validate_node` error surface the next required field (`sendBody` for POST → `body` when `sendBody=true`) until valid. Full step-by-step walkthrough in **[OPERATION_PATTERNS.md](OPERATION_PATTERNS.md#worked-example-configuring-http-request-step-by-step)**.\n\n---\n\n## get_node Detail Levels\n\n### Standard Detail (DEFAULT - Use This!)\n\n**✅ Starting configuration**\n```javascript\nget_node({\n  nodeType: \"nodes-base.slack\"\n});\n\u002F\u002F detail=\"standard\" is the default\n```\n\n**Returns** (~1-2K tokens):\n- Required fields\n- Common options\n- Operation list\n- Metadata\n\n**Use**: 95% of configuration needs\n\n### Full Detail (Use Sparingly)\n\n**✅ When standard isn't enough**\n```javascript\nget_node({\n  nodeType: \"nodes-base.slack\",\n  detail: \"full\"\n});\n```\n\n**Returns** (~3-8K tokens):\n- Complete schema\n- All properties\n- All nested options\n\n**Warning**: Large response, use only when standard insufficient\n\n### Search Properties Mode\n\n**✅ Looking for specific field**\n```javascript\nget_node({\n  nodeType: \"nodes-base.httpRequest\",\n  mode: \"search_properties\",\n  propertyQuery: \"auth\"\n});\n```\n\n**Use**: Find authentication, headers, body fields, etc.\n\n### Decision Tree\n\n1. Starting a new node config → `get_node` (standard).\n2. Standard has what you need → configure with it. Otherwise continue.\n3. Looking for a specific field → `search_properties` mode. Otherwise continue.\n4. Still need more → `get_node({detail: \"full\"})`.\n\n**Dynamic properties**: when `standard` detail marks a property with `dynamicOptions: {methodName, methodType, dependsOn}`, its real values come from a live `loadOptions`\u002F`listSearch` method, not from bundled docs — don't guess an ID for it. Resolve it with `n8n_explore_node_resources` (needs `N8N_MCP_ACCESS_TOKEN`, n8n 2.34+) and put the returned `value` in the config; `name` is display text only.\n\nAll six parameters are required and none are inferred from each other:\n\n```javascript\nn8n_explore_node_resources({\n  nodeType: \"n8n-nodes-base.googleSheets\",  \u002F\u002F LONG form\n  version: 4.5,                              \u002F\u002F the node typeVersion the method belongs to\n  methodName: \"getSheets\",                   \u002F\u002F copied verbatim from dynamicOptions\n  methodType: \"listSearch\",                  \u002F\u002F \"listSearch\" for resource locators, \"loadOptions\" for plain dropdowns\n  credentialType: \"googleSheetsOAuth2Api\",\n  credentialId: \"c2\",                        \u002F\u002F from n8n_manage_credentials({action: \"list\"})\n  currentNodeParameters: {                   \u002F\u002F whatever dependsOn names, in its real shape\n    documentId: {__rl: true, mode: \"id\", value: \"1AbC…\"}\n  }\n})\n```\n\n`dependsOn` names the parameters the method needs already chosen — pass them in `currentNodeParameters`, keeping resource-locator values in their `{__rl: true, mode, value}` shape, or the method returns nothing useful. `methodName` is case-sensitive and specific to the `nodeType` + `version` pair; a mismatch returns `OFFICIAL_MCP_ERROR` rather than an empty list.\n\n---\n\n## Property Dependencies Deep Dive\n\nFields have `displayOptions` visibility rules: `show`\u002F`hide` blocks where multiple conditions are AND'd and multiple values are OR'd (e.g. `body` shows when `sendBody=true` AND `method IN (POST, PUT, PATCH)`). The three recurring patterns are the boolean toggle (sendBody → body), the operation switch (post vs update show different fields), and type selection (string vs boolean conditions). To find what controls a field, use `get_node({mode: \"search_properties\", propertyQuery: \"...\"})` or `get_node({detail: \"full\"})` — especially when validation flags a field you don't see.\n\nMechanism details, all four dependency patterns, complex flows, nested dependencies, and troubleshooting are in **[DEPENDENCIES.md](DEPENDENCIES.md)** (quick-reference recap under [Quick Reference: displayOptions and Common Dependency Patterns](DEPENDENCIES.md#quick-reference-displayoptions-and-common-dependency-patterns)).\n\n---\n\n## Common Node Patterns\n\n### Pattern 1: Resource\u002FOperation Nodes\n\n**Examples**: Slack, Google Sheets, Airtable\n\n**Structure**:\n```javascript\n{\n  \"resource\": \"\u003Centity>\",      \u002F\u002F What type of thing\n  \"operation\": \"\u003Caction>\",     \u002F\u002F What to do with it\n  \u002F\u002F ... operation-specific fields\n}\n```\n\n**How to configure**:\n1. Choose resource\n2. Choose operation\n3. Use get_node to see operation-specific requirements\n4. Configure required fields\n\n### Pattern 2: HTTP-Based Nodes\n\n**Examples**: HTTP Request, Webhook\n\n**Structure**:\n```javascript\n{\n  \"method\": \"\u003CHTTP_METHOD>\",\n  \"url\": \"\u003Cendpoint>\",\n  \"authentication\": \"\u003Ctype>\",\n  \u002F\u002F ... method-specific fields\n}\n```\n\n**Dependencies**:\n- POST\u002FPUT\u002FPATCH → sendBody available\n- sendBody=true → body required\n- authentication != \"none\" → credentials required\n\n**Critical: credentials block, node id, typeVersion**\n- **Never set a placeholder credential ID** (e.g. `\"id\": \"REPLACE_ME\"`) — n8n's UI renders a permanently disabled credential selector for unknown IDs. Omit the `credentials` block when the real ID is unknown; the user then gets a normal clickable dropdown.\n- **Node `id` must be a UUID v4**, not a readable slug — the frontend binds forms and the credential component to it.\n- **Don't hardcode old `typeVersion` values** — verify the current version with `get_node` (httpRequest is 4.4+).\n\n### Pattern 3: Database Nodes\n\n**Examples**: Postgres, MySQL, MongoDB\n\n**Structure**:\n```javascript\n{\n  \"operation\": \"\u003Cquery|insert|update|delete>\",\n  \u002F\u002F ... operation-specific fields\n}\n```\n\n**Dependencies**:\n- operation=\"executeQuery\" → query required\n- operation=\"insert\" → table + values required\n- operation=\"update\" → table + values + where required\n\n**Critical: Write operations may return 0 items**\n- INSERT, UPDATE, DELETE can produce 0 n8n output items, depending on the node and operation (raw query execution reliably returns 0 result rows; some database nodes return the affected rows)\n- Set `alwaysOutputData: true` on write-operation nodes to keep downstream chains alive\n- Downstream nodes should use `$('UpstreamNode').all()` instead of `$input` if they need data\n\n### Pattern 4: Conditional Logic Nodes\n\n**Examples**: IF, Switch, Merge\n\n**Structure**:\n```javascript\n{\n  \"conditions\": {\n    \"\u003Ctype>\": [\n      {\n        \"operation\": \"\u003Coperator>\",\n        \"value1\": \"...\",\n        \"value2\": \"...\"  \u002F\u002F Only for binary operators\n      }\n    ]\n  }\n}\n```\n\n**Dependencies**:\n- Binary operators (equals, contains, etc.) → value1 + value2\n- Unary operators (isEmpty, isNotEmpty) → value1 only + singleValue: true\n\n---\n\n## Operation-Specific Configuration\n\nRequired fields shift with resource + operation: Slack `post` needs `channel`+`text`, but `update` needs `messageId`+`text` (channel optional) and `channel\u002Fcreate` needs `name`. HTTP `GET` uses `sendQuery`+`queryParameters`; `POST` needs `sendBody`+`body`. IF binary operators (`equals`) need `value1`+`value2`; unary (`isEmpty`) need only `value1` plus auto-added `singleValue: true`. Concrete minimal configs for each in **[OPERATION_PATTERNS.md](OPERATION_PATTERNS.md#operation-specific-configuration-examples)**.\n\n---\n\n## Handling Conditional Requirements\n\nSome fields are required only under certain conditions: HTTP `body` is required when `sendBody=true` AND `method IN (POST, PUT, PATCH, DELETE)`; IF `singleValue` should be `true` when the operator is unary (`isEmpty`, `isNotEmpty`, `true`, `false`) — and auto-sanitization sets it for you. Discover conditional requirements by reading the validation error, searching the property (`get_node({mode: \"search_properties\"})`), or iterating from a minimal config. Worked discovery examples in **[DEPENDENCIES.md](DEPENDENCIES.md#handling-conditional-requirements)**.\n\n---\n\n## Node-Specific Configuration Notes\n\n### SplitInBatches v3\n\n```javascript\n{\n  \"batchSize\": 100,  \u002F\u002F Number of items per batch\n  \"options\": {}\n}\n```\n\n**Output wiring**:\n- `main[0]` (done) → Connect to downstream processing (add Limit 1 first)\n- `main[1]` (each batch) → Connect to loop body, then loop back to SplitInBatches input\n\nSee the n8n Workflow Patterns skill for detailed loop and nested loop patterns.\n\n### Google Sheets Node\n\n**Per-item execution**: Each input item triggers a separate API call. If you have 100 items and use a Google Sheets \"Append Row\" node, it makes 100 API calls. To write in bulk, aggregate items in a Code node first, then use a single HTTP Request with the Sheets API.\n\n**Formula columns**: Never use `append` on sheets with formula columns — it overwrites formulas. Instead, use HTTP Request with Google Sheets API `values.update` (PUT) method and a `googleApi` credential.\n\n---\n\n## Configuration Anti-Patterns\n\n### ❌ Don't: Over-configure Upfront\n\n**Bad**:\n```javascript\n\u002F\u002F Adding every possible field\n{\n  \"method\": \"GET\",\n  \"url\": \"...\",\n  \"sendQuery\": false,\n  \"sendHeaders\": false,\n  \"sendBody\": false,\n  \"timeout\": 10000,\n  \"ignoreResponseCode\": false,\n  \u002F\u002F ... 20 more optional fields\n}\n```\n\n**Good**:\n```javascript\n\u002F\u002F Start minimal\n{\n  \"method\": \"GET\",\n  \"url\": \"...\",\n  \"authentication\": \"none\"\n}\n\u002F\u002F Add fields only when needed\n```\n\n### ❌ Don't: Skip Validation\n\n**Bad**:\n```javascript\n\u002F\u002F Configure and deploy without validating\nconst config = {...};\nn8n_update_partial_workflow({...});  \u002F\u002F YOLO\n```\n\n**Good**:\n```javascript\n\u002F\u002F Validate before deploying\nconst config = {...};\nconst result = validate_node({...});\nif (result.valid) {\n  n8n_update_partial_workflow({...});\n}\n```\n\n### ❌ Don't: Ignore Operation Context\n\n**Bad**:\n```javascript\n\u002F\u002F Same config for all Slack operations\n{\n  \"resource\": \"message\",\n  \"operation\": \"post\",\n  \"channel\": \"#general\",\n  \"text\": \"...\"\n}\n\n\u002F\u002F Then switching operation without updating config\n{\n  \"resource\": \"message\",\n  \"operation\": \"update\",  \u002F\u002F Changed\n  \"channel\": \"#general\",  \u002F\u002F Wrong field for update!\n  \"text\": \"...\"\n}\n```\n\n**Good**:\n```javascript\n\u002F\u002F Check requirements when changing operation\nget_node({\n  nodeType: \"nodes-base.slack\"\n});\n\u002F\u002F See what update operation needs (messageId, not channel)\n```\n\n---\n\n## Surgical Field Edits with patchNodeField\n\nWhen you need to edit a specific string inside a node field — rather than replacing the whole field — use `patchNodeField` in `n8n_update_partial_workflow`. This is especially useful for:\n\n- Editing code inside Code nodes without re-transmitting the full code block\n- Updating URLs or text in large HTML email templates\n- Fixing typos in JSON bodies or long text fields\n\n```javascript\n\u002F\u002F Instead of replacing the entire jsCode field:\nn8n_update_partial_workflow({\n  id: \"wf-123\",\n  operations: [{\n    type: \"patchNodeField\",\n    nodeName: \"Code\",\n    fieldPath: \"parameters.jsCode\",\n    patches: [{find: \"const limit = 10;\", replace: \"const limit = 50;\"}]\n  }]\n})\n```\n\n`patchNodeField` is strict — it errors if the find string isn't found or matches multiple times (unless `replaceAll: true`). This prevents accidental silent failures during configuration updates. See the n8n MCP Tools Expert skill for full syntax and examples.\n\n---\n\n## Best Practices\n\n### Do\n\n1. **Start with get_node (standard detail)**\n   - ~1-2K tokens response\n   - Covers 95% of configuration needs\n   - Default detail level\n\n2. **Validate iteratively**\n   - Configure → Validate → Fix → Repeat\n   - Average 2-3 iterations is normal\n   - Read validation errors carefully\n\n3. **Use search_properties mode when stuck**\n   - If field seems missing, search for it\n   - Understand what controls field visibility\n   - `get_node({mode: \"search_properties\", propertyQuery: \"...\"})`\n\n4. **Respect operation context**\n   - Different operations = different requirements\n   - Always check get_node when changing operation\n   - Don't assume configs are transferable\n\n5. **Trust auto-sanitization**\n   - Operator structure fixed automatically\n   - Don't manually add\u002Fremove singleValue\n   - IF\u002FSwitch metadata added on save\n\n### ❌ Don't\n\n1. **Jump to detail=\"full\" immediately**\n   - Try standard detail first\n   - Only escalate if needed\n   - Full schema is 3-8K tokens\n\n2. **Configure blindly**\n   - Always validate before deploying\n   - Understand why fields are required\n   - Use search_properties for conditional fields\n\n3. **Copy configs without understanding**\n   - Different operations need different fields\n   - Validate after copying\n   - Adjust for new context\n\n4. **Manually fix auto-sanitization issues**\n   - Let auto-sanitization handle operator structure\n   - Focus on business logic\n   - Save and let system fix structure\n\n---\n\n## Silent-Failure Gotchas by Node Family\n\nSome misconfigurations pass `validate_node` and `validate_workflow` clean, run without error, and quietly do the wrong thing — `get_node` shows the fields exist but not what happens when you omit them. The high-frequency ones:\n\n- **Switch** — no `options.fallbackOutput` ⇒ unmatched items silently dropped.\n- **Merge** — `numberOfInputs` defaults to 2 (extra sources drop); `useDataOfInput` is 1-indexed vs the 0-indexed `connections.\u003Csrc>.main[idx]` slot (`useDataOfInput: \"N\"` → `main[N-1]`).\n- **Database** — `{{ }}` interpolation into `parameters.query` is SQL injection; use `$1\u002F$2` placeholders + `options.queryReplacement`.\n- **Slack** — Block Kit must be wrapped `={{ { \"blocks\": ... } }}` or it posts as plain text.\n- **Webhook \u002F Respond** — `responseCode` defaults to 200 even on error branches.\n- **Schedule Trigger** — timezone is workflow-level (Workflow Settings), not per-rule.\n\nFull symptom\u002Fcause\u002Ffix detail (in JSON + `n8n_update_partial_workflow` terms) in **[NODE_FAMILY_GOTCHAS.md](NODE_FAMILY_GOTCHAS.md)**.\n\n---\n\n## Detailed References\n\nFor comprehensive guides on specific topics:\n\n- **[DEPENDENCIES.md](DEPENDENCIES.md)** - Deep dive into property dependencies and displayOptions\n- **[OPERATION_PATTERNS.md](OPERATION_PATTERNS.md)** - Common configuration patterns by node type\n- **[NODE_FAMILY_GOTCHAS.md](NODE_FAMILY_GOTCHAS.md)** - Silent runtime traps by family (Switch, Merge, Database, Slack, Webhook, Schedule)\n\n---\n\n## Summary\n\n**Configuration Strategy**:\n1. Start with `get_node` (standard detail is default)\n2. Configure required fields for operation\n3. Validate configuration\n4. Search properties if stuck\n5. Iterate until valid (avg 2-3 cycles)\n6. Deploy with confidence\n\n**Key Principles**:\n- **Operation-aware**: Different operations = different requirements\n- **Progressive disclosure**: Start minimal, add as needed\n- **Dependency-aware**: Understand field visibility rules\n- **Validation-driven**: Let validation guide configuration\n\n**Related Skills**:\n- **n8n MCP Tools Expert** - How to use discovery tools correctly\n- **n8n Validation Expert** - Interpret validation errors\n- **n8n Expression Syntax** - Configure expression fields\n- **n8n Workflow Patterns** - Apply patterns with proper configuration\n",{"name":5,"description":7},"main","98985c16dc8df1bbd7dcd1bc698cd997a093e751","N8N agent\u002Fplaybooks\u002Fn8n-node-configuration","https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os","https:\u002F\u002Fgithub.com\u002F26BB","🚀 Aspiring Product Manager | CS @ GS Moze\r\n\r\n🛠️ Building 0→1 products across SaaS & clean-tech\r\n\r\n📊 Turning user feedback & data into shipped features","2026-11-05 13:34:38",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add 26BB\u002Fagent-fleet-os --skill n8n-node-configuration",{"tool":37,"command":38},"bunx","bunx skills add 26BB\u002Fagent-fleet-os --skill n8n-node-configuration",{"tool":40,"command":41},"pnpm","pnpm dlx skills add 26BB\u002Fagent-fleet-os --skill n8n-node-configuration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002FN8N agent\u002Fplaybooks\u002Fn8n-node-configuration\u002FSKILL.md",true,[45,51,55,59],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"DEPENDENCIES.md","REFERENCE","参考文档",17634,"https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002FN8N agent\u002Fplaybooks\u002Fn8n-node-configuration\u002FDEPENDENCIES.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"NODE_FAMILY_GOTCHAS.md",13454,"https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002FN8N agent\u002Fplaybooks\u002Fn8n-node-configuration\u002FNODE_FAMILY_GOTCHAS.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"OPERATION_PATTERNS.md",26943,"https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002FN8N agent\u002Fplaybooks\u002Fn8n-node-configuration\u002FOPERATION_PATTERNS.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"README.md",9798,"https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002FN8N agent\u002Fplaybooks\u002Fn8n-node-configuration\u002FREADME.md",[64,71,78,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7F51NQSCRM2PWFMATCV9MEG","taste-design","Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.","https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-utilities\u002Fplaybooks\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7F51JGTS9VJ3S9T6VMQWZ08","stitch-loop","Teaches agents to iteratively build websites using Stitch with an autonomous baton-passing loop pattern","https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-utilities\u002Fplaybooks\u002Fstitch-loop\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7F51EZR2XYDWMA3XKWH1HX2","site-md","Analyze a project description or site requirements and synthesize a project constitution into SITE.md for the Stitch Build Loop","https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-utilities\u002Fplaybooks\u002Fsite-md\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7F51BNCMP0GQ7SGP39SZYDP","enhance-prompt","Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI\u002FUX keywords, injects design system context, and structures output for better generation results.","https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-utilities\u002Fplaybooks\u002Fenhance-prompt\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7F518SX707EB3X42B2V7HRA","design-md","Analyze Stitch projects and synthesize a semantic design system into DESIGN.md files","https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-utilities\u002Fplaybooks\u002Fdesign-md\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7F5148PVYTA76NR3X0YK8SK","stitch::upload-to-stitch","Upload local assets (images, mockups, extracted HTML, design markdown) to a Stitch project. ALWAYS use this skill when you need to upload visual assets, HTML pages, or design docs to Stitch, particularly when direct MCP tool calls fail or truncate due to base64 token limits.","https:\u002F\u002Fgithub.com\u002F26BB\u002Fagent-fleet-os\u002Fblob\u002Fmain\u002Fstitch agent\u002Fplugins\u002Fstitch-design\u002Fplaybooks\u002Fupload-to-stitch\u002FSKILL.md",[],[]]