Run any Skill in Manus with one click

growthub-workspace-template-export

Stars47

Forks12

UpdatedJuly 5, 2026 at 16:33

Convert any private-repo workspace variant (a customized growthub.config.json) into a clean, non-secret, production-ready seeded workspace template registered on the canonical Discover CLI pathway — export + sanitize with a verification gate, register the seed + WORKSPACE_TEMPLATES entry (src AND committed dist), mirror the seed contract tests, and prove it with the real starter-init smoke, a boot, and a browser readback. Use when the user asks to turn a workspace variant/config into a template, export a seeded config from a private repo, add a workspace template to kit list/discover, or QA a template export end to end (e.g. the gtm-os and project-management templates).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Growthub-ai

Growthub-ai/growthub-local

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	growthub-workspace-template-export
description	Convert any private-repo workspace variant (a customized growthub.config.json) into a clean, non-secret, production-ready seeded workspace template registered on the canonical Discover CLI pathway — export + sanitize with a verification gate, register the seed + WORKSPACE_TEMPLATES entry (src AND committed dist), mirror the seed contract tests, and prove it with the real starter-init smoke, a boot, and a browser readback. Use when the user asks to turn a workspace variant/config into a template, export a seeded config from a private repo, add a workspace template to kit list/discover, or QA a template export end to end (e.g. the gtm-os and project-management templates).
helpers	["scripts/export-workspace-seed-template.mjs","scripts/workspace-template-smoke.mjs"]
subSkills	[]
selfEval	{"criteria":["the seed was produced by scripts/export-workspace-seed-template.mjs (or verified equivalent) with ZERO secret/PII findings — env-ref authRef names only, needs-connection statuses, EMPTY connectionIds, evidence keys cleared, widget row caches emptied, provenance.template/templateKind stamped","the template rides ONLY the canonical pathway (templates/seeded-configs/<slug>.config.json + one WORKSPACE_TEMPLATES entry) with cli/src/commands/kit.ts and the committed cli/dist/index.js updated in the same shape — no parallel mechanism","seed-contract vitest cases are mirrored for the new slug (provenance + rows schema; no secrets / no connectionIds; picker listing)","scripts/workspace-template-smoke.mjs is GREEN at config level for the new slug AND the existing project-management slug (regression), and GREEN with --boot for the new slug (served objects/dashboards/registry hygiene match the merged export)","a browser pass on the booted export confirmed Builder home lists the template dashboards, a dashboard opens with widgets, and /data-model renders the objects — with screenshots delivered","all release gates green (check:worker-kits, check:cli-package, check:monorepo-boundary, freeze:check, version-sync --require-bump-if-source-changed, release:check)"],"maxRetries":3}

growthub-workspace-template-export

Golden-path doc (read it first, in full): docs/WORKSPACE_TEMPLATE_GOLDEN_PATH_V1.md — the one mechanism, the sanitation contract, the registration steps, and the honesty rules. This skill is the executable summary; the doc is the contract. Reference implementation: the gtm-os template (seed, registry entry, tests, smoke, proof in docs/proofs/pr270/PROOF.md).

Core loop

Recon — read cli/src/starter/init.ts (applySeededConfig merge), cli/src/commands/kit.ts (WORKSPACE_TEMPLATES registry), and one existing seed (templates/seeded-configs/gtm-os.config.json). The pathway is slug-file + registry entry; nothing else.
Export + sanitize — run node scripts/export-workspace-seed-template.mjs --config <variant config> --slug <slug> --out /tmp/<slug>.config.json --definition-rows <governed definition object ids>. The script enforces the whole sanitation contract and refuses to write on any secret/PII finding. Definition rows are configuration (blueprints, nav, agent setup) — never run evidence, never CRM/PII data.
Adversarial audit of the seed — even a validated exporter output gets a manual pass: entropy scan for token-shaped strings, api-registry rows carry env-ref NAMES + needs-connection + empty connectionIds, no .records shapes, dashboards/canvas widget row caches empty.
Register — copy the seed into cli/assets/worker-kits/growthub-custom-workspace-starter-v1/templates/seeded-configs/<slug>.config.json; add ONE WORKSPACE_TEMPLATES entry in cli/src/commands/kit.ts; apply the SAME change in the same shape to the committed cli/dist/index.js (this repo slice cannot rebuild the bundle — src and dist must not drift); mirror the seed-contract + picker vitest cases.
Prove — node scripts/workspace-template-smoke.mjs --slug <slug> (config level, plus project-management as regression), then --boot --port 3779 [--link-node-modules <dir>] for the served readback. Finish with a browser pass on the booted export (dashboards render with widgets, /data-model lists the objects) and bank screenshots. Then run every release gate.

Hard rules

Secrets: .env.local / runtime env only; seeds carry env-key NAMES (authRef) and nothing else. The exporter's verification gate is a hard stop — fix the variant, never weaken the gate.
Mirror, don't invent: one seed file + one registry entry. No new template mechanisms, no per-template routes, no config forks.
Connection ids, sync proofs, run receipts, and test evidence are operator-owned runtime state — they NEVER ship in a template.
Proof is a real export + boot + browser readback, not source claims. The strict validateWorkspaceConfig rejecting the merged file is expected (it gates PATCH bodies) — the boot is the acceptance test.
Keep the committed dist in lockstep with src for every registry edit.

More from this repository

same repository

governed-console

Growthub-ai/growthub-local

Operate the governed-universe MCP tools over a Growthub workspace — describe the workspace, traverse the metadata graph, simulate causal impact and blast radius, check ship-readiness, dry-run a PATCH with preflight_patch, and convert findings into governed next actions. Use whenever you need to answer "what exists, what depends on what, what would break, is it ready, and what governed call should happen next" in a workspace that contains growthub.config.json.

2026-07-1947

workspace-causal-cli

Growthub-ai/growthub-local

Run the offline causal-intelligence CLI over a governed Growthub workspace — growthub plan (blast radius, stale surfaces, lineage), growthub patch (offline allowlisted edit with impact + compliance, PR-ready), growthub capture (live vs repo drift), growthub readiness (ship verdict across forks). Use for scripted or CI-side impact analysis when you want JSON output instead of MCP tool calls.

2026-07-1947

growthub-custom-workspace-starter

Growthub-ai/growthub-local

Baseline primitive for every Growthub governed workspace. Routing menu for the Custom Workspace Operator — delegates to the operator runbook (`skills.md`), the session-memory template (`templates/project.md`), the self-evaluation contract (`templates/self-eval.md`), the safe-shell helpers layer (`helpers/`), and the parallel sub-skill convention (`skills/`). Invoked when the user starts a greenfield workspace via `growthub starter init`, imports a GitHub repo or skills.sh skill via `growthub starter import-repo`/`import-skill`, or downloads this kit directly via `growthub kit download`.

2026-07-1947

governed-workspace-mutation

Growthub-ai/growthub-local

The two canonical Growthub workspace mutation calls and the verified protocol — PATCH /api/workspace (allowlist dashboards, widgetTypes, canvas, dataModel) and POST /api/workspace/sandbox-run. Read before changing workspace configuration or executing anything in a governed workspace. Mutations are runtime-enforced; this card keeps you on the sanctioned lanes.

2026-07-0847

workspace-helper

Growthub-ai/growthub-local

Draft dashboards, widgets, API registry rows, custom business objects, and swarm graphs for a governed Growthub workspace via the workspace helper — a propose-only planning engine whose output is applied through an explicit governed apply step. Use when asked to build a dashboard, create a custom object, register an API, scaffold a widget, repair broken references, or explain a workspace object.

2026-07-0847

growthub-auth

Growthub-ai/growthub-local

Sign in, confirm identity, and sign out of hosted Growthub via `growthub auth login` / `whoami` / `logout`. Use when the user needs to authenticate before Workflows / Saved Workflows / Pipeline execution, verify the active session, script auth with a pre-issued token, or opt out of telemetry.

2026-07-0847

name	growthub-workspace-template-export
description	Convert any private-repo workspace variant (a customized growthub.config.json) into a clean, non-secret, production-ready seeded workspace template registered on the canonical Discover CLI pathway — export + sanitize with a verification gate, register the seed + WORKSPACE_TEMPLATES entry (src AND committed dist), mirror the seed contract tests, and prove it with the real starter-init smoke, a boot, and a browser readback. Use when the user asks to turn a workspace variant/config into a template, export a seeded config from a private repo, add a workspace template to kit list/discover, or QA a template export end to end (e.g. the gtm-os and project-management templates).
helpers	["scripts/export-workspace-seed-template.mjs","scripts/workspace-template-smoke.mjs"]
subSkills	[]
selfEval	{"criteria":["the seed was produced by scripts/export-workspace-seed-template.mjs (or verified equivalent) with ZERO secret/PII findings — env-ref authRef names only, needs-connection statuses, EMPTY connectionIds, evidence keys cleared, widget row caches emptied, provenance.template/templateKind stamped","the template rides ONLY the canonical pathway (templates/seeded-configs/<slug>.config.json + one WORKSPACE_TEMPLATES entry) with cli/src/commands/kit.ts and the committed cli/dist/index.js updated in the same shape — no parallel mechanism","seed-contract vitest cases are mirrored for the new slug (provenance + rows schema; no secrets / no connectionIds; picker listing)","scripts/workspace-template-smoke.mjs is GREEN at config level for the new slug AND the existing project-management slug (regression), and GREEN with --boot for the new slug (served objects/dashboards/registry hygiene match the merged export)","a browser pass on the booted export confirmed Builder home lists the template dashboards, a dashboard opens with widgets, and /data-model renders the objects — with screenshots delivered","all release gates green (check:worker-kits, check:cli-package, check:monorepo-boundary, freeze:check, version-sync --require-bump-if-source-changed, release:check)"],"maxRetries":3}

growthub-workspace-template-export

Core loop

Recon — read cli/src/starter/init.ts (applySeededConfig merge), cli/src/commands/kit.ts (WORKSPACE_TEMPLATES registry), and one existing seed (templates/seeded-configs/gtm-os.config.json). The pathway is slug-file + registry entry; nothing else.
Export + sanitize — run node scripts/export-workspace-seed-template.mjs --config <variant config> --slug <slug> --out /tmp/<slug>.config.json --definition-rows <governed definition object ids>. The script enforces the whole sanitation contract and refuses to write on any secret/PII finding. Definition rows are configuration (blueprints, nav, agent setup) — never run evidence, never CRM/PII data.
Adversarial audit of the seed — even a validated exporter output gets a manual pass: entropy scan for token-shaped strings, api-registry rows carry env-ref NAMES + needs-connection + empty connectionIds, no .records shapes, dashboards/canvas widget row caches empty.
Register — copy the seed into cli/assets/worker-kits/growthub-custom-workspace-starter-v1/templates/seeded-configs/<slug>.config.json; add ONE WORKSPACE_TEMPLATES entry in cli/src/commands/kit.ts; apply the SAME change in the same shape to the committed cli/dist/index.js (this repo slice cannot rebuild the bundle — src and dist must not drift); mirror the seed-contract + picker vitest cases.
Prove — node scripts/workspace-template-smoke.mjs --slug <slug> (config level, plus project-management as regression), then --boot --port 3779 [--link-node-modules <dir>] for the served readback. Finish with a browser pass on the booted export (dashboards render with widgets, /data-model lists the objects) and bank screenshots. Then run every release gate.

Hard rules

Secrets: .env.local / runtime env only; seeds carry env-key NAMES (authRef) and nothing else. The exporter's verification gate is a hard stop — fix the variant, never weaken the gate.
Mirror, don't invent: one seed file + one registry entry. No new template mechanisms, no per-template routes, no config forks.
Connection ids, sync proofs, run receipts, and test evidence are operator-owned runtime state — they NEVER ship in a template.
Proof is a real export + boot + browser readback, not source claims. The strict validateWorkspaceConfig rejecting the merged file is expected (it gates PATCH bodies) — the boot is the acceptance test.
Keep the committed dist in lockstep with src for every registry edit.