detect-webfinger

Detect WebFinger endpoint implementations and assess RFC 7033 compliance.

9|Updated Mar 12, 2026

Search Tags:#protocol detection #activitypub #api endpoint #webfinger #federated identity #rfc 7033

Ready to run

npx skills add https://github.com/reiver/vibefed --skill detect-webfinger

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: detect-webfinger
Source: https://github.com/reiver/vibefed/tree/main/skills/detect-webfinger
Command: npx skills add https://github.com/reiver/vibefed --skill detect-webfinger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers quickly determine if a codebase correctly implements the WebFinger protocol, a crucial component for federated identity and ActivityPub compatibility.

Core Features & Use Cases

Protocol Detection: Identifies the presence and implementation style of the /.well-known/webfinger endpoint.
Dependency Analysis: Differentiates between direct implementation, library delegation, and mere references.
Use Case: When auditing a social media project for ActivityPub support, use this Skill to confirm if it properly exposes user information via WebFinger.

Quick Start

Use the detect-webfinger skill to check if the current project implements the WebFinger protocol.

Frequently Asked Questions about detect-webfinger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check if my codebase implements the WebFinger protocol correctly?▼

To check WebFinger protocol implementation, scan the codebase for direct route handlers, library integrations, and framework patterns exposing the `/.well-known/webfinger` endpoint to confirm RFC 7033 compliance and proper JRD response formatting.

What is WebFinger protocol detection used for in federated identity systems?▼

WebFinger protocol detection is used to verify federated identity systems by analyzing whether a codebase correctly handles `acct:` URI lookups and returns JRD responses, which is crucial for ActivityPub compatibility and user information discovery.

How do I verify RFC 7033 compliance for my ActivityPub endpoint?▼

Verify RFC 7033 compliance by scanning for common framework patterns and direct route handlers that process WebFinger requests, ensuring the endpoint correctly formats JRD responses and handles `acct:` URI lookups required by ActivityPub.

Does this protocol detection differentiate between custom code and library-based WebFinger implementations?▼

Yes, WebFinger protocol detection differentiates between direct implementation, library delegation, and mere references within the codebase, allowing you to identify exactly how the `/.well-known/webfinger` endpoint is integrated.

Can I audit my project for ActivityPub support by checking WebFinger endpoints?▼

You can audit ActivityPub support by using WebFinger protocol detection to confirm if your project properly exposes user information via the `/.well-known/webfinger` endpoint and correctly implements `acct:` URI lookup handling.

Why does WebFinger protocol detection focus on JRD response format and acct: URI handling?▼

WebFinger protocol detection focuses on JRD response format and `acct:` URI handling because these are the core RFC 7033 requirements for resolving federated identity queries and ensuring accurate resource representation in ActivityPub systems.