skills/89jobrien/nathan-standards/SKILL.md
Development standards for the Nathan n8n-Jira agent automation system. Covers n8n workflows, Python patterns, and project conventions.
npx skillsauth add aiskillstore/marketplace nathan-standardsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Standards and patterns for developing within the Nathan project - an n8n-Jira agent automation system.
Invoke this skill when:
Nathan follows a layered architecture:
External Service (Jira) <-- n8n Workflows <-- Python Agent Service
(credentials) (webhook calls)
Core Principle: n8n owns all external credentials. Python services call n8n webhooks with shared secret authentication.
For detailed workflow patterns, load references/n8n-workflow-patterns.md.
Every webhook workflow must follow this pattern:
Webhook --> Validate Secret --> Operation --> Respond to Webhook
| | |
v v v
Unauthorized Error Response Success Response
Response (401) (500) (200)
{
"id": "validate-secret",
"name": "Validate Secret",
"type": "n8n-nodes-base.if",
"typeVersion": 2,
"parameters": {
"conditions": {
"conditions": [{
"leftValue": "={{ $json.headers['x-n8n-secret'] }}",
"rightValue": "={{ $env.N8N_WEBHOOK_SECRET }}",
"operator": { "type": "string", "operation": "equals" }
}]
}
}
}
All responses must follow this shape:
{ "success": true, "data": {...}, "status_code": 200, "error": null }
{ "success": false, "data": {}, "status_code": 500, "error": "message" }
In n8n expressions within JSON, escape properly:
| Wrong | Correct |
|-------|---------|
| .map(x => "${x}") | .map(x => '"' + x + '"') |
| .join('\n') | .join('\\n') |
| .replaceAll('\n', ' ') | .replaceAll('\\n', ' ') |
For detailed patterns, load references/python-patterns.md.
nathan/
helpers/ # Shared utilities (workflow registry, etc.)
workflows/ # n8n workflow JSON + registry.yaml per category
templating/ # YAML-to-JSON template engine
scripts/ # Standalone runnable scripts
# Required imports pattern
from __future__ import annotations
from typing import Any
from pathlib import Path
import logging
logger = logging.getLogger(__name__)
# Type hints required, use T | None not Optional[T]
async def trigger_workflow(url: str, params: dict[str, Any]) -> dict[str, Any]:
...
# registry.yaml
version: "1.0.0"
description: "Registry description"
commands:
command_name:
endpoint: /webhook/endpoint-path
method: POST
required_params:
- param1
optional_params:
- param2
description: What this command does
example:
param1: "value"
Use agent-os commands for feature development:
/shape-spec - Initialize and shape specification/write-spec - Write detailed spec document/create-tasks - Generate task list from spec/orchestrate-tasks - Delegate to subagentsSpecs live in agent-os/specs/[spec-name]/ with:
spec.md - Feature specificationtasks.md - Implementation tasks with checkboxesorchestration.yml - Subagent delegation configuv sync # Install dependencies
uv run pytest # Run tests
uv run pytest path/to/test.py -v # Single test file
uvx ruff check . # Lint
uvx ruff format . # Format
docker compose -f docker-compose.n8n.yml up -d # Start n8n
| Variable | Purpose |
|----------|---------|
| N8N_WEBHOOK_SECRET | Shared secret for webhook auth |
| N8N_API_KEY | n8n Public API key |
| JIRA_DOMAIN | Jira Cloud domain |
| JIRA_EMAIL | Jira account email |
| JIRA_API_TOKEN | Jira API token |
| Type | Convention | Example |
|------|------------|---------|
| Workflow JSON | kebab-case.json | jira-get-ticket.json |
| Python modules | snake_case.py | n8n_workflow_registry.py |
| Test files | test_*.py | test_parser.py |
| Registry | registry.yaml | per workflow category |
development
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.