Index of every page on this site: llms.txt
All skills
openclaw avatar

/release-peekaboo

@99bef5a
by openclawopenclaw/peekaboo5.5k stars
421
Run it yourself

Prepare, publish and verify Peekaboo through its hosted GitHub Actions release workflow.

Use this Skill: https://skilld.dev/gh/openclaw/peekaboo/release-peekaboo

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈27 tokens for metadata: the name and description. ≈624 when used: this file.

Description uses 1.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈107 characters, or 1.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Peekaboo Release

Read docs/RELEASING.md first; it is the source of truth. Follow repo AGENTS.md. Only .github/workflows/release.yml publishes openclaw/Peekaboo and @steipete/peekaboo. Never release or publish without an explicit release command; a rehearsal does not authorize publication.

  1. Prepare a PR with consistent version surfaces and dated root/CLI changelog sections, validated by the existing release preflight. Hosted Actions extracts notes from CHANGELOG.md; no separate notes file or local publisher is used. Merge the preparation PR and wait for green push CI on that exact commit.
  2. Rehearse from main with gh workflow run release.yml --ref main -f version=X.Y.Z -F dry_run=true. Review the frozen source and artifacts, approve the release environment, and verify the run succeeds without publication.
  3. With explicit publication authorization, create and push an annotated SSH-signed vX.Y.Z tag on the same verified commit, using the canonical release SSH key accepted by .github/release-allowed-signers. Resolve that key through the private credential guidance if needed; never copy private key material into the repo. Approve the publication run's release environment gate. Tag pushes also trigger other workflows; the release CI gate fails while checks are still running. Wait for them to succeed, then rerun failed release jobs as needed. Never replace a published tag or rebuild an existing version.
  4. Verify GitHub Release assets and checksums.txt, and compare the published notes to the root changelog. Check npm's exact version, dist-tag, tarball, integrity and publish time; compare the downloaded registry tarball's SHA-512 integrity with the exact tarball from the hosted run. Run published CLI proof with npm exec from /tmp so the checkout cannot shadow the package.
  5. Verify the Homebrew tap formula's version, URLs and checksums. Review and merge the Actions-created appcast closeout PR, then verify the feed on main and the post-release Unreleased section. Report the release/run/closeout links and any incomplete handoff. Retry hosted handoffs only after checking what is already published; do not overwrite an existing version.

Signing/notarization credentials stay in the hosted release environment; npm uses OIDC. Local terminal/fleet notarization helpers are qualification tools and are not an alternate publication path.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning24d3 checks · Risk MEDIUM
  • Gen Agent Trust Hub24d

    The skill automates complex software release processes involving sensitive credentials such as Apple Developer ID keys and npm tokens. It includes a risk-prone practice of writing private keys to the global /tmp directory, which could lead to credential exposure in multi-user environments.

  • Socket24d

    No alerts

  • Snyk24d

    Risk: LOW · No issues

Signed by skilld at 99bef5a. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 days ago.

Activeupdated last month
Other metadata
metadata
{
  "clawdbot": {
    "emoji": "👁️",
    "requires": {
      "bins": [
        "pnpm",
        "gh",
        "git",
        "node",
        "npm"
      ]
    }
  }
}

README badge

README badge for openclaw/peekaboo/release-peekaboo