workflow-template-extractor
Skill337 starsChanged 10 months agoMITView on GitHub
Extract a shareable runnable template under templates/NNN-slug/ from a real project: copy + de-brand + remove secrets + add env examples + docs, with minimal refactors. Use when you have a working project and want to turn it into a template.
- Reads credentials
In this repository40 other files it gives its agents.
- review-clean-codeSkill
- review-doc-consistencySkill
- review-merge-readinessSkill
- workflow-execute-plansSkill
- workflow-template-extractorSkill
- workflow-template-seederSkill
- cloudflareSkill
- deep-researchSkill
- mcp-cloudflareSkill
- mcp-stripeSkill
- mcp-supabaseSkill
- publish-x-articleSkill
- review-clean-codeSkill
- review-doc-consistencySkill
- review-merge-readinessSkill
- review-qualitySkill
- review-react-best-practicesSkill
- review-seo-auditSkill
- skill-creatorSkill
- skill-evolutionSkill
- skill-improverSkill
- stripeSkill
- supabaseSkill
- tool-ast-grep-rulesSkill
- tool-better-authSkill
- tool-design-style-selectorSkill
- tool-hooks-doctorSkill
- tool-openclawSkill
- tool-programmatic-seoSkill
- tool-schema-markupSkill
- tool-systematic-debuggingSkill
- tool-ui-ux-pro-maxSkill
- tool-x-article-publisherSkill
- workflow-brainstormSkill
- workflow-creatorSkill
- workflow-execute-plansSkill
- workflow-feature-shipperSkill
- workflow-project-intakeSkill
- workflow-ship-fasterSkill
- workflow-template-seederSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 36
Remove secret values from all files (.env*, config, hard-coded tokens).
- Very specific: line 48
Ensure scripts exist for dev, build, start
- Very specific: line 49
If lint/typecheck/format are missing and the repo is TS-heavy, add minimal guardrails (avoid heavy governance)
- Distinctive: line 60
Never commit secret values.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Workflow: Template Extractor (Real Project → Template)
Goal: Turn a real project into a shareable, runnable template in templates/ with minimal manual cleanup.
This is intended for “proven projects” you want to reuse as a baseline for future builds.
Input (pass paths only)
source_repo_root: Path to the real projecttarget_repo_root: Ship Faster repository root (wheretemplates/lives)run_dir:runs/template-extractor/active/<run_id>/extract_spec.md: What to keep/remove/generalize (brand, copy, assets, integrations, auth gates)
Output (persisted)
03-plans/extract-plan.md05-final/extract-summary.mdtemplates/<NNN>-<slug>/(runnable)
Workflow
0) Initialize
- Create
run_dir. - Decide
<slug>and<NNN>(next available template number). - Copy
source_repo_root→templates/<NNN>-<slug>/(no build outputs, no caches).
1) De-secrets + de-brand
Must do:
- Remove secret values from all files (
.env*, config, hard-coded tokens). - Replace project IDs (Stripe price IDs, Supabase URLs/keys, webhook secrets) with env var keys.
- Replace branding (names/domains/logos) with neutral placeholders unless the template is intentionally branded.
2) Normalize template entry docs
Required files:
README.md(5‑minute runnable).env.local.example(keys only)metadata.json(name + description)
Recommended:
- Ensure scripts exist for
dev,build,start - If lint/typecheck/format are missing and the repo is TS-heavy, add minimal guardrails (avoid heavy governance)
3) Verification
Document in 05-final/extract-summary.md:
- install works
devstartsbuildsucceeds (or clearly document why it can’t without credentials)
Constraints
- Never commit secret values.
- Extraction should be “copy + cleanup”, not a refactor project.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

