// Help the user set up Fedify inbox listeners for handling incoming ActivityPub activities. Use when the user needs to handle Follow, Like, Announce, Create, Undo, or other activity types delivered to their inbox.
| name | inbox |
| description | Help the user set up Fedify inbox listeners for handling incoming ActivityPub activities. Use when the user needs to handle Follow, Like, Announce, Create, Undo, or other activity types delivered to their inbox. |
Help the user configure Fedify inbox listeners.
Walk through:
setInboxListeners(inboxPath, sharedInboxPath?) on the
Federation / FederationBuilder..on(ActivityType, handler) for each activity type to handle
(Follow, Create, Undo, Like, Announce, etc.)..onError(handler) for error logging..onUnverifiedActivity(handler) if the user needs
to inspect activities that failed signature verification..withIdempotency(strategy) to avoid duplicate processing.Activity
class if needed.Reference: https://fedify.dev/manual/inbox
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`.
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.
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.
