mirror of
https://github.com/czlonkowski/n8n-skills.git
synced 2026-03-17 07:53:08 +00:00
## Skill #1 Complete - n8n Expression Syntax ✅ **4 Evaluations Created**: - eval-001: Missing curly braces - eval-002: Webhook body data access (critical!) - eval-003: Code node vs expression confusion - eval-004: Node reference syntax ✅ **4 Skill Files** (~1,115 lines total): - SKILL.md (285 lines) - Core concepts, under 500 line limit - COMMON_MISTAKES.md (380 lines) - 15 common errors with fixes - EXAMPLES.md (450 lines) - 10 real working examples - README.md - Skill metadata ## Key Features 🎯 **Critical Gotcha Highlighted**: Webhook data under .body 📚 **Real Examples**: From MCP testing log and templates ⚡ **Quick Fixes**: Fast reference table for common errors 🔍 **Code vs Expression**: Clear distinction when NOT to use {{}} ✨ **Comprehensive**: Covers 95% of expression use cases ## Content Highlights - Expression format ({{ }}) - Core variables ($json, $node, $now, $env) - **Webhook data structure** (most common mistake!) - When NOT to use expressions (Code nodes) - Array/object access patterns - Date/time formatting - String manipulation - Conditional logic ## Based on MCP Testing All examples verified against real: - Webhook node structure from get_node_essentials - Template #2947 (Weather to Slack) - Code node guide from tools_documentation - Real error messages from validation ## Next: Skill #2 - n8n MCP Tools Expert 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> Conceived by Romuald Członkowski - https://www.aiadvisors.pl/en
24 lines
1.0 KiB
JSON
24 lines
1.0 KiB
JSON
{
|
|
"id": "expr-004",
|
|
"skills": ["n8n-expression-syntax"],
|
|
"query": "How do I reference data from my 'HTTP Request' node in a later Slack node? I need to access the response data.",
|
|
"expected_behavior": [
|
|
"Provides correct $node syntax with quotes around node name",
|
|
"Shows example: {{$node[\"HTTP Request\"].json.fieldName}}",
|
|
"Explains that node names with spaces require bracket notation and quotes",
|
|
"Warns that node names are case-sensitive and must match exactly",
|
|
"Provides multiple examples from real workflows"
|
|
],
|
|
"baseline_without_skill": {
|
|
"likely_response": "May suggest generic data passing or variable references, might not know n8n $node syntax",
|
|
"expected_quality": "Medium - might guess at syntax but miss specifics like quotes and case sensitivity"
|
|
},
|
|
"with_skill_expected": {
|
|
"response_quality": "High - precise $node syntax with proper quoting",
|
|
"uses_skill_content": true,
|
|
"provides_correct_syntax": true,
|
|
"explains_case_sensitivity": true,
|
|
"shows_multiple_examples": true
|
|
}
|
|
}
|