nathan-standards

Enforce Nathan development standards for n8n workflows, Python modules, and webhook contracts.

4|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/89jobrien/steve --skill nathan-standards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nathan-standards
Source: https://github.com/89jobrien/steve/tree/main/steve/skills/nathan-standards
Command: npx skills add https://github.com/89jobrien/steve --skill nathan-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Nathan standards establish consistent patterns for building within the Nathan project, including n8n workflows, Python patterns, and project conventions to enable reliable automation and maintainable code.

Core Features & Use Cases

  • n8n Workflow Standards: structure, validation, and registry patterns
  • Python Patterns: module structure, clean code, and testability
  • Spec-Driven Development: feature specs, tasks, and orchestration
  • Agent-Oriented Design: contract-driven webhook commands and ADR alignment

Quick Start

Create a new n8n webhook workflow for Jira ticket creation following the registry pattern.

Frequently Asked Questions about nathan-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize n8n workflows for Jira automation?

Nathan standards enforce consistent patterns for n8n workflows, including structure, validation, and registry formats. Apply these conventions when creating webhook workflows for Jira ticket creation or modification to ensure reliable automation across the Nathan project.

What Python patterns should I follow in Nathan automation projects?

Nathan standards specify module structure, clean code practices, and testability requirements for Python helpers and templating modules. These patterns ensure maintainable code within the larger n8n-Jira automation system.

How do I design webhook command contracts for n8n workflows?

Nathan standards define contract-driven webhook command design aligned with agent-oriented principles. Structure your webhook payloads and responses according to these specifications to integrate seamlessly with the Nathan automation registry.

Can I use spec-driven development with n8n and Python automation?

Yes. Nathan standards support spec-driven development through agent-os commands, enabling you to define feature specs and orchestrate tasks across n8n workflows and Python modules while maintaining consistent patterns and ADR alignment.

What conventions apply to n8n workflow registry configurations?

Nathan standards specify naming conventions, file organization, and configuration formats for the workflow registry. Follow these to enable reliable registration and retrieval of n8n workflows within the Nathan project.

Do I need to follow environment variable patterns in Nathan workflows?

Yes. Nathan standards define required environment variable usage and naming conventions across n8n workflows and Python code. Adhering to these patterns ensures consistent configuration management and deployment reliability.