Borrowing it
Nothing to install: this file belongs to uyu423/requarks-wiki-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/uyu423/requarks-wiki-mcp/develop/.claude/skills/release-ready/SKILL.mdgit clone --depth 1 https://github.com/uyu423/requarks-wiki-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/uyu423/requarks-wiki-mcp/release-ready)<a href="https://agentmods.dev/skills/uyu423/requarks-wiki-mcp/release-ready"><img src="https://agentmods.dev/badge/skills/uyu423/requarks-wiki-mcp/release-ready/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/uyu423/requarks-wiki-mcp/release-ready"><img src="https://agentmods.dev/badge/skills/uyu423/requarks-wiki-mcp/release-ready.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00056 | $0.03913 |
| Opus 5 | $0.00028 | $0.01956 |
| Sonnet 5 | $0.00011 | $0.00783 |
| Haiku 4.5 | $0.00006 | $0.00391 |
Grade B, and why
release-ready scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
1. Check `~/.claude/.mcp.json` for `requarks-wiki` server config → extract `WIKI_BASE_URL` and `WIKI_API_TOKEN` from `env` How it starts
The opening of the file, as written. The whole thing — 458 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Ready
Prepare a new version release. This skill:
- Bumps the version in all project files
- Runs lint, format, build, and test checks
- Executes live integration tests
- Verifies npm package contents
- Analyzes code changes since last tag (new tools, resources, env vars)
- Verifies README documentation is up-to-date
- Offers to auto-update multilingual READMEs if needed
- Creates git commit and tag
Push is intentionally omitted — that is the human's domain.
Key Feature: Smart README Verification
This skill does NOT add a changelog section. Instead, it:
- Compares actual code changes with README documentation
- Detects missing tool descriptions, env vars, or features
- Automatically updates README.ko.md first (no approval needed)
- Shows user the changes and asks for review
- After user approval, propagates updates to other languages (en, ja, zh, es, pt, vi)
Workflow
1. Analyze code changes → Detect what's missing from README
2. Auto-update README.ko.md → No asking, just do it
3. Show diff to user → "I updated README.ko.md, here's what changed"
4. User reviews → Approve/Revise/Skip/Revert
5. If approved → Update all other READMEs
6. Stage files → Proceed to commit
Step 1: Determine next version
Read the current version from package.json. Ask the user which semver component to bump using AskUserQuestion:
- patch (default): bug fixes, minor tweaks (e.g., 0.3.0 → 0.3.1)
- minor: new features, backward-compatible changes (e.g., 0.3.0 → 0.4.0)
- major: breaking changes (e.g., 0.3.0 → 1.0.0)
Current: 0.3.0 → Next: ? (patch/minor/major)
Announce the next version to the user before proceeding.
Step 2: Update version in all files
The version string appears in 4 locations. Update all of them:
| File | Location | Example |
|---|---|---|
package.json |
"version": "X.Y.Z" |
Line 3 |
src/index.ts |
version: 'X.Y.Z' in Server constructor |
Search for version: near @yowu-dev/requarks-wiki-mcp |
AGENTS.md |
**Version:** X.Y.Z |
Near the top of the file |
package-lock.json |
Two occurrences of "version": "X.Y.Z" |
Lines 3 and 9 (root + packages) |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 458 lines · 56 tokens per session scan B 63e12508069e
release-ready is a skill published in the GitHub repository uyu423/requarks-wiki-mcp (6 stars, last pushed 6mo ago), licensed MIT. It adds 56 tokens to every session and 3,913 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.