workflow-template-extractor

To turn a real project into a reusable template, the skill copies the source repository into a templates directory, removes secrets and branding, replaces sensitive values with neutral placeholders, and generates a README.md, .env.local.example, and metadata.json for quick setup.

Removing secrets and branding from a project involves identifying sensitive values and replacing them with neutral placeholders. This de-secret and de-branding process ensures the copied project is safe to share as a baseline template for future builds.

Generating an .env.local.example file from an existing project happens during the template extraction process. The skill normalizes template entry points by creating this file alongside a README.md and metadata.json to document required environment variables with neutral placeholders.

You can specify which files to keep, remove, or generalize when extracting a project template by providing an extract_spec.md file. This specification guides the deterministic copy, de-secret, and de-branding process for your source repository.

Template extraction works with any project structure located at your defined source_repo_root. The deterministic process copies the entire project, applies de-branding and secrets removal, and verifies that the resulting template is runnable.