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

dt-calendar

Skill4 starsChanged 4 days agoMITView on GitHub

[Rutina] Conectar Google Calendar a la memoria del equipo — marketplace oficial del IDE, calendarios, eventos. Use when the user invokes /calendar or wants the DT to list or create calendar events.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

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

    No copiar descripciones sensibles al repo.

    line 62
  5. Distinctive:

    No commitear contextos ni cuentas GCP.

    line 78
  6. Distinctive:

    No borrar recurrentes enteros sin avisar.

    line 79
  7. Distinctive:

    No asumir Calendar 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 372,429 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-calendar

Integración opcional de Calendar 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 Calendar. Sin JSON Desktop ni Node.

Archivos

ArchivoGitRol
vitals/config/google-apps.yamlNoApps habilitadas
vitals/config/calendar-context.yamlNoCalendarios + zona horaria
vitals/config/calendar-context.yaml.exampleSíPlantilla

Flujo /calendar

  1. Confirmar /yo.
  2. Embudo: ¿solo Calendar o también Drive y Gmail?
  3. Instalar el oficial con el procedimiento único de vitals/specs/google-apps-mcp.md § Instalar. Slug en Cursor: google-calendar. Marketplace / Store primero. No recorras Google Cloud Console.
  4. Esperar tools de listar/crear eventos. Si no hay, Freno.
  5. Selector de calendarios. google-apps.yaml (calendar: true) + calendar-context.yaml.
  6. Legado google-drive-dt → --remove-legacy cuando el oficial liste eventos.

Si solo quieren cambiar calendarios → selector.

Freno

Si no hay tools o no aparece Authenticate:

  1. Parar. No seguir al selector. No inventar la agenda.
  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 calendarios

Default: id: primary.

  1. Mostrar calendar-context.yaml si existe.
  2. Zona horaria (default Europe/Madrid si no dicen otra).
  3. Calendarios extra (Calendar ID) o quedarse en primary.
  4. Por cada uno: propósito; write: true solo si aceptan que el DT cree/edite.
  5. sync_mode: all_calendars solo si lo piden.
  6. Escribir el YAML (schema del .example). No va a Git.

Uso diario

  1. Operar solo en calendars[].id (selective).
  2. Crear/editar si lo piden y write: true. Borrar solo con confirmación.
  3. Citar calendario + título + horario.
  4. No copiar descripciones sensibles al repo.

Tools

Las que existan: calendar_list_events, calendar_create_event, calendar_update_event, calendar_delete_event, o equivalentes del plugin oficial.

Errores frecuentes

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

No hacer

  • No commitear contextos ni cuentas GCP.
  • No borrar recurrentes enteros sin avisar.
  • No reinstalar google-drive-dt.
  • No asumir Calendar 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.