workflow-template-extractor

Copy a real project into templates/NNN-slug/ with de-branding and environment examples.

339|58|Updated Jan 10, 2026

Search Tags:#automation #template #templates #env-examples #de-branding #secrets-removal

Ready to run

npx skills add https://github.com/Heyvhuang/ship-faster --skill workflow-template-extractor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-template-extractor
Source: https://github.com/Heyvhuang/ship-faster/tree/main/skills/workflow-template-extractor
Command: npx skills add https://github.com/Heyvhuang/ship-faster --skill workflow-template-extractor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill turns a real software project into a shareable, runnable template under templates/NNN-slug/ by copying the project, removing secrets and branding, and adding environment examples to enable rapid reuse.

Core Features & Use Cases

Copy real projects into templates/NNN-slug/ for reuse as baseline templates.
De-secret and de-brand the copy, replacing sensitive values with neutral placeholders.
Normalize template entry points (README.md, .env.local.example, and metadata.json) to ensure a quick start.

Quick Start

Run the workflow-template-extractor on a real project by pointing:

source_repo_root to the real project
target_repo_root to the Ship Faster repository root
run_dir to runs/template-extractor/active/<run_id>/
extract_spec.md to specify what to keep/remove/generalize

Frequently Asked Questions about workflow-template-extractor

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

FAQPage Schema

How do I turn a real software project into a reusable template?▼

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.

What is the best way to remove secrets and branding from a project before sharing it as a template?▼

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.

How do I generate an .env.local.example file from an existing project?▼

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.

Can I specify which files to keep or remove when extracting a project template?▼

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.

Does template extraction work with any project structure?▼

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.