detect-nodeinfo
Detects whether a codebase implements the NodeInfo protocol endpoint. NodeInfo is a standard used by Fediverse and federated social network servers to expose metadata about the instance (software name, version, protocols supported, user counts, etc.). Use this skill whenever the user asks whether a repo or codebase supports NodeInfo, has a /.well-known/nodeinfo endpoint, exposes instance metadata, or implements Fediverse server discovery. Also trigger when auditing a codebase for ActivityPub, Diaspora, or federated social networking support, since NodeInfo is a common companion to those protoc
npx skills add majiayu000/claude-skill-registry --skill detect-nodeinfo --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 NodeInfo Endpoint NodeInfo is a protocol used by federated social network servers to expose instance metadata in a standardized format. It is widely used in the Fediverse (Mastodon, Misskey, Pleroma, Diaspora, etc.). ## How NodeInfo Works (Two-Part Architecture) NodeInfo is **always two endpoints**, not one. This is important for classification: **Part 1 — Discovery endpoint** (required): - URL: `GET /.well-known/nodeinfo` - Returns a JSON object with a `links` array, each entry pointing to a versioned schema document - Example response: ```json { "links": [ { "rel": "http://nodeinfo.diaspora.software/ns/schema/2.1", "href": "https://example.org/nodeinfo/2.1" } ] } ``` **Part 2 — Schema endpoint** (required): - URL: typically `/nodeinfo/2.1` or `/nodeinfo/2.0` (path is not standardized, but this convention is near-universal) - Returns the full instance metadata document - Key fields: `version`, `software`, `protocols`, `usage`, `openRegistrations`, `metadata` **Variant — NodeInfo2** (optional, separate spec): - URL: `GET /.well-known/x-nodeinfo2` - A different, simpler schema by a different author (jaywink/nodeinfo2) - Less common; treat as a separate positive signal if fo
- How NodeInfo Works (Two-Part Architecture)
- Step 1 — Fast Signal Search
- Step 2 — Fallback Search (if Step 1 found nothing)
- Step 3 — Classify Each Match
- Category A — Discovery endpoint (confirmed)
- Category B — Schema endpoint (confirmed)
- Category C — Both endpoints present
- Category D — Library/Framework delegation
- Category E — Reference only (not an implementation)
- Category F — NodeInfo2 variant
- Step 4 — Check for Framework-Specific Patterns
- Step 5 — Check Schema Version Support
- Step 6 — Report Results
- What a Complete NodeInfo Implementation Looks Like
What does the detect-nodeinfo skill do?
Detects whether a codebase implements the NodeInfo protocol endpoint. NodeInfo is a standard used by Fediverse and federated social network servers to expose metadata about the instance (software name, version, protocols supported, user counts, etc.). Use this skill whenever the user asks whether a repo or codebase supports NodeInfo, has a /.well-known/nodeinfo endpoint, exposes instance metadata, or implements Fediverse server discovery. Also trigger when auditing a codebase for ActivityPub, Diaspora, or federated social networking support, since NodeInfo is a common companion to those protoc
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill detect-nodeinfo --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.