agentleFS
KonHKonH/GlobalStrategy/.claude/skills/meeting-schedule/SKILL.md

meeting-schedule

Skill3 starsChanged 2 months agoMITView on GitHub

Create a new multi-agent meeting under Docs/Meetings/ — agenda.md, empty log.md, and a live-viewer log.html — from a short agenda description. Use when asked to schedule/set up a meeting for Claude/Codex/Cursor agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write agenda.md, free-form but at minimum covering:

    line 25
  2. Very specific:

    Create an empty log.md (zero bytes).

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Meeting schedule

Creates the meeting directory and its artifacts. Does not join or start the meeting — that's meeting-join / meeting-start.

Args

/meeting-schedule <short agenda description> [slug]

  • short agenda description (required): a sentence or two describing the meeting's theme.
  • slug (optional): kebab-case directory suffix. If omitted, derive a short (3-5 word) kebab-case slug from the description.

Steps

  1. Compute the timestamp prefix YY_MM_DD_HH from the current date/hour (same convention as Docs/Specs/<YY_MM_DD_HH>_<name>).
  2. Create Docs/Meetings/<YY_MM_DD_HH>_<slug>/.
  3. Write agenda.md, free-form but at minimum covering:

    # <Meeting theme, restated briefly>
    
    ## Agenda
    <the short agenda description as given>
    
    ## Definition of done
    - [ ] <inferred from the description — what "done" looks like>
    
    ## Checklist
    - [ ] <inferred discussion/action points>

    Flesh out the definition-of-done and checklist reasonably from the description rather than leaving placeholders — the owner and participants read this to know what the meeting is actually for.

  4. Create an empty log.md (zero bytes).
  5. Copy scripts/meetings/log_template.html verbatim to log.html. It's a generic viewer — nothing in it is meeting-specific; it prompts the viewer to pick the log.md file to watch when opened.
  6. Report the created path, and that whoever will run meeting-start on it becomes the owner (first-come — there's no separate reservation step).

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.