agentleFS
p10ns11yp10ns11y/skills/x-agent-resources/SKILL.md

x-agent-resources

Skill2 starsChanged 40 days agoMITView on GitHub

Integration and usage of official X Developer Platform agent resources (llms.txt, skill.md, MCP/XMCP, xurl, OpenAPI) for accurate, composable X access in agentic apps. Use when building search, analysis, posting, or any X interaction. Ensures llms/skill ground prompts, MCP exposes tools, xurl provides CLI UX. Fission for implementation; fusion for unifying with finder-reactor and agentic design.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never assume X API behavior not in current skill.md/llms.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

X Agent Resources — Official Primitives for X-Powered Agents

Core Mission: Make every X interaction correct, efficient, and agent-composable by treating official X agent resources as first-class citizens.

Key Resources (Always Reference Fresh or Cached)

Agent read order (mandatory for X work)

  1. Vendored snapshot in your project (e.g. .agents/x-resources/skill.md) — read first.
  2. This skill — integration patterns for your app.
  3. Live https://docs.x.com/... if behavior disagrees with snapshot — refresh vendored copy.

Integration Principles

  1. Ingest for Intelligence: LLM calls include relevant excerpts from X skill.md + llms context.
  2. MCP for Composability: Expose app functions (search, analyze, prep, promote) as MCP tools; use XMCP for direct X ops when richer than a custom client.
  3. xurl for UX & Fallback: Shell to xurl for ad-hoc or as reference implementation.
  4. Follow the Spec: Publish your own SKILL.md compatible with agentskills.io.
  5. Self-Guards Apply: MCP tool calls respect the same guards/pauses as the UI.

Implementation Patterns

  • At startup / refresh: Load vendored X resources; copy to app data in production if needed.
  • Backend client: Validate/build queries using skill.md knowledge; prefix prompts with current capabilities excerpt.
  • MCP Server: Tools like search_x_opportunities, analyze_and_decide, generate_prep_with_guards, promote_with_preview.
  • UI: Command palette maps 1:1 to MCP tools.
  • Prompt library: Central file combining X skill + CV packet + app state.
  • Testing: bdd-strategizer for guard scenarios (429, low rate, pause).

Guardrails

  • Never assume X API behavior not in current skill.md/llms.
  • Writes (posts, DMs): always guard + user pause.
  • Rate limits: surface from headers; backoff in reactor.
  • Auth: secure OS keyring or encrypted store — never hardcode tokens.

Related

finder-reactor, tauri-agentic, ai-optimization, fusion-sage.

Official: https://docs.x.com/tools/ai

Example provenance: collab-finder.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.