newt-blueprint-generator_skill

Overview

This skill generates and validates Pangolin Newt blueprint configurations in YAML or Docker Labels format. It helps create proxy and client resources, configure authentication and access rules, and produce Docker Compose labels for containerized deployments. Use it to ensure blueprints meet protocol-specific constraints and naming/port uniqueness rules.

How this skill works

Provide resource requirements (proxy vs client, protocol, domain or proxy-port, targets, auth and rules) and choose output format (YAML or Docker Labels). The skill constructs the blueprint, applies validation rules (protocol constraints, port and domain uniqueness, target method requirements, auth restrictions) and returns a ready-to-use YAML file or Docker Compose labels. It also emits clear validation errors and remediation suggestions when constraints are violated.

When to use it

• Creating standalone Newt YAML blueprints for API or CLI deployment
• Defining Pangolin resources inside Docker Compose via pangolin.* labels
• Configuring HTTP, TCP, or UDP proxy resources and associated targets
• Setting up Olm client resources (SSH, RDP) and port mappings
• Enabling and validating authentication (SSO, basic auth, pincode, password)
• Converting blueprints between YAML and Docker label formats and validating them

Best practices

• Use descriptive kebab-case resource IDs (e.g., web-app-prod)
• Group related targets under a single resource to simplify management
• Enable authentication for sensitive HTTP resources and avoid auth on TCP/UDP
• Document proxy-port assignments to prevent duplicates across resources
• Specify site explicitly for multi-site deployments to avoid misassignment
• Order access rules from most specific to least specific and validate early

Example use cases

• Generate a YAML blueprint for a public HTTP service with SSO and header rules
• Create Docker labels for multiple containers that merge into a single proxy resource
• Produce a client resource definition for an RDP service accessible via Olm
• Validate a mixed blueprint and fix errors like duplicate full-domain or proxy-port
• Convert a targets-only resource from Docker labels into a standalone YAML file