Release Asc CLI
rorkai/App-Store-Connect-CLI
Publish and verify a new release of the App-Store-Connect-CLI repository.
Create, edit, comment on, close, reopen, classify, or change project fields for issues in KeeForge/KeeForge.
Install Keeforge GitHub Issues
$ npx skills add KeeForge/KeeForge --skill keeforge-github-issues -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install KeeForge/KeeForge keeforge-github-issues --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/KeeForge/KeeForge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/keeforge-github-issues .claude/skills/keeforge-github-issues && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "keeforge-github-issues" agent skill from https://github.com/KeeForge/KeeForge/tree/main/.agents/skills/keeforge-github-issues into .claude/skills/keeforge-github-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keeforge-github-issues", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/KeeForge/KeeForge/tree/main/.agents/skills/keeforge-github-issuesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add KeeForge/KeeForge --skill keeforge-github-issues -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install KeeForge/KeeForge keeforge-github-issues --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KeeForge/KeeForge.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/keeforge-github-issues .agents/skills/keeforge-github-issues && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "keeforge-github-issues" agent skill from https://github.com/KeeForge/KeeForge/tree/main/.agents/skills/keeforge-github-issues into .agents/skills/keeforge-github-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keeforge-github-issues", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add KeeForge/KeeForge --skill keeforge-github-issues -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install KeeForge/KeeForge keeforge-github-issues --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KeeForge/KeeForge.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/keeforge-github-issues .cursor/skills/keeforge-github-issues && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "keeforge-github-issues" agent skill from https://github.com/KeeForge/KeeForge/tree/main/.agents/skills/keeforge-github-issues into .cursor/skills/keeforge-github-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keeforge-github-issues", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/KeeForge/KeeForge.git --path .agents/skills/keeforge-github-issues--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add KeeForge/KeeForge --skill keeforge-github-issues -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install KeeForge/KeeForge keeforge-github-issues --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KeeForge/KeeForge.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/keeforge-github-issues .gemini/skills/keeforge-github-issues && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "keeforge-github-issues" agent skill from https://github.com/KeeForge/KeeForge/tree/main/.agents/skills/keeforge-github-issues into .gemini/skills/keeforge-github-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keeforge-github-issues", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install KeeForge/KeeForge keeforge-github-issuesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add KeeForge/KeeForge --skill keeforge-github-issues -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/KeeForge/KeeForge.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/keeforge-github-issues .github/skills/keeforge-github-issues && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "keeforge-github-issues" agent skill from https://github.com/KeeForge/KeeForge/tree/main/.agents/skills/keeforge-github-issues into .github/skills/keeforge-github-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keeforge-github-issues", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add KeeForge/KeeForge --skill keeforge-github-issues -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install KeeForge/KeeForge keeforge-github-issues --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/KeeForge/KeeForge.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/keeforge-github-issues .opencode/skills/keeforge-github-issues && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "keeforge-github-issues" agent skill from https://github.com/KeeForge/KeeForge/tree/main/.agents/skills/keeforge-github-issues into .opencode/skills/keeforge-github-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "keeforge-github-issues", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
keeforge-github-issues- GitHub stars
- 111
- Token cost
- ~1.1k tokens
- SKILL.md length
- 553 words
- Files
- 2
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Create, edit, comment on, close, reopen, classify, or change project fields for issues in KeeForge/KeeForge.
- Works in 3 steps: Read the live README for KeeForge… → Read the issue's current title, body,… → Identify any source material that came…
- An action will mutate a KeeForge GitHub issue
- SKILL.md covers Required preflight, Privacy and public wording, Classification and Project tracking, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Keeforge GitHub Issues is an agent skill from KeeForge/KeeForge. Create, edit, comment on, close, reopen, classify, or change project fields for issues in KeeForge/KeeForge. Use whenever an action will mutate a KeeForge GitHub issue. Do not use for read-only issue searches or reviews that will not change GitHub state.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Mobile. It works with GitHub. The repository describes itself as: KeePass-compatible password manager for iPhone, iPad, and Mac. The licence is GPL-3.0.
When your agent uses it
- An action will mutate a KeeForge GitHub issue
- Read-only issue searches
- Reviews that will not change GitHub state
Example prompts
- “/keeforge-github-issues”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Read the live README for KeeForge project 1
- Read the issue's current title, body, type, comments, state, and project fields when it already
- Identify any source material that came from a private or external channel, such as email,
What it can do on your machine
Read from SKILL.md and the folder at commit 2778b90. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Keeforge GitHub Issues loads about 1.1k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 553 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from KeeForge/KeeForge at commit 2778b90, republished under its GPL-3.0 licence (© KeeForge). 553 words, ~1,062 tokens.
Download SKILL.mdSave it as
.claude/skills/keeforge-github-issues/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- keeforge-github-issues
- description
- Create, edit, comment on, close, reopen, classify, or change project fields for issues in KeeForge/KeeForge. Use whenever an action will mutate a KeeForge GitHub issue. Do not use for read-only issue searches or reviews that will not change GitHub state.
KeeForge GitHub Issues
Apply this workflow before every GitHub issue mutation, including mutations requested as part of another workflow. Keep the mutation within the user's authorized scope.
Required preflight
- Read the live README for KeeForge project 1 in the current session. Do not rely on memory or a cached summary. Follow its current workflow and field guidance. If the README cannot be accessed, stop before mutating the issue and explain what is blocked.
- Read the issue's current title, body, type, comments, state, and project fields when it already exists. For a new issue, check for likely duplicates before creating it.
- Identify any source material that came from a private or external channel, such as email, in-app feedback, support conversations, private messages, logs, or attachments. Treat it as source context, not text to publish.
Privacy and public wording
- Never put personally identifiable information from an external channel into an issue, comment, title, project field, or attachment. Omit names, email addresses, account identifiers, device identifiers, exact locations, and other details that could identify the reporter.
- Never quote an external user's message verbatim. Paraphrase the relevant behavior, impact, and reproduction details in neutral language, even when the original wording seems harmless.
- Include only the minimum diagnostic detail needed to understand or reproduce the issue. Inspect logs, screenshots, and attachments before publishing them; remove secrets and identifying data.
- Do not mention the external reporter or channel unless provenance is necessary. If it is, use a generic phrase such as "A user reported" without identifying the person.
Classification
Set the GitHub issue type from the substance of the issue, not from a requested label, template, or existing value that appears inaccurate:
- Bug: KeeForge behaves incorrectly, crashes, regresses, loses data, or violates intended behavior.
- Feature: the requested outcome adds or expands user-facing product capability.
- Task: internal engineering, maintenance, documentation, research, release, or operational work that is neither a product defect nor a user-facing capability request.
Use the repository's currently configured type values. If an issue contains materially separate concerns, keep the primary type accurate and propose separate issues rather than forcing an ambiguous classification.
Show full SKILL.md (202 more words)Show less
Project tracking
- Add every created or updated issue to KeeForge project 1 unless the user explicitly says not to track that issue there. If an existing issue is missing from the project, add it as part of the requested update.
- Follow the live project README when choosing or changing fields and status.
- Whenever moving an issue to Triaged, set Effort to Low, Medium, or High in the same workflow. Use a reasonable qualitative estimate based on implementation scope, uncertainty, and validation cost. Never leave Effort unset on a newly Triaged item.
Comments and replies
When replying to another user, write concise, friendly, natural prose. Address the question or next step directly, avoid process-heavy boilerplate, and do not use em dashes. Paraphrase any external source material under the privacy rules above.
Mutate and verify
Use an available GitHub connector or authenticated GitHub tooling. Apply only the requested issue changes plus the required type and project bookkeeping above. Afterward, read back the issue and project item to verify the public text, issue type, state, project membership, status, and Effort. Report the issue link and summarize the mutations. If a multi-step mutation only partially succeeds, stop, disclose the partial state, and do not claim completion.
© KeeForge, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/keeforge-github-issues of KeeForge/KeeForge.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 2778b90
Compare with similar skills
Keeforge GitHub Issues next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Keeforge GitHub Issues this skillKeeForge/KeeForge | 111 | — | ~1.1k | Automated safety check: Pass | GPL-3.0 | |
| Release Asc CLIrorkai/App-Store-Connect-CLI | 7.7k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Flutter Pub ReleaseMixinNetwork/flutter-plugins | 512 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Publish ReleaseAyuilos/Miffan | 182 | — | ~635 | Automated safety check: Pass | AGPL-3.0 | |
| macOS Releasefayazara/macos-app-skills | 672 | — | ~1.8k | Automated safety check: Pass | None | |
| Release AppK9i-0/ccpocket | 1.1k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Flutter Pub Release
MixinNetwork/flutter-plugins
Prepare and draft a pub.dev release for a package in the flutter-plugins monorepo.
Publish Release
Ayuilos/Miffan
Publish a GitHub release for this fork, with a bilingual changelog that separates fork-owned changes from changes introduced by upstream merges.
macOS Release
fayazara/macos-app-skills
Release a native macOS app to GitHub with DMG packaging and Sparkle appcast updates.
Release App
K9i-0/ccpocket
ccpocketアプリのバージョン更新と、指定プラットフォーム向けリリースを行う. An agent skill from K9i-0/ccpocket.
Test Reviewer
axelixlabs/axelix
Reviews test code in GitHub pull requests for isolation, public-API contract coverage, AAA structure, and correct exception assertions.
More from KeeForge/KeeForge
All 9 skills in this repoShip Release
KeeForge/KeeForge
Ship an accepted, soaked KeeForge candidate across iOS, Mac App Store, and direct Mac.
Publish App Store Version
KeeForge/KeeForge
Prepare and publish an already-built KeeForge iOS or macOS version through the App Store Connect API using an API key.
Test Audit
KeeForge/KeeForge
Assess KeeForge test quality, redundant coverage, and test-support complexity; audit a selected subsystem or apply an authoring checklist while changing tests.
Pre Release Review
KeeForge/KeeForge
Statically review KeeForge changes since a shipped release for behavior risks, documentation inconsistencies, i18n gaps, and missing test coverage.
Respin Release
KeeForge/KeeForge
Replace an unshipped KeeForge candidate after a fix on an existing release branch.
Triage Feedback
KeeForge/KeeForge
Triage product feedback by inspecting its message and attachments, checking implementation and existing issues, classifying each concern, and drafting a reporter response.
Related
Works with
Categories
Questions about Keeforge GitHub Issues
What does Keeforge GitHub Issues do?
Create, edit, comment on, close, reopen, classify, or change project fields for issues in KeeForge/KeeForge. Keeforge GitHub Issues is an agent skill from KeeForge/KeeForge. Create, edit, comment on, close, reopen, classify, or change project fields for issues in KeeForge/KeeForge.
When should I use Keeforge GitHub Issues?
Keeforge GitHub Issues fits situations like: an action will mutate a KeeForge GitHub issue; read-only issue searches; reviews that will not change GitHub state.
How do I install Keeforge GitHub Issues in Claude Code?
Run `npx skills add KeeForge/KeeForge --skill keeforge-github-issues -a claude-code`. Or copy the skill folder (.agents/skills/keeforge-github-issues in KeeForge/KeeForge) into .claude/skills/keeforge-github-issues in your project. Claude Code loads it when a task matches its description.
How do I install Keeforge GitHub Issues in Codex?
Run `npx skills add KeeForge/KeeForge --skill keeforge-github-issues -a codex`. Or copy the skill folder (.agents/skills/keeforge-github-issues in KeeForge/KeeForge) into .agents/skills/keeforge-github-issues in your project. Codex loads it when a task matches its description.
Can I use Keeforge GitHub Issues in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add KeeForge/KeeForge --skill keeforge-github-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/keeforge-github-issues, .gemini/skills/keeforge-github-issues, .github/skills/keeforge-github-issues and .opencode/skills/keeforge-github-issues in your project.
What does Keeforge GitHub Issues need to run?
SKILL.md names no scripts, command-line tools or credentials: Keeforge GitHub Issues is instructions for the agent only.
Does Keeforge GitHub Issues access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Keeforge GitHub Issues safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Keeforge GitHub Issues use?
Keeforge GitHub Issues is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Keeforge GitHub Issues use?
About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Keeforge GitHub Issues?
Skills that share tags, products or a category with Keeforge GitHub Issues: Release Asc CLI (rorkai/App-Store-Connect-CLI, 7.7k stars), Flutter Pub Release (MixinNetwork/flutter-plugins, 512 stars), Publish Release (Ayuilos/Miffan, 182 stars) and macOS Release (fayazara/macos-app-skills, 672 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Keeforge GitHub Issues?
KeeForge (a GitHub organization) maintains it in KeeForge/KeeForge, which has 111 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 6, 2026.
Source: KeeForge/KeeForge on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.