keys-sync
From the author
Add the Release Manager's public key to the project KEYS file: check it meets the ASF strength floor, draft the KEYS diff, and emit the `svn` (or backend) commands and keyserver reminder for the RM to run. Never holds the private key, never commits.
Install
npx skills add apache/magpie --skill keys-sync -a claude-code
Installs to .claude/skills/keys-sync/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Contains hidden text (invisible characters, long comments or encoded blobs)Medium
Why 76
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- rc-cutapache/magpieEmit the paste-ready commands to tag an RC, build the source archive reproducibly, sign, checksum and stage it to the distribution backend (or, with ASF automated signing, the tag push that triggers CI). Never runs them: the RM does, with their own key and credentials.Other★ 135
- releasepaperclipai/paperclipCoordinate a full Paperclip release across engineering verification, npm, GitHub, smoke testing, and announcement follow-up. Use when leadership asks to ship a release, not merely to discuss versioning.Testing★ 110.2K
- issue-syncapache/magpieSynchronize a security issue in <tracker> with the state of its GitHub discussion, the <security-list> mailing thread, and any <upstream> PRs that fix it. The skill gathers all relevant signals and proposes label / milestone / assignee / field / draft-email updates — applying only what the user has explicitly confirmed. Suggests the next step in the handling process and prints the CVE allocation link when a CVE is needed.Security★ 135
- prepareapache/magpieDraft release-preparation artefacts for `<upstream>`: the planning issue, the version-bump and changelog prep PR (with the first-release review of what the source archive ships), the post-release dev-version bump PR, and, for ASF projects, the one-time `automated-signing` setup. Every output is a draft the RM confirms; nothing is merged, filed or sent.Planning★ 135
- git-syncEricTechPro/super-boardSync the current branch in one pass — commit the working tree as one commit per logical change (in the host repo's commit format, or the super-board writing standard), gate Supabase schema changes, merge-pull, resolve conflicts hunk by hunk, then push without force. Use when the user runs /git-sync or says "git-sync", "sync", "commit and push", "pull and push", or "sync my branch".Engineering★ 585
- release-managerborghei/Claude-SkillsAutomates release management with changelog generation, semantic versioning, and release readiness checks. Use when preparing releases, generating changelogs, bumping versions, or validating release candidates.Other★ 1K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in