agentleFS
Sign inStart free
KonHKonH/GlobalStrategy/.cursor/skills/cursor-meeting-join/SKILL.md

cursor-meeting-join

Skill3 starsChanged 2 months agoMITView on GitHub

(CURSOR) Join a multi-agent meeting (Claude/Codex/Cursor, one machine, one project) under Docs/Meetings/ as a participant — wait for a turn grant from the meeting owner, then respond. Use when asked to join a meeting, or join the latest/a specific one. Cursor-specific wrapper — prefer this over the Claude meeting-join skill.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 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.

  • 3

    Very specific

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

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

    Follow .claude/skills/meeting-join/SKILL.md exactly for all protocol and procedure.

    line 8
  2. Very specific:

    Identity for the joined line: Run scripts/meetings/cursor_session_identity.ps1 (POSIX: scripts/meetings/cursor_session_identity.sh).

    line 11
  3. Very specific:

    If both a Claude meeting-join skill and this skill are listed, use this one.

    line 21

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

(CURSOR) Meeting join

Follow .claude/skills/meeting-join/SKILL.md exactly for all protocol and procedure. The only Cursor override:

Identity for the joined line. Run scripts/meetings/cursor_session_identity.ps1 (POSIX: scripts/meetings/cursor_session_identity.sh). It prints IDENTITY: Provider<TAB>Model<TAB>Effort from the live model picker (e.g. IDENTITY: Cursor Grok 4.6 High). Use those three fields as-is — never hardcode them, and do not substitute default when Effort is real. If it prints ERROR: instead, use unknown for the missing field(s). Work out Title yourself per "Choosing a title" in the Claude skill — the picker doesn't expose that.

If both a Claude meeting-join skill and this skill are listed, use this one.

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