agentleFS
Sign inStart free
Simple-With-UsSimple-With-Us/BotFleet/.claude/skills/fleet-infra/SKILL.md

fleet-infra

Skill4 starsChanged 11 days agoApache-2.0View on GitHub

Access private fleet infrastructure inventory (host IPs, Tailscale mesh IPs, Coolify container UUIDs, Infisical project IDs, and SSH keys) maintained in Simple-With-Us/fleet-ops:ATTACK-MAP.md. Use when locating production servers, configuring environment variables, verifying edge routing, or handling infrastructure secrets without leaking them into public repos.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 0 are distinctive, and 6 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.

  • 6

    Very specific

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

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

    All fleet repositories except fleet-ops are public.

    line 15
  2. Very specific:

    Read /Users/jay/Code/fleet-ops/ATTACK-MAP.md privately.

    line 20
  3. Very specific:

    Do not fetch ATTACK-MAP.md over HTTP.

    line 23
  4. Very specific:

    Always read values from environment variables (INFISICAL_PROJECT_ID, COOLIFY_ST_APP_UUID, HETZNER_HOST_IP, etc.) or query them dynamically …

    line 42
  5. Very specific:

    Read credentials with fleet-secrets get NAME (Mac) or from Infisical.

    line 45
  6. Very specific:

    Use RFC 5737 documentation ranges (192.0.2.1, 198.51.100.1, 203.0.113.1) and generic mock UUIDs (mock-app-uuid, mock-project-id) in test …

    line 48

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

Fleet Infrastructure & Private Inventory Access (ALL AGENTS)

Shared ~/.claude/skills. Monet, Claude/Fable, and (when active) Renoir all load this directory. Do not treat the word Monet in examples as proof of your seat. Pin AGENT_SEAT / AGENT_TAG from the logged-in account before Slack or board --by:

  • Monet → MONET, Notes Monet, monet/, ~/apps/<app>-monet
  • Claude / Fable → CLAUDE, Notes Claude, claude/, ~/apps/<app>-claude
  • Renoir → RENOIR, Notes Renoir, renoir/, ~/apps/<app>-renoir Cursor, Grok, Grok Bot, Codex, AG, DeepSeek, Kimi, and Fx have their own skill dirs and must not take identity from here.

All fleet repositories except fleet-ops are public. To protect origin infrastructure from direct attacks, scanning, and DDoS, production host IPs, Tailscale IPs, Coolify container/server UUIDs, hardware serials, and secret keys must never be committed to public repositories or printed to chat/logs.

Canonical Inventory Location

  • Local Workstation Agents (Mac/Terminal): Read /Users/jay/Code/fleet-ops/ATTACK-MAP.md privately. Copy only the single field the task needs. Never paste the file, a host list, or a Tailscale address into chat or a public repo.
  • Cloud / Remote Agents (without direct repo access): Do not fetch ATTACK-MAP.md over HTTP. A curl (or similar) with Authorization: Bearer ${MAC_COLLAB_TOKEN} puts the token on argv and dumps the whole inventory into the transcript. Ask a Mac seat to read the file locally and return only the redacted field required for the task.

What Lives in fleet-ops:ATTACK-MAP.md

  1. Host Topology & IP Addresses: Production public IPs, Tailscale MagicDNS names, mesh IPs, workstation relay addresses, and retired-host notes. None of those values belong in this public skill.
  2. Coolify Container & Server UUIDs: Server and application UUIDs for Socratic.Trade, Congress.Trade, and Usage-Monitor.
  3. Infisical Project IDs: Project workspace IDs for ST, CT, Shared, and UM scopes.
  4. Edge & Access Control Rules: Cloudflare origin isolation, SSH restricted to the Tailscale mesh, and Coolify control-plane bind rules.

Invariants for Public Repositories

  1. Never Hardcode Infrastructure IDs in Public Repos: Always read values from environment variables (INFISICAL_PROJECT_ID, COOLIFY_ST_APP_UUID, HETZNER_HOST_IP, etc.) or query them dynamically via authenticated APIs.
  2. Secrets Handoff Protection: Read credentials with fleet-secrets get NAME (Mac) or from Infisical. Never cat, grep -E '^[A-Z0-9_]+=', or log secret values into transcripts.
  3. Mock Data in Tests & Documentation: Use RFC 5737 documentation ranges (192.0.2.1, 198.51.100.1, 203.0.113.1) and generic mock UUIDs (mock-app-uuid, mock-project-id) in test fixtures and public rollouts.

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