repo-config-emitter

Transform n8n workflow JSON, vercel.json, and package.json into canonical-shape substrate nodes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/NewEarthAI/vibecode-project-template --skill repo-config-emitter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-config-emitter
Source: https://github.com/NewEarthAI/vibecode-project-template/tree/main/.claude/skills/repo-config-emitter
Command: npx skills add https://github.com/NewEarthAI/vibecode-project-template --skill repo-config-emitter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the emission of in-repo n8n workflow topology to the substrate, simplifying the process of mapping project workflows and configurations.

Core Features & Use Cases

  • Automated Topology Emission: Reads in-repo n8n workflow JSON files, vercel.json, and package.json, transforming and emitting them as canonical-shape nodes into the substrate.
  • Use Case: Use this Skill after a change in your in-repo workflow JSON, vercel.json, or package.json to refresh the topology substrate, or when a fresh repository needs its topology populated.

Quick Start

Run the skill with the command: /repo-config-emit

Frequently Asked Questions about repo-config-emitter

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

FAQPage Schema
How do I emit n8n workflow JSON files into a topology substrate?

Emitting n8n workflow topology involves reading in-repo workflow JSON, vercel.json, and package.json files, then transforming and mapping them as canonical-shape nodes into the substrate. This synchronizes project configurations without requiring external dependencies.

What is the best way to refresh project topology after changing package.json or vercel.json?

Refreshing project topology is best handled by re-emitting your updated configuration files. The process reads the modified package.json, vercel.json, and workflow JSON to update the substrate with the latest canonical-shape nodes for configuration synchronization.

Do I need external dependencies to synchronize in-repo n8n workflows to the substrate?

No external dependencies are required to synchronize n8n workflows to the substrate. The emission process operates entirely within your repository using Bash and file reading permissions to parse and transform the local JSON configurations.

When should I run n8n topology config emission for my repository?

You should run n8n topology config emission when a fresh repository needs its topology populated, or immediately after making changes to your in-repo workflow JSON, vercel.json, or package.json to ensure the substrate stays synchronized.

What permissions are required to transform n8n workflow JSON into canonical-shape nodes?

Transforming n8n workflow JSON into canonical-shape nodes requires Bash and file reading permissions. These allow the emission process to access and parse your in-repo configuration files for substrate synchronization.