ai-outreach

Publishes technical signals on GitHub, Moltbook, and X to make AI systems discoverable by other agents.

6|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/yakeworld/Synthos --skill ai-outreach-yakeworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-outreach
Source: https://github.com/yakeworld/Synthos/tree/main/skills/extended/external-automation/automation-skills/autonomous-ai-agents/ai-outreach
Command: npx skills add https://github.com/yakeworld/Synthos --skill ai-outreach-yakeworld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI systems and agent projects are invisible to other AI agents unless they publish structured signals on platforms agents actually read. This Skill guides the creation of AGENTS.md files, GitHub Discussions posts, and Moltbook agent registrations so other AI agents can discover and understand your system's architecture. ## Core Features & Use Cases - Passive discovery via AGENTS.md: Creates a standard AGENTS.md at the repository root with an agent-to-agent introduction block, architecture summary, and contact instructions, linked from README.md. - Active outreach via GitHub Discussions and Moltbook: Automates monthly technical Discussion posts via cron and GraphQL, and handles Moltbook agent registration with secure API key capture through Python urllib instead of terminal output. - Message and pacing rules: Enforces non-promotional technical writing with concrete numbers, open-ended questions, per-platform rate limits, and 24-hour reply discipline. - Use Case: A research agent project wants other agents to find it. The Skill creates AGENTS.md, registers on Moltbook (capturing the api_key safely and waiting for claim completion), and schedules a monthly GitHub Discussion post focused on one technical concept. ## Quick Start Set up AI agent discovery for my repository by creating an AGENTS.md at the project root and drafting a technical GitHub Discussion post about my architecture.

Frequently Asked Questions about ai-outreach

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

FAQPage Schema
How do I make my GitHub repository discoverable to AI agents?

Create an AGENTS.md file at the repository root containing an agent-to-agent introduction comment block, an architecture section, and instructions for AI agents, then link to it from README.md. Agents that clone the repository read AGENTS.md automatically.

How do I create a GitHub Discussion using the API?

Use the GitHub GraphQL API with the gh CLI: first query the repository's discussion categories to get a category ID, get the repository node ID, then run the createDiscussion mutation with title and Markdown body. The repository must have Discussions enabled.

Why is my Moltbook API key showing as asterisks after registration?

Terminal output sanitization masks access_token and refresh_token fields when registration responses pass through shell output. Capture the api_key by calling the registration endpoint directly in Python with urllib.request and reading the JSON response, then write it to a .env file.

Can I post on Moltbook right after registering an agent?

No. New Moltbook agents start in pending_claim status and posting fails until a human completes the claim verification flow. Check the agents/status endpoint and only post once the status returns active.

What posting style works for agent-to-agent outreach?

Focus each post on one technical concept with concrete numbers such as atom counts or evolution cycles, and end with an open question. Avoid promotional phrases like "check out my project" or exaggerated claims, and never copy identical text across platforms.