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

Whats New

by letsrevel in letsrevel/revel-backend

Draft a "What's New" community update for the Revel Discord covering changes across backend, frontend, and infra over a time window.

MITAuto-check passedDevelopment

Install Whats New

skills CLI
$ npx skills add letsrevel/revel-backend --skill whats-new -a claude-code

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

GitHub CLI
$ gh skill install letsrevel/revel-backend whats-new --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/letsrevel/revel-backend.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/whats-new .claude/skills/whats-new && 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
whats-new
GitHub stars
110
Token cost
~1.7k tokens
SKILL.md length
633 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Draft a "What's New" community update for the Revel Discord covering changes across backend, frontend, and infra over a time window.

  • Works in 5 steps: Parse the window → Gather changes (changelog-first, dig… → Compose — grouped by area → …
  • The user runs /whats-new
  • SKILL.md covers 1. Parse the window, 2. Gather changes…, 3. Compose — grouped by area and 4. The changelog footer…, plus 2 more sections
  • Calls gh and git; reaches docs.letsrevel.io and github.com

What it does

Whats New is an agent skill from letsrevel/revel-backend. Draft a "What's New" community update for the Revel Discord covering changes across backend, frontend, and infra over a time window. Use when the user runs /whats-new or asks for a community changelog/release-roundup post for organizers (and the programmers in the room).

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes. It works with Discord, Git and Django. The repository describes itself as: Open-source event management, ticketing and membership platform for communities, clubs, independent venues and independent artists. The licence is MIT.

When your agent uses it

  • The user runs /whats-new
  • Asks for a community changelog/release-roundup post for organizers (and the programmers in the room)

Example prompts

  • “/whats-new”

Requirements

  • Pre-approved tools (allowed-tools): Bash(git:*), Bash(gh:*), Bash(date:*), Bash(grep:*), Bash(ls:*), Bash(test:*), Read, Edit, Write, Glob, Grep

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Parse the window
  2. Gather changes (changelog-first, dig only gaps)
  3. Compose — grouped by area
  4. The changelog footer (REQUIRED on every edition page)
  5. Deliver

What it can do on your machine

Read from SKILL.md and the folder at commit 8333099. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(git:*)
    • Bash(gh:*)
    • Bash(date:*)
    • Bash(grep:*)
    • Bash(ls:*)
    • Bash(test:*)
    • Read
    • Edit
    • Write
    • Glob

    …and 1 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git

    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:

    • docs.letsrevel.io
    • 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

Whats New loads about 1.7k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 633 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
~1.7k

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 letsrevel/revel-backend at commit 8333099, republished under its MIT licence (© letsrevel). 633 words, ~1,664 tokens.

Download SKILL.mdSave it as .claude/skills/whats-new/SKILL.md (or your agent's skills folder).
name
whats-new
description
Draft a "What's New" community update for the Revel Discord covering changes across backend, frontend, and infra over a time window. Use when the user runs /whats-new or asks for a community changelog/release-roundup post for organizers (and the programmers in the room).
allowed-tools
Bash(git:*), Bash(gh:*), Bash(date:*), Bash(grep:*), Bash(ls:*), Bash(test:*), Read, Edit, Write, Glob, Grep

What's New

Produces a Discord-ready "What's New" post for the Revel community and archives it on the published docs site. Audience: mostly organizers, but programmers too — every item leads with the organizer-facing benefit and carries a light technical detail (a flag, an endpoint, a behavior change) for the developers reading along.

Three repos, all public, all siblings of the cwd (revel-backend):

RepoPathPrimary source
Backend. (cwd)CHANGELOG.md (rich, dated, user-facing prose)
Frontend../revel-frontendCHANGELOG.md if present, else git/PR digging
Infra../infragit/PR digging (no changelog)

The frontend is adopting the backend's changelog process. Always check for ../revel-frontend/CHANGELOG.md first and use it changelog-first when it exists; only fall back to git/PR digging for repos that have no changelog yet.

1. Parse the window

The argument is number + w|m (e.g. 1w, 2m, 6w). Default 1m if empty/unrecognized.

Compute the cutoff date (this is darwin/BSD date; for GNU use date -d "-2 months" +%F):

bash
# N and UNIT parsed from the arg; UNIT is w (weeks) or m (months)
date -v-${N}${UNIT} +%F        # e.g. date -v-1m +%F  → cutoff YYYY-MM-DD
date +%F                       # today, for the edition header

Keep the human label for the header: "Last month" (1m), "Last 2 weeks" (2w), etc.

2. Gather changes (changelog-first, dig only gaps)

Backend — primary, already curated prose:

bash
grep -nE '^## \[' CHANGELOG.md          # locate version sections + dates

Read every ## [X.Y.Z] - DATE section with DATE >= cutoff, plus [Unreleased]. These bullets are already user-facing — reuse their substance. Open a PR (gh pr view <n>) only when an entry is too terse to translate for a community audience.

Frontend — changelog-first if present, else git/PR:

bash
test -f ../revel-frontend/CHANGELOG.md && echo "use changelog" || echo "dig git/PRs"
# changelog path: same as backend, against ../revel-frontend/CHANGELOG.md
# fallback path:
git -C ../revel-frontend log --since="<cutoff>" --first-parent --merges --pretty='%h %s'
gh -R letsrevel/revel-frontend pr list --state merged --search "merged:>=<cutoff>" \
   --limit 50 --json number,title,body,mergedAt

Infra — git/PR only:

bash
git -C ../infra log --since="<cutoff>" --first-parent --merges --pretty='%h %s'
gh -R letsrevel/infra pr list --state merged --search "merged:>=<cutoff>" \
   --limit 50 --json number,title,body,mergedAt

When a PR title is opaque, read its body for the user-facing description. Drop the noise: pure CI/lint/test/dependency-bump/refactor commits unless they change observable behavior.

3. Compose — grouped by area

Group items into emoji-headed areas chosen from what's actually in the window. Suggested palette (use only the ones that apply; invent others as needed):

  • ## 🎟️ Events & Tickets
  • ## 💳 Payments, VAT & Reporting
  • ## 🔔 Notifications & Comms
  • ## 📋 Questionnaires & Polls
  • ## 🌍 Self-hosting & Infrastructure
  • ## 🛠️ Under the Hood (perf, security, developer-facing)

Per bullet: organizer benefit first, light tech detail inline. Example:

  • Mark an event as open-ended when there's no fixed finish — the page shows "Ongoing" instead of an end time (is_open_ended flag, propagates to recurring series).

Rules:

  • Discord markdown only: ##/### headers, **bold**, - bullets, `code`. No tables, no collapsibles.
  • Confident and community-friendly, concise, no marketing fluff.
  • Don't surface internal refactors, secrets, or per-PR links in the body.
Show full SKILL.md (274 more words)Show less

4. The changelog footer (REQUIRED on every edition page)

Every edition page must end with a footer linking the changelog(s) — include a repo only if it has a changelog. mkdocs has no auto-link extension, so use markdown links:

markdown
**📋 Full changelogs:** [Backend](https://github.com/letsrevel/revel-backend/blob/main/CHANGELOG.md) · [Frontend](https://github.com/letsrevel/revel-frontend/blob/main/CHANGELOG.md)

Only list Frontend once ../revel-frontend/CHANGELOG.md exists; add Infra if/when it gets one.

5. Deliver

The published docs page is the canonical artifact; the Discord message is a short teaser that links to it.

a. Write a new edition page (one file per run): docs/whats-new/<today>-last-<slug>.md, where <slug> is the window label kebab-cased — 1m→last-month, 2m→last-2-months, 1w→last-week, 2w→last-2-weeks. Example: docs/whats-new/2026-06-22-last-month.md. Structure: # What's New — <date range> H1, the area sections (##), then the §4 changelog footer.

b. Index it — prepend a bullet to docs/whats-new/index.md right after the <!-- EDITIONS BELOW ... --> marker, newest first:

markdown
- [<date> — Last <window>](<filename-without-.md>.md) — <one-line teaser of the headline items>

Also add the edition to the left-sidebar nav in mkdocs.yml, under the What's New: section right after whats-new/index.md (newest first, matching the ADR section's per-entry layout):

yaml
  - What's New:
      - whats-new/index.md
      - whats-new/<filename>.md   # <-- prepend the new edition here, above older ones

c. Print the Discord message in chat, inside a fenced block so it's copy-pasteable — a SHORT teaser, not the full post: a punchy intro line, 4–6 headline bullets (the biggest items only), and a link to the published edition page:

📖 Full update → https://docs.letsrevel.io/whats-new/<slug>/

(The <slug> is the filename without .md. The URL goes live when docs deploy — that's expected; say so.) Keep it comfortably under Discord's 2000-char limit.

d. Do not commit (project rule: always ask first). Report the new file, the index update, and print the Discord teaser, then offer to commit.

Notes

  • The docs publish to https://docs.letsrevel.io under the "What's New" nav tab; each edition lives at https://docs.letsrevel.io/whats-new/<slug>/.
  • The edition page carries the full detail; the Discord teaser only summarizes and links to it.

© letsrevel, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/whats-new of letsrevel/revel-backend.

Open the folder on GitHubat commit 8333099

Compare with similar skills

Whats New 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.

Whats New compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Whats New this skillletsrevel/revel-backend110—~1.7kAutomated safety check: PassMIT
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT
Mole Release Notes Publishertw93/Mole70k—~1.9kAutomated safety check: PassGPL-3.0
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills104k2 repos~3.5kAutomated safety check: NotesMIT

Similar skills

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Draft Release Notes

    jamiepine/voicebox

    Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.

    57k GitHub stars~941 tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Mole Release Notes Publisher

    tw93/Mole

    Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.

    70k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Release Bump

    jamiepine/voicebox

    Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.

    57k GitHub stars~1.1k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    104k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

More from letsrevel/revel-backend

  • Loki Logs

    letsrevel/revel-backend

    A skill your agent uses when investigating production behaviour from logs — a 500/error in prod, a failing or stuck Celery task, tracing one request/traceid/user across services, or confirming a…

    110 GitHub stars~918 tokensUpdated 3 days ago
    Auto-check: notes

  • Silk Debug

    letsrevel/revel-backend

    Analyze Django Silk profiling data to debug slow requests, detect N+1 queries, and optimize database performance.

    110 GitHub stars~1.2k tokensUpdated 3 days ago
    Auto-check passed

  • Update Changelog

    letsrevel/revel-backend

    Update CHANGELOG.md comprehensively based on git tags, merged PRs, and actual code diffs.

    110 GitHub stars~1.9k tokensUpdated 3 days ago
    Auto-check: notes

  • Updating Deps

    letsrevel/revel-backend

    Update Python dependencies using UV. An agent skill from letsrevel/revel-backend.

    110 GitHub stars~746 tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about Whats New

What does Whats New do?

Draft a "What's New" community update for the Revel Discord covering changes across backend, frontend, and infra over a time window. Whats New is an agent skill from letsrevel/revel-backend. Draft a "What's New" community update for the Revel Discord covering changes across backend, frontend, and infra over a time window.

When should I use Whats New?

Whats New fits situations like: the user runs /whats-new; asks for a community changelog/release-roundup post for organizers (and the programmers in the room).

How do I install Whats New in Claude Code?

Run `npx skills add letsrevel/revel-backend --skill whats-new -a claude-code`. Or copy the skill folder (.claude/skills/whats-new in letsrevel/revel-backend) into .claude/skills/whats-new in your project. Claude Code loads it when a task matches its description.

How do I install Whats New in Codex?

Run `npx skills add letsrevel/revel-backend --skill whats-new -a codex`. Or copy the skill folder (.claude/skills/whats-new in letsrevel/revel-backend) into .agents/skills/whats-new in your project. Codex loads it when a task matches its description.

Can I use Whats New 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 letsrevel/revel-backend --skill whats-new -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/whats-new, .gemini/skills/whats-new, .github/skills/whats-new and .opencode/skills/whats-new in your project.

What does Whats New need to run?

Going by SKILL.md and its folder, Whats New needs the command-line tools its instructions call (gh and git). Its frontmatter pre-approves these tools: Bash(git:*), Bash(gh:*), Bash(date:*), Bash(grep:*), Bash(ls:*), Bash(test:*), Read, Edit, Write, Glob, Grep.

Does Whats New access the network?

SKILL.md names 2 domains. In commands or code: docs.letsrevel.io and github.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Whats New 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 Whats New use?

Whats New 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 Whats New use?

About 1.7k tokens (SKILL.md is roughly 6.7k 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 Whats New?

Skills that share tags, products or a category with Whats New: React Router Release Notes Prep (remix-run/react-router, 57k stars), Draft Release Notes (jamiepine/voicebox, 57k stars), Mole Release Notes Publisher (tw93/Mole, 70k stars) and Release Bump (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Whats New?

letsrevel (a GitHub organization) maintains it in letsrevel/revel-backend, which has 110 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 7, 2026.

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