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.
In this repository169 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/00-orquestador-core.mdcCursor rule
- .cursor/rules/01-protocolos-dt.mdcCursor rule
- .cursor/rules/02-documentacion.mdcCursor rule
- .cursor/rules/03-catalogo-subagentes.mdcCursor rule
- .cursor/rules/05-multi-project-git.mdcCursor rule
- .cursor/rules/06-dt-colaboracion.mdcCursor rule
- .cursor/rules/07-orden-continuo.mdcCursor rule
- .cursor/rules/08-stack-web-default.mdcCursor rule
- .cursor/rules/10-arquitectura-backend.mdcCursor rule
- .cursor/rules/15-engineering-reuse.mdcCursor rule
- .cursor/rules/16-numeric-grounding.mdcCursor rule
- .cursor/rules/17-canvas-first.mdcCursor rule
- .cursor/rules/18-drive-contexto.mdcCursor rule
- .cursor/rules/19-gmail-contexto.mdcCursor rule
- .cursor/rules/20-frontend-ui.mdcCursor rule
- .cursor/rules/21-calendar-contexto.mdcCursor rule
- .cursor/rules/30-testing.mdcCursor rule
- .cursor/rules/31-agent-inbox.mdcCursor rule
- .cursor/rules/40-devops.mdcCursor rule
- .cursor/rules/90-seguridad-secrets.mdcCursor rule
- analisis-propuestaSkill
- arquitectoSkill
- atelier-actualizarSkill
- atelierSkill
- auditoria-legalSkill
- bragSkill
- brand-guardianSkill
- content-creatorSkill
- data-auditorSkill
- deploySkill
- development-plannerSkill
- devopsSkill
- docSkill
- dt-actualizarSkill
- dt-ayudaSkill
- dt-bootstrapSkill
- dt-configSkill
- dt-driveSkill
- dt-gmailSkill
- dt-oficialSkill
- dt-ordenarSkill
- dt-revisar-instalacionSkill
- dt-sessionSkill
- dt-setupSkill
- dt-skillsSkill
- engineering-reuseSkill
- feedback-synthesizerSkill
- frontendSkill
- git-actualizarSkill
- git-guardarSkill
- github-save-releaseSkill
- growth-hackerSkill
- hack-auditSkill
- marketing-strategistSkill
- operations-maintainerSkill
- pitch-specialistSkill
- prd-creatorSkill
- The first 60 shown.
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
- Distinctive: line 12
No abras el runbook de IT ni fichas de Google Cloud en este chat.
- Distinctive: line 42
No recorras Google Cloud Console.
- Very specific: line 43
No abras el runbook de IT.
- Distinctive: line 62
No copiar descripciones sensibles al repo.
- Distinctive: line 78
No commitear contextos ni cuentas GCP.
- Distinctive: line 79
No borrar recurrentes enteros sin avisar.
- Distinctive: line 81
No asumir Calendar conectado — opt-in.
- Distinctive: line 82
No dictar el alta en Cloud.
≈ “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.
Files
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
| Archivo | Git | Rol |
vitals/config/google-apps.yaml | No | Apps habilitadas |
vitals/config/calendar-context.yaml | No | Calendarios + zona horaria |
vitals/config/calendar-context.yaml.example | Sí | Plantilla |
Flujo /calendar
- Confirmar
/yo. - Embudo: ¿solo Calendar o también Drive y Gmail?
- 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. - Esperar tools de listar/crear eventos. Si no hay, Freno.
- Selector de calendarios.
google-apps.yaml(calendar: true) +calendar-context.yaml. - Legado
google-drive-dt→--remove-legacycuando el oficial liste eventos.
Si solo quieren cambiar calendarios → selector.
Freno
Si no hay tools o no aparece Authenticate:
- Parar. No seguir al selector. No inventar la agenda.
- No recorras Google Cloud Console.
- No abras el runbook de IT. No armes un JSON con
clientId. - 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.
- Mostrar
calendar-context.yamlsi existe. - Zona horaria (default
Europe/Madridsi no dicen otra). - Calendarios extra (Calendar ID) o quedarse en
primary. - Por cada uno: propósito;
write: truesolo si aceptan que el DT cree/edite. sync_mode: all_calendarssolo si lo piden.- Escribir el YAML (schema del
.example). No va a Git.
Uso diario
- Operar solo en
calendars[].id(selective). - Crear/editar si lo piden y
write: true. Borrar solo con confirmación. - Citar calendario + título + horario.
- 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íntoma | Acción |
| Plugin cancelado | No seguir al selector. Ofrecer /add-plugin google-calendar |
needsAuth | El operador autentica el plugin; no fingir la agenda |
| Antigravity o Claude sin Authenticate | Freno. 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.
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
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.

