agentleFS
Sign inStart free
seoutopicoseoutopico/pm_claude_code/.claude/skills/digest/SKILL.md

digest

Skill4 starsChanged 6 months agoMITView on GitHub

Genera un resumen periódico (semanal, mensual o ad-hoc) de avances, decisiones, bloqueos y próximos hitos. Trigger con "digest", "resumen semanal", "resumen del mes", "/digest".

33 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use aeon-update, auto-workflow 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.
  • aaronjmarsSkill

    aeon-update

    Pull framework updates from the upstream Aeon repo into this instance - 3-way merges canon's new commits into a PR, never clobbering operator config.

    Also in 4 projects that use this

  • aaronjmarsSkill

    auto-workflow

    Two-mode aeon.yml workflow builder - analyze inspects URLs and emits a tiered, signal-verified skill-enablement plan plus an aeon.yml diff; enable flips slugs to enabled:true and opens a PR.

    Also in 4 projects that use this

  • +10 more from aaronjmars

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 29 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:

    Default: última semana (lunes pasado hasta hoy).

    line 19

“Common” is measured: kept by at least 6 in 10 of the 29 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

Skill: Digest

Cuándo se activa

Cuando el usuario pide un "resumen", "digest", "informe semanal/mensual", o lanza /digest [periodo].

Qué hace

Lee el sistema y produce un resumen narrativo del periodo solicitado. No es un dashboard (eso es STATUS.md): es prosa breve para enviar por email, compartir con un manager, o leer al final del día.

Cómo proceder

  1. Determina el periodo:
    • Default: última semana (lunes pasado hasta hoy).
    • /digest mes → último mes natural.
    • /digest YYYY-MM-DD..YYYY-MM-DD → rango explícito.
  2. Recoge eventos del periodo filtrando por fecha:
    • Entradas de _memory/log.md en el rango.
    • Reuniones en _projects/*/meetings/<fecha>_*.md cuya fecha caiga en el rango.
    • Decisiones en _projects/*/decisions/ o en _memory/decisions.md registradas en el rango.
    • Cambios de estado de proyectos (si están en log).
  3. Lee _templates/digest.md para la estructura.
  4. Rellena las secciones:
    • Avances: qué se completó, en qué proyectos.
    • Decisiones: tomadas en el periodo, con enlace.
    • Bloqueos: nuevos, resueltos, pendientes.
    • Próximos hitos: fechas en los próximos 7-14 días (según periodo).
    • Atención: cosas que requieren input humano.
  5. Sé conciso. Un digest semanal cabe en pantalla. Un digest mensual no más de una página A4 leída con calma.
  6. Guarda el digest en _memory/digests/<YYYY-MM-DD>_<periodo>.md. Si la carpeta no existe, créala.
  7. Añade al log:
    ## [YYYY-MM-DD] digest | <periodo>
- Guardado en: _memory/digests/<...>
  8. Muestra el digest al usuario en la conversación.

Output esperado

El digest rellenado y guardado. Mensaje al usuario:

  • Periodo cubierto.
  • Ruta donde se guardó.
  • El contenido en pantalla.

Reglas

  • Hechos, no opiniones. El digest documenta lo ocurrido, no celebra ni dramatiza.
  • Enlaces relativos a proyectos, reuniones, decisiones para que sean navegables desde Obsidian o el editor.
  • Si el periodo no tiene movimiento, el digest lo dice explícitamente ("Sin avances registrados en proyectos activos") en vez de inventar.
  • Personalízalo a tu cadencia real editando _templates/digest.md. La plantilla por defecto es genérica.

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.

Check your setup, free