Skip to content

feat(skill): add deploy-setup skill — first-deploy walkthrough across 11 starters#27

Open
heznpc wants to merge 1 commit into
mainfrom
feat/deploy-setup-skill
Open

feat(skill): add deploy-setup skill — first-deploy walkthrough across 11 starters#27
heznpc wants to merge 1 commit into
mainfrom
feat/deploy-setup-skill

Conversation

@heznpc
Copy link
Copy Markdown
Member

@heznpc heznpc commented May 7, 2026

Closes the gap between scaffold (covered by create skill) and first release (currently manual per-template docs).

What it does

skills/deploy-setup/SKILL.md walks a developer through:

  1. Detect which Starter Series template the cwd came from
  2. Inspect that template's cd*.yml for required secrets
  3. Diff against existing GitHub secrets (gh secret list)
  4. Prompt for missing values + register via gh secret set
  5. Provide registry-side OIDC URLs (npm/PyPI trusted publisher web UI)
  6. Trigger the first cd.yml run after explicit user confirmation
  7. Verify the release

Why

  • Existing competing skills (Buildkite Automation, OpenCode Project Setup, jeremylongshore's tonsofskills) cover adjacent niches but none own the scaffold→first-deploy axis across multiple stacks.
  • starter-series already owns the scaffold step via create skill + plugin + Anthropic Registry. Adding deploy-setup cements the loop before others generalize into it.

Safety

  • Never echoes secret values — always pipes to gh secret set --body
  • Dry-run mode supported
  • Never auto-triggers workflow_dispatch without 'yes'
  • Workflow files are read-only during this skill (this is setup, not editing)

Test plan

  • Local dry-run on a freshly scaffolded mcp-server-starter
  • Plugin manifest update follow-up (separate PR) to surface skill in marketplace
  • Anthropic Registry listing follow-up under io.github.starter-series/deploy-setup

…arter Series

Closes the gap between 'scaffolded' and 'first release published.' The new
skills/deploy-setup/SKILL.md captures, per template, the secrets and OIDC
trusted-publisher setup the user needs and walks them through gh CLI
interactions to land it.

Pairs with skills/create/SKILL.md: scaffold first, then this skill ferries
the project to its first release on the right registry. Pre-empts the
'one Claude Code skill that owns scaffold→deploy for the whole stack'
position before competing CI/CD skills (Buildkite skill, OpenCode setup
skill) generalise into the same niche.

Per-template coverage: mcp-server (npm OIDC), npm-package (npm OIDC),
mcp-server-python (PyPI OIDC), vscode-extension (VSCE_PAT/OVSX_PAT),
browser-extension (Chrome+Firefox publish creds), electron-app (releases),
react-native (Expo+Apple+Google), cloudflare-pages (CF API token),
discord/telegram-bot (Railway/Fly), docker-deploy (VPS SSH).

Safety rails: never echo secrets, never auto-trigger publish without
explicit user confirmation, dry-run mode supported.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant