# Move CI Jobs to Peak Runners

Teams need a faster GitHub Actions runner setup without manually editing every workflow. This skill runs the Peak workflow, guides authentication, and reports the proposed changes for review.

## Install

```bash
npx skillstore add peakinc/peak-setup
```

## Metadata

- Status: approved
- Slug: peakinc-peak-setup
- Skillstore revision: r1
- Version status: missing
- Tree hash: cfc43ef8793e8fb3feb98485171fba904f870b9628ec1b74d92d38d7b1560bec
- Author: peakinc
- GitHub username: peakinc
- License: MIT
- Repository: https://github.com/peakinc/skills/tree/650e73ec5600d12f4d900398a3248bbd38f10899/skills/peak-setup
- Ref: 5526951beaeca22519572a471618555839b53b05
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/peakinc-peak-setup
- Manifest: https://skillstore.pages.dev/api/skills/peakinc-peak-setup/manifest

## Capabilities

- Checks repository, GitHub remote, Node version, and organization ownership prerequisites.
- Runs the Peak initialization CLI with structured JSON output.
- Relays authorization links, user codes, pull request links, and failure details.
- Explains jobs that require the Peak wizard because they use complex runner configurations.
- Provides a manual runs-on replacement when the CLI commands cannot run.
- Describes how to undo the branch created by the initialization command.

## Use Cases

- Migrate a GitHub Actions repository: Set up Peak runners across eligible workflow jobs and return a pull request for the repository owner to review.
- Investigate jobs needing translation: Identify matrix jobs, operating system legs, and runner expressions that require the Peak wizard or manual handling.
- Prepare a cautious runner transition: Apply the runner change through a pull request, preserve the existing CI, and explain the steps for validation and rollback.

## Prompt Templates

### Start Peak setup

```
Set up Peak in this repository. Check the prerequisites first, run the standard initialization flow, and report the pull request link.
```

### Review the migration plan

```
Inspect this repository for Peak setup readiness. Summarize eligible jobs, blocked jobs, required authentication, and the expected workflow change before running the CLI.
```

### Handle hard jobs

```
Run the Peak setup flow and handle jobs that use matrices, expressions, or non-Linux runners. Report translated jobs, skipped jobs, reasons, and the pull request.
```

### Use a controlled fallback

```
If Peak initialization cannot run, identify each eligible GitHub Actions job, propose the exact runs-on migration, preserve all other workflow content, and prepare the changes for review.
```

## Limitations

- The setup requires a GitHub organization owner and does not support personal accounts.
- Node 22.13 or newer must be installed in the repository environment.
- The CLI and wizard depend on network access and third-party Peak packages.
- The skill does not merge pull requests or independently verify the resulting CI run.

## Best Practices

- Review the generated pull request before merging and confirm every runner change.
- Keep the existing CI until the first successful Peak run validates the migration.
- Never expose PEAK\_TOKEN or other credentials in logs, prompts, or pull request text.

## Anti Patterns

- Do not merge the pull request automatically.
- Do not edit workflow steps or unrelated settings during runner migration.
- Do not run the setup without reviewing the package source, version, and data-transfer behavior.

## Security Audit

- Audited at: 2026-09-13T16:33:37.803\+00:00
- Summary: All 25 external-command alerts are false positives because they match Markdown backticks and documented command text, not executable Ruby or shell code. The two URL alerts are also false positives because they are fixed documentation links; however, the instructions introduce supply-chain and workflow-disclosure risks through mutable npx packages and remote workflow processing.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0