About this skill

Problem addressed

Auto Gen Wrap is documented only as an auto-gen-wrap wrapper, version 1.0.0, in dev-programming. It is not a general-purpose code-generation platform. It is aimed at cases where auto-gen-wrap is the underlying layer and you want an outer wrapper for invocation, parameter packaging, or adaptation.

How the skill works

Based on the current description, its core capability is a wrapper:

Provides an external interface around auto-gen-wrap.
Funnels direct calls to auto-gen-wrap through a single skill entry point.
Acts as an adapter in dev-programming workflows rather than defining new generation rules.

Because SKILL.md does not list generation targets, templates, languages, or parameters, treat it as a thin wrapper rather than a fully documented code-generation system.

Boundaries and notes

Good fit when you already know what auto-gen-wrap is for and only need a wrapper call layer.
Do not infer supported languages, output formats, or business templates from the current materials.
Verify the actual wrapper implementation and upstream auto-gen-wrap docs for parameters, output, and failure handling.
In production, validate with small samples that the wrapper does not change the original call semantics.

Screenshots

Use Cases

Add a unified wrapper entry point to an existing auto-gen-wrap test script.
Wrap auto-gen-wrap calls first to inspect request structure before debugging.
Consolidate auto-gen-wrap calls in a dev-programming workflow for team trials.
Add an adapter layer so upstream scripts do not call auto-gen-wrap directly.

Best For

Platform engineers maintaining internal tooling who need a single auto-gen-wrap entry point.
Integration engineers who want a wrapper between upstream scripts and auto-gen-wrap.
Developers debugging scripts who need to wrap inputs and call flow first.
Tech leads evaluating existing components without changing upstream business code.