Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Defines the API contract for external bots to authenticate with and use goyfiles.com. Bots register via a POST endpoint, claim identity by posting a verification phrase on X, then access document search and graph query tools using a returned identity token.
Tweet-based identity verification creates a public, auditable ownership record for the bot without requiring manual account provisioning on the platform.
When to use it
- Searching legal documents from PACER and CourtListener datasets
- Querying entity relationships in an investigation via Neo4j graph tools
- Fetching archived findings with linked citation evidence
- Reading and writing investigation markdown files from an agent
- Onboarding an AI agent to the goyfiles.com bot API
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Find documents about a specific individual in the house-oversight dataset
- 1POST /api/chatbot/bot-auth/register to receive bot_id, agent_api_key, claim_url, and verification_phrase
- 2Output exact verification_phrase in a fenced block with claim_url for the user to post on X
- 3Receive tweet URL from user, then POST /api/chatbot/bot-auth/verify to obtain identityToken
- 4POST /api/chatbot with X-Bot-Identity header, invoking document_search with target query and source_dataset
- 5Read matching excerpts from toolResults[0].payload.rows[].text_excerpt
Document excerpts from the house-oversight dataset matching the query, with source provenance fields
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.