More room for your next idea. Membership from $9.99/month.Take a look

Changelog Studiov1.0.0

Turn reviewed release notes into a filterable static changelog site.

See what you can make

Skip the interactive example

Loading the working example…

Open example
Interact with the sample. Scroll inside to explore.
Made with this SkillA filterable static changelog site

Two fictional products · filterable version history

Open full example

What you get

A filterable static changelog site

What you can make

  • Turn reviewed release notes into a filterable static changelog site.
  • Browse versions with category filters and search; export HTML, JSON, CSV and a SHA-256 delivery manifest.
  • Preview locally with Python 3.10+ offline, then host the static folder on your own site.
Explore delivered files5 groups
  • index.html
  • changelog.json
  • releases.csv
  • input.json
  • delivery-manifest.json

Good fit

Product, growth and indie teams that need a lasting public changelog—not a one-off release card.

Know the limits

Uses reviewed release text only. Does not invent versions, user counts or commitments, scrape repositories, create GitHub Releases or publish automatically. Distinct from release-digest. Examples are fictional.

About this skill

Capabilities: Build a multi-version public changelog site from reviewed JSON. Filter by category and version, search titles and bodies, and keep full exports regardless of browser filters.

Deliverables: index.html, changelog.json, releases.csv, input.json and delivery-manifest.json (SHA-256). Optional product HTTPS URL and custom theme colors with contrast checks.

Read the full workflow

Requirements and run: Python 3.10+ standard library only. python3 scripts/build-changelog.py --input examples/northline.json --output ./changelog-site

Validation: Two fictional samples (Northline, Harbor Desk) generated offline. Invalid empty releases fail without writing output. Existing output directories are never overwritten.

Limits: Does not invent versions, user counts or commitments. Does not create GitHub Releases, scrape repositories or publish automatically. Distinct from release-digest (single release card).

FROM PACKAGE TO FIRST RESULT

Your first result, with your agent

Choose a starting point, add the content you already have, then let your agent check the setup and create one result.

View example result

Purchase access is required. Unzip the package into the project folder below, or let your agent follow the installation guide. .agents/skills/changelog-studio

Your project name, audience and the content or images you already have are enough to start. Your agent will ask for anything essential that is missing.

3. Let your agent guide the first result

Package location: .agents/skills/changelog-studio

Use Changelog Studio at .agents/skills/changelog-studio. Read SKILL.md and check local dependencies. Start with examples/northline.json. Make one inspectable result first, then adapt it to my content. Keep fictional examples labeled, ask for essential missing inputs and do not invent business facts.

Use a new output folder and preserve existing files. Inspect the actual deliverables (index.html, changelog.json, releases.csv), open the visual result and explain failed checks. An incomplete dependency check is not a successful result. Ask before paid services and do not publish automatically.
Before calling it done
  • Dependencies checked before rendering
  • Actual files open and work with your content
  • Editable source saved in a new folder
Made your first result? Share your experience →
Installation options & technical requirements
US$4.99 · MIT licensePython 3.10+ · offlineNo API key or paid provider
  1. 01

    Choose your agent

    These steps use a project folder. Open the project in your agent and run terminal commands from its root.

    Codex directory guide

    Package folder .agents/skills/changelog-studio

  2. 02

    Add the package

    Download and unzip the package into the folder above. Keep all its files together, with SKILL.md directly inside that folder.

    Downloads require a verified account and purchase access. Choose a new folder if this Skill is already installed.

  3. 03

    Run the included sample

    Manual sample commands and technical details

    Read SKILL.md, review the generator and check its runtime requirements before running:

    cd .agents/skills/changelog-studio
    python3 scripts/build-changelog.py --input examples/northline.json --output ./changelog-site
    Your first result

    Open changelog-site/index.html. Filter by version and category, search titles and bodies, then inspect changelog.json, releases.csv and delivery-manifest.json. Generate into a fresh folder after edits.

    Uses reviewed release text only. Does not invent versions, user counts or commitments, scrape repositories, create GitHub Releases or publish automatically. Distinct from release-digest (single release card). Python 3.10+ standard library, offline. Examples are fictional.

    If changelog-site already exists, change the output to ./changelog-site-2. Existing files are never overwritten.

    Prefer to ask your agent?

    Use Changelog Studio at .agents/skills/changelog-studio. Read SKILL.md and review scripts/build-changelog.py. Run examples/northline.json into a new output folder and show me all generated files. Keep fictional sample content clearly labeled.

Reviews0

Share your first result

Tried this workflow? Help others decide with an honest review.

Before you choose this Skill

How do I get Changelog Studio?

The listed individual package price is USD 4.99. Premium downloads require a confirmed purchase or active membership. Your agent subscription, model access and external provider credits are separate.

Which agents can use this skill?

This release lists Codex, Claude Code, Cursor as intended installation hosts. Check the package’s dependencies and permissions before running it. These labels do not certify that every workflow has been tested in every agent.

What files can this workflow generate?

The documented 1.0.0 workflow lists: index.html; changelog.json; releases.csv; input.json; delivery-manifest.json. Some files or exports are optional; follow the package’s setup and inspect the delivered result.

What should I check before using the result?

Uses reviewed release text only. Does not invent versions, user counts or commitments, scrape repositories, create GitHub Releases or publish automatically. Distinct from release-digest (single release card). Python 3.10+ standard library, offline. Examples are fictional.

$4.99One-time purchase