detect-webfinger
Detects whether a codebase implements the WebFinger protocol endpoint (RFC 7033). Use this skill whenever the user asks whether a repo, project, or codebase supports WebFinger, has a /.well-known/webfinger endpoint, implements the JRD response format, or handles acct: URI lookups. Also trigger when the user is auditing a codebase for ActivityPub or federated identity support, since WebFinger is a common dependency.
npx skills add majiayu000/claude-skill-registry --skill detect-webfinger --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Detect WebFinger Endpoint WebFinger (RFC 7033) is a protocol that allows discovery of information about people or resources using a standard URL pattern: `/.well-known/webfinger`. It is commonly used by ActivityPub implementations (Mastodon, etc.) and federated identity systems. ## Step 1 — Fast Signal Search Search the codebase for the string `webfinger` (case-insensitive) across all source files. This single search catches the vast majority of implementations. ``` Search query: webfinger Case: insensitive Scope: all source files (exclude: node_modules, vendor, .git, dist, build) ``` If **no matches** are found, proceed to Step 2 (fallback search). If **matches are found**, proceed to Step 3 (classify results). ## Step 2 — Fallback Search (if Step 1 found nothing) Some implementations register WebFinger indirectly under a generic well-known handler. Search for: - `/.well-known/` (route registration) - `well_known` (snake_case variant common in Python/Ruby) - `jrd+json` (the WebFinger response MIME type — very specific signal) - `acct:` (the URI scheme WebFinger uses for user lookups) If any of these match, include the files in Step 3 classification. If still nothing — report: **
- Step 1 — Fast Signal Search
- Step 2 — Fallback Search (if Step 1 found nothing)
- Step 3 — Classify Each Match
- Category A — Implementation (confirmed)
- Category B — Library/Framework delegation
- Category C — Reference only (not an implementation)
- Category D — Ambiguous
- Step 4 — Check for Framework-Specific Patterns
- Step 5 — Report Results
- What a Complete WebFinger Implementation Looks Like
What does the detect-webfinger skill do?
Detects whether a codebase implements the WebFinger protocol endpoint (RFC 7033). Use this skill whenever the user asks whether a repo, project, or codebase supports WebFinger, has a /.well-known/webfinger endpoint, implements the JRD response format, or handles acct: URI lookups. Also trigger when the user is auditing a codebase for ActivityPub or federated identity support, since WebFinger is a common dependency.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill detect-webfinger --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.