- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add amplifthq/openmeld --skill openmeld-changelog -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add amplifthq/openmeld --skill openmeld-changelog -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add amplifthq/openmeld --skill openmeld-changelog -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add amplifthq/openmeld --skill openmeld-changelog -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/amplifthq/openmeld/tree/HEAD/.agents/skills/openmeld-changelogFrom the publisher
Keep changelog/entries/*.md as the human- and agent-authored source of truth.
Treat CHANGELOG.md, changelog/index.json, and changelog/releases/*.md as
generated projections. Read developing/engineering/changelog.md before
editing either source or projections.
publishedAt, optional release, and concrete
evidence only after the delivery claim is proven.Use the coding agent's native file, Git, GitHub, test, and search tools. No custom Changelog command is required for investigation or writing.
Establish these facts separately:
Merge, tag, deployment, and smoke are different claims. Keep an entry draft when the evidence proves only an earlier claim.
Record changes that affect users, operators, integrators, or contributors:
Skip internal refactors, test-only changes, routine dependency maintenance, and documentation cleanup when they do not change an external workflow. Combine several implementation commits into one user-meaningful entry when they deliver one outcome.
Use a unique lowercase slug for both the filename and id. Write native-level
English for OpenMeld's North American audience. Lead with what is now possible
or what changed, not implementation details.
---
id: slack-channel-invitations
title: Invite teammates from Slack
kind: new
areas: ["channels", "center-agent"]
audiences: ["admins"]
---
Organization admins can invite a teammate while working with the Center Agent
in Slack, without switching to a separate setup flow.
That entry is a draft. Publish it only after delivery is proven:
publishedAt: 2026-08-17
release: v0.3.60
evidence: ["pr:72", "commit:1d5254d", "workflow:123456789"]
release is optional for continuously delivered changes. Every published entry
requires durable evidence. Keep uncertain historical work as a draft rather
than inventing a date, scope, or release.
Run:
pnpm changelog:build
pnpm changelog:check
Review the resulting diff. A complete change has valid source entries, up-to-date deterministic projections, and no unsupported publication claim.
For a historical backfill, also confirm that adding the older entry placed it
by publishedAt rather than by the date of the backfill commit.
Maintain the official OpenMeld Changelog from repository evidence. Use when deciding whether a change needs a Changelog entry, writing or publishing an entry, preparing release notes, validating gener
---name: openmeld-changelogdescription: Maintain the official OpenMeld Changelog from repository evidence. Use when deciding whether a change needs a…---# .agents/skills/openmeld-changelog/SKILL.mdOverview
Maintain the official OpenMeld Changelog from repository evidence. Use when deciding whether a change needs a Changelog entry, writing or publishing an entry, preparing release notes, validating generated Changelog files, or historically backfilling missing changes.
FAQ
Download .agents/skills/openmeld-changelog/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/amplifthq/openmeld.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.