agentleFS
MazalucasMazalucas/El-DT-Lightweight-Army/.agents/skills/dt-gmail/SKILL.md

dt-gmail

Skill4 starsChanged 3 days agoMITView on GitHub

[Rutina] Conectar Gmail a la memoria del equipo — marketplace oficial del IDE, etiquetas, borradores en hilo. Use when the user invokes /gmail or wants the DT to search mail or leave drafts.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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. Distinctive:

    No abras el runbook de IT ni fichas de Google Cloud en este chat.

    line 12
  2. Distinctive:

    No recorras Google Cloud Console.

    line 42
  3. Very specific:

    No abras el runbook de IT.

    line 43
  4. Very specific:

    No leer “todo el correo” salvo sync_mode: full_mailbox pedido explícito.

    line 48
  5. Distinctive:

    No copiar hilos sensibles al repo.

    line 61
  6. Distinctive:

    No commitear contextos ni cuentas GCP.

    line 78
  7. Distinctive:

    No asumir Gmail conectado — opt-in.

    line 81
  8. Distinctive:

    No dictar el alta en Cloud.

    line 82

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

dt-gmail

Integración opcional de Gmail vía el MCP oficial del IDE. google-drive-dt está descontinuado.

Spec: vitals/specs/google-apps-mcp.md. Guía usuario: docs/02_guides/google-contexto-setup.md (DOC-GUIDE-009). ADR: DOC-DEC-006.

No abras el runbook de IT ni fichas de Google Cloud en este chat.

Prerequisitos

Sesión (/yo). Plugin, MCP Store o conector oficial de Gmail. Sin JSON Desktop ni Node.

Archivos

ArchivoGitRol
vitals/config/google-apps.yamlNoApps habilitadas
vitals/config/gmail-context.yamlNoEtiquetas / queries
vitals/config/gmail-context.yaml.exampleSíPlantilla

Flujo /gmail

  1. Confirmar /yo.
  2. Embudo: ¿solo Gmail o también Drive y Calendar?
  3. Instalar el oficial con el procedimiento único de vitals/specs/google-apps-mcp.md § Instalar. Slug en Cursor: gmail. Marketplace / Store primero. No recorras Google Cloud Console.
  4. Esperar tools de búsqueda/lectura/draft. Si no hay, Freno — no inventar el inbox.
  5. Selector de contexto. Actualizar google-apps.yaml (gmail: true) y gmail-context.yaml.
  6. Legado google-drive-dt → ofrecer --remove-legacy cuando el oficial ya lea mail.

Si solo quieren cambiar etiquetas y Gmail ya está → selector.

Freno

Si no hay tools o no aparece Authenticate:

  1. Parar. No seguir al selector. No inventar el inbox.
  2. No recorras Google Cloud Console.
  3. No abras el runbook de IT. No armes un JSON con clientId.
  4. Decí solo: Falta el client OAuth de la organización. Pedíselo a IT. Si no hay IT, usá la documentación oficial de Google Workspace MCP en tu navegador. El DT no recorre Google Cloud Console ni pega secrets.

Selector de contexto

No leer “todo el correo” salvo sync_mode: full_mailbox pedido explícito.

  1. Mostrar gmail-context.yaml si existe.
  2. Pedir etiquetas y/o queries (from:, newer_than:, label:) con propósito.
  3. Si hay list_labels / list_email_labels, ayudar a elegir.
  4. Escribir el YAML (schema del .example). No va a Git.

Uso diario

  1. Acotar a labels/queries (selective).
  2. Borradores — create_draft / draft_email / gmail_create_draft. Reply en cadena: replyToMessageId o threadId + inReplyTo. El humano envía en Gmail.
  3. Etiquetar mails/hilos existentes si lo piden. Crear label nuevo solo con pedido explícito y tool real.
  4. Nunca enviar — no send_email, no messages.send, no drafts.send.
  5. No copiar hilos sensibles al repo.
  6. El token ve todo el buzón; el YAML es política DT.

Tools

Usar las que existan (spec). Típico oficial Google: search_threads, get_thread, create_draft, list_labels, label_message, label_thread. Cursor puede exponer nombres distintos (search_emails, read_email, draft_email).

Errores frecuentes

SíntomaAcción
Plugin canceladoNo seguir al selector. Ofrecer /add-plugin gmail
needsAuthEl operador autentica el plugin; no fingir el inbox
Antigravity o Claude sin AuthenticateFreno. No caer a google-drive-dt

No hacer

  • No commitear contextos ni cuentas GCP.
  • No enviar mail.
  • No reinstalar google-drive-dt.
  • No asumir Gmail conectado — opt-in.
  • No dictar el alta en Cloud.

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.