New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Yaak Changelog

by mountain-loop in mountain-loop/yaak

Create or edit Yaak changelogs. An agent skill from mountain-loop/yaak.

MITAuto-check passedDevelopment

Install Yaak Changelog

skills CLI
$ npx skills add mountain-loop/yaak --skill yaak-changelog -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mountain-loop/yaak yaak-changelog --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mountain-loop/yaak.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/yaak-changelog .claude/skills/yaak-changelog && rm -rf skills-src

Use ~/.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/

Facts

Skill name
yaak-changelog
GitHub stars
19k
Token cost
~1.6k tokens
SKILL.md length
756 words
Files
2
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

Create or edit Yaak changelogs. An agent skill from mountain-loop/yaak.

  • Codex needs to update a beta GitHub release body
  • SKILL.md covers Workflow, File Rules and Checks
  • Calls gh and go; reaches github.com and yaak.app
  • Generate a stable website changelog from beta releases

What it does

Yaak Changelog is an agent skill from mountain-loop/yaak. Create or edit Yaak changelogs. Beta and draft prerelease changelogs live only in the GitHub release body; stable release changelogs live in src/content/changelog/YYYYMMDDVERSION/. Use when Codex needs to update a beta GitHub release body, generate a stable website changelog from beta releases, update release.yaml or intro.md, expand major entries into markdown files, or preserve Yaak's changelog writing style.

Its SKILL.md is about 1.6k 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 Development, covering Changelog and release notes. It works with GitHub, gRPC, Postman and Tauri. The repository describes itself as: The most intuitive desktop API client. Organize and execute REST, GraphQL, WebSockets, Server Sent Events, and gRPC 🦬. The licence is MIT.

When your agent uses it

  • Codex needs to update a beta GitHub release body
  • Generate a stable website changelog from beta releases
  • Update release.yaml
  • Expand major entries into markdown files

Example prompts

  • “/yaak-changelog”

What it can do on your machine

Read from SKILL.md and the folder at commit 919e58f. 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

    Shell commands in SKILL.md call:

    • gh
    • go

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com
    • yaak.app
    • feedback.yaak.app

    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

Yaak Changelog loads about 1.6k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 756 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~110
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

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 mountain-loop/yaak at commit 919e58f, republished under its MIT licence (© mountain-loop). 756 words, ~1,611 tokens.

Download SKILL.mdSave it as .claude/skills/yaak-changelog/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
yaak-changelog
description
Create or edit Yaak changelogs. Beta and draft prerelease changelogs live only in the GitHub release body; stable release changelogs live in `src/content/changelog/YYYYMMDD_VERSION/`. Use when Codex needs to update a beta GitHub release body, generate a stable website changelog from beta releases, update `_release.yaml` or `_intro.md`, expand major entries into markdown files, or preserve Yaak's changelog writing style.

Yaak Changelog

Use this skill to create Yaak changelogs in the correct place:

  • Beta or draft prerelease changelogs live only on the GitHub release.
  • Stable release changelogs live in website files under src/content/changelog/YYYYMMDD_VERSION/.

Workflow

  1. Identify the target release.
  • If the target tag contains -beta or the GitHub release is a draft prerelease, update the GitHub release body only. Do not create or edit src/content/changelog/ files for beta releases.
  • For a new stable changelog, gather all beta release notes for that version since the previous stable release, then create or edit website changelog files.
  • Prefer gh api or GitHub release pages. If network access is restricted, request permission before querying GitHub.
  • Extract PR numbers and yaak.app/feedback URLs while fetching. If most bullets do not include PR references, fetch again with a more specific prompt.
  • Fetch PR authors when generating or revising release notes. Include contributor attribution for non-@gschier PR authors.
  1. Parse release bullets.
  • Treat each release-note bullet as one changelog entry.
  • Skip dependency-only, generated, build-only, test-only, CI-only, and internal maintenance bullets unless they have a clear user-facing impact that can be described in user terms.
  • For stable website changelogs, skip bullets prefixed with [beta-only].
  • Preserve the entry wording closely. Remove wrapping quotes from titles.
  • Map categories to feature, fix, improvement, or breaking.
  • Convert #NNN into https://github.com/mountain-loop/yaak/pull/NNN.
  1. For beta or draft prerelease changelogs, update the GitHub release.
  • Keep the changelog in the GitHub release body. Do not create a website changelog directory.
  • Do not add a changelog badge or link to yaak.app/changelog/VERSION for beta releases.
  • Prefer concise bullets with PR links and feedback links when available.
  • When a bullet has a feedback URL, wrap the changelog item text itself in the feedback link, then put the PR link after it. Example: - [Fixed request history timestamps](https://yaak.app/feedback/posts/request-history-time-stamp) in [#492](https://github.com/mountain-loop/yaak/pull/492).
  • Append by [@handle](https://github.com/handle) to PR-backed bullets authored by external contributors. Do not append by @gschier for @gschier PRs.
  • Include a **Full Changelog** comparison link using the previous beta tag when it exists, or the previous stable tag for beta.1.
  • Use gh release edit TAG --repo mountain-loop/yaak --notes-file ... or the GitHub release API to update the draft/prerelease body.
  • Stop after verifying the GitHub release body. The website checks below do not apply.
  1. For stable website changelogs, create or edit the release directory.
  • Path format: src/content/changelog/YYYYMMDD_VERSION/.
  • For a new release, use today's date for YYYYMMDD.
  • For an existing release, keep the original directory date.
  • Do not create changelog directories for beta releases.
  1. Write _release.yaml.
  • Include draft, optional title, summary, image, youtube, and entries.
  • Keep minor items as quick entries without content.
  • Use content only when an entry needs its own markdown section.
yaml
title: "What's New in 2026.1.0"
summary: "Brief overview of the most important additions and fixes"
draft: true
entries:
  - title: "Request debugging"
    category: feature
    pr: "https://github.com/mountain-loop/yaak/pull/123"
    feedback: "https://feedback.yaak.app/p/request-debugging"
    content: "request-debugging.md"
  - title: "Fix broken cookie clearing"
    category: fix
    pr: "https://github.com/mountain-loop/yaak/pull/124"
  1. Expand major entries.
  • Expand 3 to 6 major items when enough context exists.
  • Create slugified markdown files and reference them with content.
  • Read the related PR before writing expanded content.
  • Add emoji prefixes only for expanded entry titles if it helps distinguish major sections.
Show full SKILL.md (271 more words)Show less
  1. Handle images.
  • Reuse screenshots from PRs when they exist.
  • Convert GitHub private attachment URLs to https://github.com/user-attachments/assets/UUID before upload.
  • Upload with go run cmd/yaakadmin/main.go upload "URL" when the environment permits it.
  • If no real image is available, use a placeholder with real alt text and a caption.
  1. Write _intro.md.
  • Add a short overview paragraph at the top of the release.
  • Focus on the major themes across the release instead of repeating every bullet.
  1. Follow Yaak writing style.
  • Be direct and factual. Avoid hype.
  • State what changed and how to use it.
  • Keep paragraphs short.
  • Use backticks for code symbols, settings, and literal values.
  • Use bold sparingly for the most important phrase in a section.

File Rules

  • Beta releases must not create or edit files in src/content/changelog/.
  • Main files are _release.yaml and optional _intro.md.
  • Expanded entry files are regular markdown files such as request-debugging.md.
  • entries[].content must match an existing markdown filename in the same directory.
  • Images for changelog pages live under static/changelog/VERSION/ when committed to the repo.

Checks

  • For beta releases, verify gh release view TAG --repo mountain-loop/yaak --json body,tagName,isDraft,isPrerelease and ensure no website changelog files were created.
  • For beta releases, verify feedback-backed bullets use the feedback URL as the link target for the whole item text, not as a separate trailing Feedback: link.
  • For stable releases, ensure each user-facing source bullet becomes exactly one changelog entry unless it is [beta-only] or dependency-only/internal maintenance.
  • Ensure most entries include pr when the source release notes provide one.
  • For stable releases, ensure every referenced content file exists.
  • If the user wants stable website verification, run the site and inspect /changelog/VERSION and /rss.xml.

© mountain-loop, MIT. 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 .codex/skills/yaak-changelog of mountain-loop/yaak.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 919e58f

Compare with similar skills

Yaak Changelog 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.

Yaak Changelog compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Yaak Changelog this skillmountain-loop/yaak19k—~1.6kAutomated safety check: PassMIT
Release WorkflowGoldziher/spikard123—~909Automated safety check: PassMIT
Plugin Release CheckVoidenHQ/voiden2k—~857Automated safety check: PassApache-2.0
Release ChangelogVoidenHQ/voiden2k—~2.3kAutomated safety check: PassApache-2.0
Store Submitzhitongblog/solomd1.2k—~1.7kAutomated safety check: NotesMIT
Release VersionGOODBOY008/r-shell153—~4kAutomated safety check: PassMIT

Similar skills

  • Release Workflow

    Goldziher/spikard

    Release/publish the spikard Rust core crate and CLI end-to-end.

    123 GitHub stars~909 tokensUpdated 6 days ago
    Backend & APIsAuto-check passed

  • Plugin Release Check

    VoidenHQ/voiden

    A skill your agent uses whenever a plugin under plugins/<name is updated/pushed, or whenever asked to write a changelog/release for the app or a plugin.

    2k GitHub stars~857 tokensUpdated today
    Backend & APIsAuto-check passed

  • Release Changelog

    VoidenHQ/voiden

    A skill your agent uses whenever asked to write/create a new changelog entry for a new Voiden app version (e.g.

    2k GitHub stars~2.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Store Submit

    zhitongblog/solomd

    Publish a SoloMD release to the stores that have no usable submission API — Google Play Console and Microsoft Partner Center — by driving them through the local Unzoo Browser REST API.

    1.2k GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check: notes

  • Release Version

    GOODBOY008/r-shell

    Release a new r-shell version and create a published GitHub release with contributor credits.

    153 GitHub stars~4k tokensUpdated today
    DevelopmentAuto-check passed

  • Workclaw Release Publish

    haojing8312/WorkClaw

    A skill your agent uses when publishing a confirmed WorkClaw desktop release after the version number and bilingual Chinese plus English release notes have already been reviewed and approved by a…

    141 GitHub stars~786 tokensUpdated 4 mo ago
    DevelopmentAuto-check passed

More from mountain-loop/yaak

  • Use Yaak

    mountain-loop/yaak

    A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…

    19k GitHub stars~1.9k tokensUpdated 2 days ago
    Auto-check passed

  • Release Generate Release Notes

    mountain-loop/yaak

    Generate Yaak release notes from git history and PR metadata, including feedback links and full changelog compare links.

    19k GitHub stars~548 tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Yaak Changelog

What does Yaak Changelog do?

Create or edit Yaak changelogs. An agent skill from mountain-loop/yaak. Yaak Changelog is an agent skill from mountain-loop/yaak. Create or edit Yaak changelogs.

When should I use Yaak Changelog?

Yaak Changelog fits situations like: Codex needs to update a beta GitHub release body; generate a stable website changelog from beta releases; update release.yaml; expand major entries into markdown files.

How do I install Yaak Changelog in Claude Code?

Run `npx skills add mountain-loop/yaak --skill yaak-changelog -a claude-code`. Or copy the skill folder (.codex/skills/yaak-changelog in mountain-loop/yaak) into .claude/skills/yaak-changelog in your project. Claude Code loads it when a task matches its description.

How do I install Yaak Changelog in Codex?

Run `npx skills add mountain-loop/yaak --skill yaak-changelog -a codex`. Or copy the skill folder (.codex/skills/yaak-changelog in mountain-loop/yaak) into .agents/skills/yaak-changelog in your project. Codex loads it when a task matches its description.

Can I use Yaak Changelog 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 mountain-loop/yaak --skill yaak-changelog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/yaak-changelog, .gemini/skills/yaak-changelog, .github/skills/yaak-changelog and .opencode/skills/yaak-changelog in your project.

What does Yaak Changelog need to run?

Going by SKILL.md and its folder, Yaak Changelog needs the command-line tools its instructions call (gh and go).

Does Yaak Changelog access the network?

SKILL.md names 3 domains. In commands or code: github.com, yaak.app and feedback.yaak.app; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Yaak Changelog 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 Yaak Changelog use?

Yaak Changelog is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Yaak Changelog use?

About 1.6k tokens (SKILL.md is roughly 6.4k 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 Yaak Changelog?

Skills that share tags, products or a category with Yaak Changelog: Release Workflow (Goldziher/spikard, 123 stars), Plugin Release Check (VoidenHQ/voiden, 2k stars), Release Changelog (VoidenHQ/voiden, 2k stars) and Store Submit (zhitongblog/solomd, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Yaak Changelog?

mountain-loop (a GitHub organization) maintains it in mountain-loop/yaak, which has 19,303 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.

Source: mountain-loop/yaak on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.