atproto-endpoint-stub-finder

Scan Objective-C codebases for ATProto/XRPC endpoint stub markers and map them to registered methods.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/jvalinsky/garazyk --skill atproto-endpoint-stub-finder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: atproto-endpoint-stub-finder
Source: https://github.com/jvalinsky/garazyk/tree/main/skills/atproto-endpoint-stub-finder
Command: npx skills add https://github.com/jvalinsky/garazyk --skill atproto-endpoint-stub-finder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps identify and track incomplete or unimplemented ATProto/XRPC endpoints within a codebase, ensuring better API coverage and facilitating the generation of follow-up tasks.

Core Features & Use Cases

  • Stub Detection: Locates markers like not_implemented, TODO, and FIXME within handler code.
  • Endpoint Mapping: Correlates registered XRPC methods with their implementation status.
  • Use Case: When auditing a new ATProto server implementation, use this Skill to quickly find all endpoints that are still stubs and need to be fully implemented, mapping them against the official lexicon definitions.

Quick Start

Run the skill's stub detection script to audit endpoint coverage.

Frequently Asked Questions about atproto-endpoint-stub-finder

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

FAQPage Schema
How does XRPC endpoint mapping against registered methods work for auditing API coverage?

Endpoint stub detection works by parsing Objective-C source files for placeholder markers such as `not_implemented`, `TODO`, and `FIXME`, then correlating those handlers against the registered XRPC method registry to expose incomplete logic.

Can I use this to map ATProto lexicon definitions against unimplemented endpoint stubs?

This Skill supports auditing ATProto server implementations by correlating registered XRPC methods with their implementation status, allowing you to quickly find endpoints that remain stubs and require full implementation.

What are the limitations of detecting ATProto endpoint stubs in Objective-C source files?

When auditing a new ATProto server implementation, this Skill maps registered XRPC methods against official lexicon definitions to find all endpoints that are still stubs and need to be fully implemented.

How do I find unimplemented ATProto XRPC endpoints in my Objective-C codebase?

This Skill requires parsing Objective-C source files and correlating findings with XRPC method registry definitions, so it will not detect unregistered methods or work with non-Objective-C codebases.