federation
The rules that let independent social sites like Mastodon pass posts, follows and likes to each other, and how this WordPress plugin does its side of it.
LABSCO SUMMARY
Summary
automattic/wordpress-activitypub's skills are all Automattic's own contributor playbook for this WordPress plugin's codebase, not guidance for anyone running or federating a WordPress site.
Three cover engineering fundamentals for this specific codebase: code-style is the plugin's PHP coding standards and WordPress-hook conventions, dev walks through its wp-env setup, linting, and build commands, and test documents its PHPUnit and Playwright end-to-end testing patterns. Two more are domain knowledge rather than process: federation explains the ActivityPub protocol and federation mechanics the plugin implements, and integrations covers how the plugin stays compatible with specific third-party WordPress plugins.
The remaining three are release-and-review mechanics. pr is meant to be invoked before opening any pull request, checking branch naming, changelog entries, and reviewer assignment against the project's own rules. gitattributes audits which dev-only files — lint configs, CI, tests, docs, build tooling — are excluded from the WordPress.org plugin zip, to be run before a release or after adding a new top-level file. release covers version bumps and changelog generation through Jetpack's own Changelogger tool.
READ THE FULL ANALYSIS
Who this is for. A contributor opening a pull request against this specific repository, and specifically one already familiar with its own tools and terms — wp-env, Jetpack Changelogger, its own export-ignore conventions. Someone running the ActivityPub plugin on their own WordPress site, or building an unrelated federation integration, gets nothing from any of them.
The README never mentions any of this. automattic/wordpress-activitypub's own README describes the plugin for end users — install from WordPress.org, try it in WordPress Playground — and how to contribute in general terms: bug reports, discussions, security disclosure. It says nothing about skills or an agent anywhere; they all sit in the repository tree.
What it costs to start. Several assume something already set up on your machine or in this project — a working wp-env, PHPUnit, Playwright, or the Changelogger tooling the release process expects. Others — code-style, federation and integrations — need nothing beyond the skill itself.
WHAT'S INSIDE
Skills
Ready to use
Nothing else to set up — install it and go.
2 of 2
SETUP
Showing all 2 skills
gitattributes
The plugin people download from WordPress.org is built straight from the code repository, so this is the check that keeps everything only developers need — tests, build settings, internal docs — out of it.