add-to-fedify-init
This skill is used to add an integration package to the @fedify/init package so that users can select the new framework via the `fedify init` command, and to test it with `mise test:init`.
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
This skill is used to add an integration package to the @fedify/init package so that users can select the new framework via the `fedify init` command, and to test it with `mise test:init`.
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.
Guides an LLM to review a codebase's direct dependencies and suggest lightweight, low-risk custom replacements using cdxgen SBOM evidence.
This skill is used to create an example application for a web framework integration package and to test it with `mise test:examples`.
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.
Use when migrating a Bot Framework .NET SDK bot to Microsoft 365 Agents SDK. Triggered by projects that depend on packages: Microsoft.Bot.Builder or Microsoft.Bot.Builder.Integration.AspNet.Core that want to migrate to Agents SDK.
Deep WebSocket connection knowledge: FoxgloveWebSocketPlayer state machine, WorkerSocketAdapter postMessage protocol, the Foxglove WebSocket protocol handshake, RAF-based state emission, and reconnection.