agentleFS
MiguelARojas3103MiguelARojas3103/rtovar-aios/.agents/skills/brief/SKILL.md

brief

Skill0 starsChanged 29 days agoMITView on GitHub

Resume qué tengo por delante leyendo mi sistema y, si están conectados, mi calendario y mi correo. Úsala cuando el usuario diga "/brief", "qué tengo hoy", "qué tengo pendiente", "por dónde voy", "en qué estaba", "arma mi día" o al empezar una sesión de trabajo.

81 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use capture, strategy and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • toneron2Skill

    capture

    Capture thoughts to inbox with automatic classification

    Also in 6 projects that use this

  • EpistatesSkill

    strategy

    Plan weekly or monthly X content strategy. Use when the user wants to plan their content calendar, set growth goals, build a content pipeline, or think strategically about their X presence.

    Also in 4 projects that use this

  • aleksander-dytkoSkill

    decision

    Make a product decision with full context from the vault and available sources

    Also in 3 projects that use this

  • dirienSkill

    decide

    Three-agent adversarial debate protocol for strategic decisions. Two advocates steelman opposing positions while a moderator identifies risks and synthesizes a binding consensus. Use when choosing between alternatives, evaluating tradeoffs, or making high-stakes decisions.

    Also in 5 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 7 projects that use this

  • howellsSkill

    reconcile

    Audit a project against current plugin conventions and offer to update structure.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 73 edited versions we read keep these.

  • 1

    Distinctive

    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:

    No copies el contenido de los correos, solo remitente y asunto.

    line 44

“Common” is measured: kept by at least 6 in 10 of the 73 edited versions of this file we could read. “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

Brief

Dile al usuario dónde está parado y qué debería atender ahora. Solo lee: nunca envía, crea ni borra nada.

Qué leer

En este orden, sin pedir permiso:

  1. AGENTS.md: la sección "En qué estoy trabajando".
  2. memory/index.md y las páginas con fechas próximas o proyectos activos.
  3. proyectos/*/NOTAS.md: el estado de cada proyecto.
  4. universidad/: qué materias hay y si alguna tiene entregas anotadas.
  5. Si hay herramientas de Composio disponibles (mira memory/wiki/conexiones.md o si tienes herramientas COMPOSIO_*):

    • Calendario: los eventos de hoy y de los próximos 3 días.
    • Correo: los no leídos de las últimas 24 horas, solo remitente y asunto.
    • GitHub: issues o pull requests abiertos que tenga asignados.

    Usa únicamente acciones de lectura (las que buscan, listan u obtienen). Si una acción manda, crea, actualiza o borra algo, no la uses. Si la conexión falla, sigue sin ella y dilo en una línea.

Si algo no existe, sáltalo sin comentarlo.

Qué reportar

Corto. Nadie lee un brief de dos pantallas.

Primero: lo que tiene fecha. Eventos, entregas, exámenes o compromisos con día, con los días que faltan. Lo que esté a menos de 72 horas va de primero.

Después: en qué estaba. Una línea por proyecto activo, con su estado según sus notas.

Si hay correo conectado: los mensajes que parezcan pedir respuesta, máximo cinco, una línea cada uno.

Al final: tres cosas para hoy. Concretas, empezando por un verbo, ordenadas por lo que más mueve la aguja.

Cierra preguntando por cuál quiere empezar.

Reglas

  • Solo reporta lo que leíste. Si no hay fechas anotadas, dilo y sugiere dónde anotarlas. No inventes entregas ni eventos.
  • No copies el contenido de los correos, solo remitente y asunto.
  • Si el sistema está casi vacío, dilo sin rodeos y propón /conoceme.
  • Si algo lleva semanas sin tocarse, menciónalo una vez.

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.