Skills peak-setup

📦

peak-setup

Name: peak-setup
Author: peakinc

Content revision r1 High Risk ⚙️ External commands🌐 Network access

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.

Supports: Claude Codex Code(CC)

⚠️ 38 Poor

Maintain this Skill? Claim it ⚠️ 38 Poor

Stop for confirmation before installing.

Review the plan and obtain explicit user consent before changing files.

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "peak-setup" from https://skillstore.io/skills/peakinc-peak-setup.md and its manifest at https://skillstore.io/api/skills/peakinc-peak-setup/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/peakinc-peak-setup.md Signed manifest GET /api/skills/peakinc-peak-setup/manifest Signed lockfile GET /api/skills/peakinc-peak-setup/lockfile

Test it

Using "peak-setup". Set up Peak for this GitHub repository.

Expected outcome:

Prerequisites passed. Peak authentication is required. Open the provided sign-in link and approve access. The CLI will return a pull request after updating eligible runner labels.

Using "peak-setup". Why were some jobs not moved to Peak?

Expected outcome:

The plan identified jobs with matrix or runner expression complexity.
Those jobs require the Peak wizard or manual review.
The report includes each skipped job and its reason.

Using "peak-setup". The CLI cannot run. What should I do?

Expected outcome:

Use the manual fallback for eligible workflow jobs: change only the runs-on value, open a pull request, and leave the existing CI steps unchanged.

Security Audit

High Risk

v1 • 9/13/2026 Open versioned report

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.

Files scanned

Lines analyzed

Review items

False positives ignored

Confirmed security concerns (2)

High

SKILL.md:28 SKILL.md:60

Mutable Remote Package Execution

The instructions tell the agent to run npx -y with @peakinc/init@latest and @peakinc/wizard@latest in the repository. A future package release can execute with repository access before the user reviews a pull request.

The commands explicitly use npx -y and mutable @latest package tags, which directly establishes unattended remote package execution in the repository context.

Medium

SKILL.md:63

Workflow File Disclosure to External Service

The wizard path states that selected workflow files are sent to Peak over a network connection. This can disclose proprietary CI logic or configuration to an external service without a documented data review or local-only option.

The skill explicitly describes transmitting workflow files to Peak, but it provides no evidence that those files contain secrets or that the transfer is malicious; the concern is disclosure and consent.

Risk Factors

⚙️ External commands (25)

🌐 Network access (2)

SKILL.md:7 SKILL.md:8

Audited by: codex

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/peakinc-peak-setup/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/peakinc-peak-setup/security.svg)](https://skillstore.io/skills/peakinc-peak-setup?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/peakinc-peak-setup?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/peakinc-peak-setup/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/peakinc-peak-setup.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

peakinc. (2026). peak-setup security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/peakinc-peak-setup/audits/1

BibTeX citation

@techreport{peakinc-peakinc-peak-setup-2026,
  author = {peakinc},
  title = {peak-setup security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/peakinc-peak-setup/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "peak-setup security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "peakinc"
date-released: "2026-09-13"
url: "https://skillstore.io/skills/peakinc-peak-setup/audits/1"
identifiers:
  - type: other
    value: "skillstore:peakinc-peak-setup:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

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.

Try These Prompts

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.

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.

Avoid

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.