Agent skill · software engineering · rknall
Newt Blueprint Generator
Generate and validate Pangolin Newt blueprint configurations in YAML or Docker Labels format. Use when creating Pangolin resource configurations, proxy resources, client resources, authentication settings, or Docker Compose blueprints.
Why this skill is useful
Provides specific YAML and Docker Labels configuration patterns for Pangolin Newt that the AI wouldn't reliably generate on its own.
What it needs
Requires newt installed locally. About 8k tokens when loaded. Last updated 2025-10-20. 58 stars on the source repository.
What this skill does
Newt Blueprint Generator Expert assistance for creating, validating, and managing Pangolin Newt blueprint configurations. When to Use This Skill This skill should be triggered when: Creating Pangolin blueprint configurations Generating YAML configuration files for Newt Creating Docker Compose files with Pangolin labels Configuring proxy resources (HTTP, TCP, UDP) Setting up client resources for Olm Configuring authentication (SSO, basic auth, pincode, password) Validating blueprint configurations Troubleshooting blueprint validation errors Converting between YAML and Docker Labels formats Overview Pangolin Blueprints are declarative configurations that allow you to define resources and their settings in a structured format. They support two formats: 1. YAML Configuration Files: Standalone configuration files 2. Docker Labels: Configuration embedded in Docker Compose files Blueprint Formats YAML Configuration Format YAML configs can be applied using: Newt CLI: Pass --blueprint-file /path/to/blueprint.yaml API: POST to /org/{orgId}/blueprint with base64-encoded JSON body Example Newt usage: Docker Labels Format For containerized applications, blueprints can be defined using Docker labels with the pangolin. prefix. Enable Docker socket access: Or use environment variable: Resource Types Proxy Resources Proxy resources expose HTTP, TCP, or UDP services through Pangolin. HTTP Proxy Resource Example TCP/UDP Proxy Resource Example Targets-Only Resources Simplified resources containing only target configurations: Note: When using targets-only resources, name and protocol fields are not required. Client Resources Client resources define proxied resources accessible via Olm client (SSH, RDP): Authentication Configuration Authentication is off by default. Enable by adding fields in the auth section. Note: Authentication is only allowed on HTTP resources, not TCP/UDP. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills rknall/newt-blueprint-generator