Skip to content

lab-meeting-digest

Reads the week's project updates and posts a summary on the morning before lab meeting.

  • Recipe: Make materials accessible
  • Output check: Expert-checkable Every line links to its source. The group leader reads the digest before the meeting.
  • Status: brief

Make your own version

This skill depends on local details, so the site publishes a brief instead of one institute's skill. Copy the brief and give it to your agent. If your agent has a skill-creation skill, such as Anthropic's skill-creator, it will use it. The agent asks you the questions under "Local details", builds the skill, and runs it once on the test case.

An agent that can read web pages can also fetch the brief itself from https://aiforscientists.eu/skills/lab-meeting-digest/brief.md.

# Skill brief: lab-meeting-digest

Source: https://aiforscientists.eu/skills/lab-meeting-digest/
Recipe: Make materials accessible (https://aiforscientists.eu/recipes/01-make-materials-accessible/)

Build a skill for my own setting from this brief.
If you have a skill-creation skill or tool, use it.
Before you write anything, ask me each question under "Local details", one at a time.
Do not guess an answer; if I do not know one, leave a marked TODO in the skill.
Keep every rule under "Never" in the skill you write.
Write the check under "How to check the output" into the skill, so that it runs every time.
Then run the skill once on the test case and show me the result.

## Purpose

Reads the week's project updates and posts a summary on the morning before lab meeting.

## Inputs

- The week's project updates: notes, issues, commits or messages.
- The list of projects and the people working on them.

## Output

- A digest of overlaps between projects, overdue items and suggested priorities, with a link to each source.

## Steps

1. Collect the updates since the last meeting.
2. Summarise each project in two or three lines.
3. List overlaps between projects and items that are overdue.
4. Suggest priorities, and mark them as suggestions.
5. Post the digest at the scheduled time.

## Local details

1. Where do project updates live (repositories, issue tracker, notes tool, chat)?
2. When is lab meeting, and when should the digest arrive?
3. Where should the digest be posted, and who can read it?
4. Which projects or people must be left out?

## Never

- Never post anything about a person's performance.
- Never post to a channel outside the group.

## How to check the output

Every line links to its source. The group leader reads the digest before the meeting.

## Test case

Run it on last week's updates, and compare the digest with what was discussed in the meeting.

Local details

Your version needs answers to these questions:

  1. Where do project updates live (repositories, issue tracker, notes tool, chat)?
  2. When is lab meeting, and when should the digest arrive?
  3. Where should the digest be posted, and who can read it?
  4. Which projects or people must be left out?

Never

  • Never post anything about a person's performance.
  • Never post to a channel outside the group.

Local versions

No local version is published yet. If you built one, share it as an example for others.

Discussion

Used this recipe or skill, or seen it fail? Say so here. Comments need a GitHub account; without one, write to aiforscience@googlegroups.com.