4 skills.
Use when asked to write or improve API documentation — reference docs for a REST, GraphQL, or SDK interface covering authentication, endpoints or methods, parameters, return values, and error codes — as distinct from [[readme-writing]], which orients a newcomer to a whole project rather than documenting one interface in depth.
Use when asked to write or maintain a changelog — the complete, running, human-readable record of notable changes to a project across all versions — as distinct from [[release-notes]], which is the announcement for one specific release, narrower in scope and often more promotional in tone.
Use when asked to write or improve a project's README — the first, and often only, file a visitor reads to understand what a project is, whether it's relevant, and how to start using it — as distinct from [[api-documentation]], which documents a specific interface's operations in depth rather than orienting a newcomer to the whole project.
Use when asked to write release notes — the announcement accompanying one specific release, aimed at users deciding whether and how it affects them — as distinct from a [[changelog]], which is the complete, cumulative running history across every version rather than one release's announcement.