Use {{}} syntax for all dynamic content; access current node data with $json , other nodes with $node[\"Node Name\"] , and webhook payloads from $json.body (not root)
Node names are case-sensitive and require quotes; field names with spaces use bracket notation like $json['field name']
Code nodes use direct JavaScript access without {{}} braces; expressions don't work in webhoo
Fetches n8n-expression-syntax from czlonkowski/n8n-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/n8n-expression-syntax
Restart Cursor to activate n8n-expression-syntax. Access via /n8n-expression-syntax in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
// Node without spaces{{$node["Set"].json.value}}// Node with spaces (common!){{$node["HTTP Request"].json.data}}{{$node["Respond to Webhook"].json.message}}// Webhook node{{$node["Webhook"].json.body.email}}
Combine Variables
// Concatenation (automatic)Hello{{$json.body.name}}!// In URLshttps://api.example.com/users/{{$json.body.user_id}}// In object properties{"name":"={{$json.body.name}}","email":"={{$json.body.email}}"}
When NOT to Use Expressions
❌ Code Nodes
Code nodes use direct JavaScript access, NOT expressions!
// ❌ WRONG in Code nodeconst email ='={{$json.email}}';const name ='{{$json.body.name}}';// ✅ CORRECT in Code nodeconst email = $json.email;const name = $json.body.name;// Or using Code node APIconst email = $input.item.json.email;const allItems = $input.all();
❌ Webhook Paths
// ❌ WRONGpath:"{{$json.user_id}}/webhook"// ✅ CORRECTpath:"user-webhook"// Static paths only
❌ Credential Fields
// ❌ WRONGapiKey:"={{$env.API_KEY}}"// ✅ CORRECTUse n8n credential system, not expressions
Validation Rules
1. Always Use {{}}
Expressions must be wrapped in double curly braces.
❌ $json.field✅ {{$json.field}}
2. Use Quotes for Spaces
Field or node names with spaces require bracket notation:
❌ {{$json.field name}}✅ {
✓
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
