Skip to content

Add Shipyard power - #218

Open
daniellle wants to merge 3 commits into
kirodotdev:mainfrom
shipyard:add-shipyard-power
Open

daniellle wants to merge 3 commits into
kirodotdev:mainfrom
shipyard:add-shipyard-power

Conversation

@daniellle

Copy link
Copy Markdown

Issue #, if available: N/A (also submitted through https://kiro.dev/powers/submit/)

Description of changes:

Adds Shipyard, a power that puts a GitHub repo on Shipyard and checks its preview environments: one live environment per branch.

What's added

  • shipyard/, in the Agent Plugins format:
    • plugin.json: name shipyard, version 0.2.1
    • mcp.json: Shipyard's hosted MCP server, https://mcp.shipyard.build/mcp (Streamable HTTP, OAuth sign-in in the browser)
    • skills/shipyard/SKILL.md, plus references/compose.md (loaded only when the repo has no Docker Compose file)
    • skills/shipyard/scripts/shipyard-git.sh: the git steps the skill takes before a push, as one tested script
    • README.md, and a .gitattributes that keeps the script's LF line endings
  • A README entry for Shipyard, in alphabetical order.

There's nothing to install and no token to paste: the user connects from Kiro, signs in to Shipyard, and Kiro keeps the token.

Source
These files are copied from shipyard/shipyard-plugins, tag shipyard-hosted-v0.2.1. That repo is the source of truth, and we'll send updates here as PRs. The only difference from it is name, which is shipyard here instead of shipyard-hosted.

What the agent can do

  • plan_application: preview adding a pushed GitHub branch as an app (read-only)
  • create_application, update_application: create an app from a confirmed plan, or change its branches, services, routes or repos
  • get_environments, get_environment, get_build_history, get_failure_details, get_build_logs: check environments, builds and failures

Safety

  • The skill asks the user before it commits, pushes, creates a repo, or creates or changes an app.
  • Every git step goes through shipyard-git.sh. The agent passes it file paths and messages in files, never on a shell command line. The script:
    • checks the files and the commits a push would send for anything that looks like a secret, and asks the user about each match
    • never commits .env files, keys, Terraform state or dependency folders
    • pushes only to GitHub, and never prints file contents
  • The script needs bash and perl. Both come with macOS and most Linux distributions; on Windows, use Git Bash.
  • The skill never asks the user to paste a token, and the server exposes only the tools the sign-in's scopes allow.

Testing
Imported into Kiro IDE from this branch, then on a test repo with untracked code, a .env and a Terraform state file:

  • clicked Try power
  • connected and signed in with OAuth
  • listed environments
  • added an app end to end: wrote the Compose file, flagged and left out .env and the state file, committed, pushed, planned, created and built the app, including env values set at create time

A note on Try power
This power has no POWER.md or steering files. Following Kiro's power-builder guidance for plugin-format powers, its onboarding lives in a skill. Kiro's built-in Try power prompt still looks for POWER.md, so the agent's first line can say none was found before it loads the skill and carries on normally. Happy to adjust if you'd prefer a different layout.

Contacts

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

daniellle and others added 3 commits November 16, 2026 19:02
Shipyard's hosted MCP server (https://mcp.shipyard.build/mcp) with OAuth
sign-in, and a skill that takes a new user from no account to a running
preview environment, including writing a Docker Compose file when the repo
has none. Copied from shipyard/shipyard-plugins (hosted/), named shipyard.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copies skills/shipyard/SKILL.md and references/compose.md from https://github.com/shipyard/shipyard-plugins/releases/tag/shipyard-hosted-v0.2.0. The compose check no longer loads .env, committed files never hold a literal secret, and commits name their paths.
Copies hosted/ from shipyard/shipyard-plugins tag shipyard-hosted-v0.2.1:
first-run onboarding, the git helper script the skill runs before a push
(skills/shipyard/scripts/shipyard-git.sh), and the plugin's README.
.gitattributes keeps the script's LF line endings. As before, only
plugin.json's name differs (shipyard instead of shipyard-hosted).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

2 participants