agentleFS
Sign inStart free
anotbanotb/x-signal/skills/x-setup/SKILL.md

x-setup

Skill1 starsChanged 3 months agoMITView on GitHub

Diagnose and operate X Signal Docker, browser, sign-in, MCP, operation, and tunnel setup. Use when installation, health, authentication, browser visibility, or client connection is failing.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. belzoralolbtw/x-agent-skill★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call x_status with liveProbe: true, then distinguish app, database, browser/CDP, X authentication/challenge, captured operation, and tunnel …

    line 8
  2. Very specific:

    Check docker compose ps, /healthz, /readyz, and redacted service logs.

    line 9

≈ “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 Signal setup

  1. Call x_status with liveProbe: true, then distinguish app, database, browser/CDP, X authentication/challenge, captured operation, and tunnel failures.
  2. Check docker compose ps, /healthz, /readyz, and redacted service logs. Use http://127.0.0.1:6080/vnc.html only for visible sign-in or challenge recovery.
  3. The persistent browser profile survives Compose and host restarts. For an alternate account, recommend a dedicated Chrome profile with the companion installed, automatic sync left on, and Use this profile selected once; the everyday Chrome profile can remain on another account. Never ask the user to paste cookies or tokens into chat. Check all named sources' lastSeenAt plus the active source's lastSyncedAt/lastAppliedAt and any pendingSessionSource. A different prepared profile is selected intentionally and automatic sync completes the switch after current runs settle. An account change inside the selected profile is detected from cookie changes and automatically deferred/retried behind active research. A same-profile one-time transfer can pause automatic sync, but X may invalidate it when that profile changes accounts.
  4. For local MCP clients use http://127.0.0.1:7345/mcp. For ChatGPT, use the Compose chatgpt profile and the hidden npm run tunnel:secure:configure prompt. Configure the tunnel ID, its owning Platform organization ID, and the runtime key so accounts with multiple organizations have an explicit control-plane context. Check the local tunnel /readyz and verify workspace association plus Tunnels Read + Use if it is not listed. Never capture or repeat a tunnel ID, organization ID, or runtime key. Use the path-gated temporary command only for an explicitly short-lived fallback, then refresh the app after schema changes.
  5. Give exact recovery commands and recheck status. Do not bypass X challenges or weaken loopback/tunnel authentication.

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.

Check your setup, free