// Look up a Fediverse Enhancement Proposal (FEP) and explain how to implement it with Fedify. Use when the user asks about a specific FEP by ID (e.g., FEP-8fcf, FEP-1b12) or wants to implement a fediverse standard in their Fedify application.
| name | fep |
| description | Look up a Fediverse Enhancement Proposal (FEP) and explain how to implement it with Fedify. Use when the user asks about a specific FEP by ID (e.g., FEP-8fcf, FEP-1b12) or wants to implement a fediverse standard in their Fedify application. |
| argument-hint | <fep-id> |
Look up the Fediverse Enhancement Proposal identified by “$ARGUMENTS” and explain how to implement it with Fedify.
Normalise the identifier first: strip any leading FEP- or fep- prefix
and lowercase the result to get the bare four-character hex id (e.g. 8fcf).
Call that $ID in the steps below. If the result does not match
^[0-9a-f]{4}$, stop and ask the user to provide a valid FEP identifier.
If the fep MCP server is available, use mcp__fep__get_fep with id $ID
to retrieve the proposal. Otherwise clone the proposals repo and read the
file:
FEP_DIR="${TMPDIR:-${TEMP:-/tmp}}/fedify-fep-repo"
git clone https://codeberg.org/fediverse/fep.git "$FEP_DIR" 2>/dev/null \
|| git -C "$FEP_DIR" pull --ff-only
cat "$FEP_DIR/fep/$ID/fep-$ID.md"
Summarise: status, what problem it solves, and what extensions it defines (new JSON-LD terms, HTTP endpoints, or activity shapes).
Explain which Fedify APIs are relevant to the implementation: vocabulary
types in @fedify/vocab, custom context handling, dispatcher or inbox
listener patterns.
This skill is utilized when creating a web framework integration package. After examining the given framework, a feasibility assessment is conducted regarding the creation of an integration package. If implementation is feasible, the package is generated; if it is not possible, the rationale is provided to the user.
This skill should be used when adding new ActivityPub/JSON-LD vocabulary types to the @fedify/vocab package, defining new YAML vocabulary schema files, or updating existing vocabulary definitions in Fedify. Applies when implementing FEPs, extending ActivityStreams vocabulary, or adding third-party vocab types such as Mastodon extensions, Litepub types, or other fediverse vocabularies.
This skill is used to create an example application for a web framework integration package and to test it with `mise test:examples`.
Help the user migrate Fedify code between versions. Use when the user needs to upgrade their Fedify version, fix breaking-change errors, or update deprecated API usage.
Fetch and explain Fedify documentation on a specific topic. Use when the user asks about Fedify API details, configuration options, or how a specific feature works. Fetches up-to-date docs from fedify.dev.
Guide the user through implementing an ActivityPub actor with Fedify. Use when the user needs to add or configure an actor dispatcher, set up key pairs, configure aliases, or handle actor-related requests.