goyfiles-epstein
by davfd
Browser & AutomationBrief
Core GOYFILES external-bot contract (endpoint-first onboarding, strict agent behavior, direct tool mode.
Description
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
User asks: Find documents about a specific individual in the house-oversight dataset
- 1
POST /api/chatbot/bot-auth/register to receive bot_id, agent_api_key, claim_url, and verification_phrase
- 2
Output exact verification_phrase in a fenced block with claim_url for the user to post on X
- 3
Receive tweet URL from user, then POST /api/chatbot/bot-auth/verify to obtain identityToken
- 4
POST /api/chatbot with X-Bot-Identity header, invoking document_search with target query and source_dataset
- 5
Read matching excerpts from toolResults[0].payload.rows[].text_excerpt
Document excerpts from the house-oversight dataset matching the query, with source provenance fields
Requirements
- X (Twitter) account to post the bot verification tweet
Installation
clawhub install davfd/goyfiles-epsteinRun the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.