Stats
Actions
Tags
From fedify
Looks up Fediverse Enhancement Proposals (FEPs) by ID and explains implementation with Fedify. Useful for specific FEP queries (e.g., FEP-8fcf) or fediverse standards in Fedify apps.
How this skill is triggered — by the user, by Claude, or both
Slash command
/fedify:fep <fep-id><fep-id>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Look up the Fediverse Enhancement Proposal identified by “$ARGUMENTS” and
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.
npx claudepluginhub fedify-dev/fedify --plugin fedifyBuilds ActivityPub servers and handles fediverse federation in JavaScript/TypeScript using Fedify. Covers builder pattern, dispatchers, HTTP Signatures, vocab objects, key management, and integrations with Hono, Express, Next.js, and more.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.