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

Pixiv CLI Release Notes

by FlanChanXwO in FlanChanXwO/pixiv-cli

Prepare pixiv-cli bilingual versioned release notes, audit source coverage, coordinate an authorized version release, or recover its independent publishers.

MITAuto-check passedDevelopment

Install Pixiv CLI Release Notes

skills CLI
$ npx skills add FlanChanXwO/pixiv-cli --skill pixiv-cli-release-notes -a claude-code

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

GitHub CLI
$ gh skill install FlanChanXwO/pixiv-cli pixiv-cli-release-notes --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/FlanChanXwO/pixiv-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pixiv-cli-release-notes .claude/skills/pixiv-cli-release-notes && 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
pixiv-cli-release-notes
GitHub stars
134
Token cost
~954 tokens
SKILL.md length
462 words
Files
2
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Prepare pixiv-cli bilingual versioned release notes, audit source coverage, coordinate an authorized version release, or recover its independent publishers.

  • Works in 5 steps: Confirm the version, prior tag, target… → Use scripts/cmd/releasenotes audit to… → Write changelog/vX.Y.Z/en.md and… → …
  • Release preparation and historical Release synchronization
  • SKILL.md covers Prepare an approved version, Release and publishers and History and handoff
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Pixiv CLI Release Notes is an agent skill from FlanChanXwO/pixiv-cli. Prepare pixiv-cli bilingual versioned release notes, audit source coverage, coordinate an authorized version release, or recover its independent publishers. Use for release preparation and historical Release synchronization, not routine feature PR metadata.

Its SKILL.md is about 950 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 and Translation. The repository describes itself as: Pixiv, in your terminal — a CLI, MCP server, and Go SDK for discovery, accounts, creators, collections, and downloads. The licence is MIT.

When your agent uses it

  • Release preparation and historical Release synchronization
  • Not routine feature PR metadata

Example prompts

  • “/pixiv-cli-release-notes”

Requirements

  • Docker

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Confirm the version, prior tag, target commit/range, and allowed actions. Inspect current tags/releases rather than guessing the next…
  2. Use scripts/cmd/releasenotes audit to collect merged PRs, direct commits, authors, and first-time contributors for the exact range. Keep…
  3. Write changelog/vX.Y.Z/en.md and zh-CN.md directly in the release-prep change. Use the documented non-empty section order, matching source…
  4. Update the changelog navigation and release metadata that actually changes. Preserve skills/pixiv-cli/SKILL.md publisher fields and align…
  5. Run the release-note tool's validation with the same audit plus the relevant local release/test checks. After release-prep merge, re-audit…

What it can do on your machine

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

    No URLs in SKILL.md.

    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

Pixiv CLI Release Notes loads about 954 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 462 words of instructions outside code blocks.

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

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 FlanChanXwO/pixiv-cli at commit 2b3ccbb, republished under its MIT licence (© FlanChanXwO). 462 words, ~954 tokens.

Download SKILL.mdSave it as .claude/skills/pixiv-cli-release-notes/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
pixiv-cli-release-notes
description
Prepare pixiv-cli bilingual versioned release notes, audit source coverage, coordinate an authorized version release, or recover its independent publishers. Use for release preparation and historical Release synchronization, not routine feature PR metadata.

Prepare a pixiv-cli Release

Read AGENTS.md, current release.yml and the relevant publisher YAML, and the release sections of docs/en/maintainers/development.md. Executable workflows own current inputs and ordering. SemVer advice is not authorization to create a release-prep PR, merge, tag, publish, or rewrite history.

Prepare an approved version

  1. Confirm the version, prior tag, target commit/range, and allowed actions. Inspect current tags/releases rather than guessing the next version.
  2. Use scripts/cmd/releasenotes audit to collect merged PRs, direct commits, authors, and first-time contributors for the exact range. Keep its non-secret audit output in a temporary location, not committed source. Read the tool's current help for arguments.
  3. Write changelog/vX.Y.Z/en.md and zh-CN.md directly in the release-prep change. Use the documented non-empty section order, matching source sets, inline PR/commit links, contributors, and compare footer. Pixiv requires coverage of every in-range PR/direct commit; internal work belongs in Maintenance.
  4. Update the changelog navigation and release metadata that actually changes. Preserve skills/pixiv-cli/SKILL.md publisher fields and align its version with the release contract. Do not publish maintenance skills as the product skill, or change old release notes as unrelated cleanup.
  5. Run the release-note tool's validation with the same audit plus the relevant local release/test checks. After release-prep merge, re-audit and validate the exact final commit before creating the authorized tag. Missing attribution or an API failure blocks that step.

Ordinary PRs have changes, verification, and a checklist; no release classification fields or automatically generated changelog fragment are required. changelog/unreleased/ is not a mandatory feature-PR editing target.

Show full SKILL.md (213 more words)Show less

Release and publishers

release.yml is tag-push only. Validate, tests, native production archives, and verified containers are tied to the immutable source. Prepared artifacts precede release-approval; publisher credentials are scoped separately. Do not dispatch a nonexistent manual release input or replace source under an existing tag.

GitHub Release, GHCR, Homebrew, Docker Hub, SkillHub, and ClawHub are not one atomic transaction. Read the current graph: independent publishers consume the completed Release handoff and original artifact identity. Manual publisher recovery uses release_run_id. Inspect their results independently; one successful channel does not prove another succeeded. Use ClawHub verify_only only for its documented non-republishing check.

Verify public Release notes/assets, signatures/checksums and channel outcomes that the authorized release requires. Real SDK, native-library, browser-host, and installer evidence must be obtained through their actual workflows; mocks and local workflow tests cannot replace them. Do not add extra approval stages or bypass the existing single final approval.

History and handoff

Run history synchronization as a dry-run for explicitly identified versions first. sync-history --apply requires explicit approval; it does not authorize new tags or replacement assets. Confirm the resulting remote body against local bilingual rendering.

Report the exact version, tag/commit, Release run, per-channel state, and outstanding evidence. Never print signing keys, deploy keys, account credentials, or private logs. Leave incomplete publication clearly incomplete.

© FlanChanXwO, 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 .agents/skills/pixiv-cli-release-notes of FlanChanXwO/pixiv-cli.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 2b3ccbb

Compare with similar skills

Pixiv CLI Release Notes 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.

Pixiv CLI Release Notes compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pixiv CLI Release Notes this skillFlanChanXwO/pixiv-cli134—~954Automated safety check: PassMIT
DeepChat Release ProcessThinkInAIXYZ/deepchat6.4k—~1.1kAutomated safety check: PassApache-2.0
D2mcpp Authoringmcpp-community/d2mcpp1.8k—~2.7kAutomated safety check: PassCustom licence
Pre ReleaseZhuoZhuoCrayon/throttled-py651—~1.1kAutomated safety check: PassMIT
Pulse Releasequnqin24/Pulse516—~1.3kAutomated safety check: PassApache-2.0
Release WorkflowCaldis/react-zmage946—~3.6kAutomated safety check: NotesMIT

Similar skills

  • DeepChat Release Process

    ThinkInAIXYZ/deepchat

    Runs the DeepChat repository's release flow: prepares bilingual release notes and a version bump on dev, cuts or updates a release branch, then fast-forwards main and tags the version.

    6.4k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

  • D2mcpp Authoring

    mcpp-community/d2mcpp

    Authoring conventions, design principles, and file formats for the d2mcpp (D2X) Modern C++ tutorial project.

    1.8k GitHub stars~2.7k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

  • Pre Release

    ZhuoZhuoCrayon/throttled-py

    Automates release preparation for throttled-py. An agent skill from ZhuoZhuoCrayon/throttled-py.

    651 GitHub stars~1.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Pulse Release

    qunqin24/Pulse

    Release a new Pulse version end to end — checks, bilingual CHANGELOG entry, VERSION, tag, the release workflow, syncing main, and the issue replies that go with it.

    516 GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Release Workflow

    Caldis/react-zmage

    A skill your agent uses when the user wants to ship a new version of react-zmage to npm.

    946 GitHub stars~3.6k tokensUpdated 4 mo ago
    DevelopmentAuto-check: notes

  • Release New Version

    niki914/zafiro

    A skill your agent uses when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and…

    227 GitHub stars~2k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from FlanChanXwO/pixiv-cli

All 11 skills in this repo

  • Pixiv CLI

    FlanChanXwO/pixiv-cli

    Operate the installed pixiv CLI to search works and users, reverse-search images with SauceNAO or ascii2d, inspect Pixiv references, read feeds and rankings, and perform explicitly authorized…

    134 GitHub stars~2.8k tokensUpdated 2 days ago
    Auto-check passed

  • Pixiv CLI CI

    FlanChanXwO/pixiv-cli

    Diagnose pixiv-cli GitHub Actions failures and verify current-head quality, platform, PR-verification, native/browser, and release evidence.

    134 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed

  • Pixiv CLI Code Commenting

    FlanChanXwO/pixiv-cli

    In pixiv-cli, write and review intent-focused code comments, API documentation, docstrings, and numbered workflow stages.

    134 GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed

  • Pixiv CLI Native

    FlanChanXwO/pixiv-cli

    Change or validate pixiv-cli Rust ugoira, cgo/FFI, committed static libraries, vendored dependencies, Linux ABI, and native runner evidence.

    134 GitHub stars~948 tokensUpdated 2 days ago
    Auto-check passed

  • Pixiv CLI PR

    FlanChanXwO/pixiv-cli

    Prepare, update, or verify a pixiv-cli pull request using its current template, trusted verification policy, reviewed diff, and head-specific check results.

    134 GitHub stars~802 tokensUpdated 2 days ago
    Auto-check passed

  • Pixiv CLI Docs

    FlanChanXwO/pixiv-cli

    Edit pixiv-cli documentation, AGENTS.md, client bridges, repository maintenance skills, or the distributed product skill.

    134 GitHub stars~997 tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Pixiv CLI Release Notes

What does Pixiv CLI Release Notes do?

Prepare pixiv-cli bilingual versioned release notes, audit source coverage, coordinate an authorized version release, or recover its independent publishers. Pixiv CLI Release Notes is an agent skill from FlanChanXwO/pixiv-cli. Prepare pixiv-cli bilingual versioned release notes, audit source coverage, coordinate an authorized version release, or recover its independent publishers.

When should I use Pixiv CLI Release Notes?

Pixiv CLI Release Notes fits situations like: release preparation and historical Release synchronization; not routine feature PR metadata.

How do I install Pixiv CLI Release Notes in Claude Code?

Run `npx skills add FlanChanXwO/pixiv-cli --skill pixiv-cli-release-notes -a claude-code`. Or copy the skill folder (.agents/skills/pixiv-cli-release-notes in FlanChanXwO/pixiv-cli) into .claude/skills/pixiv-cli-release-notes in your project. Claude Code loads it when a task matches its description.

How do I install Pixiv CLI Release Notes in Codex?

Run `npx skills add FlanChanXwO/pixiv-cli --skill pixiv-cli-release-notes -a codex`. Or copy the skill folder (.agents/skills/pixiv-cli-release-notes in FlanChanXwO/pixiv-cli) into .agents/skills/pixiv-cli-release-notes in your project. Codex loads it when a task matches its description.

Can I use Pixiv CLI Release Notes 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 FlanChanXwO/pixiv-cli --skill pixiv-cli-release-notes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pixiv-cli-release-notes, .gemini/skills/pixiv-cli-release-notes, .github/skills/pixiv-cli-release-notes and .opencode/skills/pixiv-cli-release-notes in your project.

What does Pixiv CLI Release Notes need to run?

SKILL.md names no scripts, command-line tools or credentials: Pixiv CLI Release Notes is instructions for the agent only. Our summary lists: Docker.

Does Pixiv CLI Release Notes access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Pixiv CLI Release Notes 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 Pixiv CLI Release Notes use?

Pixiv CLI Release Notes 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 Pixiv CLI Release Notes use?

About 954 tokens (SKILL.md is roughly 3.8k 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 Pixiv CLI Release Notes?

Skills that share tags, products or a category with Pixiv CLI Release Notes: DeepChat Release Process (ThinkInAIXYZ/deepchat, 6.4k stars), D2mcpp Authoring (mcpp-community/d2mcpp, 1.8k stars), Pre Release (ZhuoZhuoCrayon/throttled-py, 651 stars) and Pulse Release (qunqin24/Pulse, 516 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pixiv CLI Release Notes?

FlanChanXwO (a GitHub user) maintains it in FlanChanXwO/pixiv-cli, which has 134 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 6, 2026.

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