agentleFS
TheVellerTheVeller/claude-skills/skills/agent-operations/identity-pipeline/SKILL.md

identity-pipeline

Skill4 starsChanged 14 days agoMITView on GitHub

Use when alta con identidad, auditing identity (incl. Composio fase 1, Postly/composio connect fase 3), Chrome profiles per-bot, or updating identity inventory.

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:

    Start without Orq + Ignacio OK.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Identity pipeline (Bot Father)

Factory execution + identity inventory for agents/bots. Grok Bot = roster SSOT + “alta con identidad”. Bot Father = pipeline + identity ledger + CreateAgent when named. Ignacio = HITL + structural yes in 1:1.

Must NOT

  • Invent oficios / CreateAgent without Orq naming.
  • Start without Orq + Ignacio OK.
  • Skip HITL (captcha/SMS/2FA).
  • Touch Mac Orca/Herdr (Hermes) or ZeroClaw (Orq) inside this pipeline.
  • Duplicate Gmails for the same agent; paste secrets in chat.
  • Replace Orq roster SSOT — only own identity columns.

Phases (updated)

Fase 1 — core (obligatorio antes de CreateAgent serio)
VPN → Gmail real → AgentMail → (número/Instinct si Orq pidió) → cuenta Composio.dev (por identidad o compartida según Orq) → Bitwarden (títulos en ledger) → Chrome profile dedicado → CreateAgent si aplica.

Fase 2 — otras cuentas
Google Sign-In apps, redes (FB/IG/…), ChatGPT, etc. Solo con Ignacio OK y fase 1 estable.

Fase 3 — cablear
Conectar todo a Composio (connectors del agente) + social scheduler (Postly LTD, hasta ~200 workspaces / cuentas ilimitadas según plan Ignacio). No crear Postly de nuevo si ya existe LTD; asignar workspace/cuentas.

Chrome profiles

  • Extensiones (Bitwarden, Surfshark, …) son por perfil, no globales entre bots.
  • Homelab tools (VPN/vault): prefer perfil Ignacio/Orq.
  • Identidad de agente: ~/.chrome-profiles/<slug> propio; instalar extensiones ahí si esa identidad las necesita.
  • Un alta a la vez; bajo RAM = un Chrome.

Inventory

/workspace/lab/state/identity-inventory.md — no secrets; Bitwarden title only. Include composio account + postly workspace columns when known.

Triggers

/identity-pipeline, Orq webhook alta. No Kit OS @mention cron. Fleet healthchecks off until Ignacio enables.

Related

[alta-identidad](alta-identidad skill), brand-chrome-login, Postly = fase 3 scheduler (Ignacio already has LTD).

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.