agentleFS
stardustaistardustai/stardust-skills/skills/ceo-calendar-invite/SKILL.md

ceo-calendar-invite

Skill0 starsChanged 2 months agoMITView on GitHub

Use for incoming DingTalk calendar invitations, calendar cards, meeting invitations, attendance decisions, schedule conflicts, tentative, accept, or decline responses, and questions about why the principal should attend or what input is expected. Use ceo-meeting-work for meeting content after attendance is settled. Load dingtalk-calendar before issuing any DWS calendar command.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Use the supplied exact event command first.

    line 17
  2. Distinctive:

    Do not ask broad questions such as whether the principal should attend.

    line 40
  3. Distinctive:

    Before execution, Audit B rereads the live event state and the applicable Skills.

    line 48

≈ “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

CEO Calendar Invite

Decide from the live invitation, schedule context, attendance value, and requested contribution. Calendar responses and factual clarification questions are Consumer proposals for Audit B to execute and verify.

Load And Read

Load dingtalk-calendar before every calendar read or write. Load dingtalk-chat before a chat fallback. Load dingtalk-doc or dingtalk-drive before reading the corresponding linked material; follow those Skills instead of copying their command catalogs here.

Use the supplied exact event command first. Read the title, time, organizer, attendees, description, comments, linked materials, the principal's current response state, and conflicting accepted events. Reuse confirmed facts from the trigger, conversation, and live results; do not ask for facts already present.

Decide

  • Accept when the principal's decision or customer, product, personnel, or cross-team input has clear value.
  • Tentatively hold when the meeting is relevant but confirmation is premature.
  • Decline when the event is only broadcast or synchronization and the principal's input is not needed.
  • A missing description alone is not a reason to clarify. Decide from the other confirmed facts when they establish the value.
CaseDecisionClarificationRequired handling
clear_valueacceptnoPropose acceptance.
worth_holding_but_uncertaintentativenoPropose a tentative hold.
no_principal_input_neededdeclinenoPropose decline.
missing_attendance_valueclarify_inviteryesAsk what decision or input is required.
missing_description_but_clear_titleacceptnoDo not clarify only for the description.
silent_meeting_with_materialprocess_material_and_acceptnoProcess the material and produce the requested review outcome, then propose acceptance.
silent_meeting_without_materialclarify_exact_materialyesAsk for the referenced material itself.

Clarify

If participation value or requested input remains unclear after the reads, ask the verified inviter one concrete factual question; prefer a calendar comment when the installed capability supports it, otherwise use the source chat after loading dingtalk-chat. A resolvable factual question is a Consumer proposal, never needs_human.

Do not ask broad questions such as whether the principal should attend. Ask for the missing fact, such as the decision to make, the input expected, or the specific referenced material.

Silent Review

For a silent meeting or asynchronous review, read and process every linked material and produce the requested review outcome; do not merely accept the invitation. Use the linked material's dingtalk-doc or dingtalk-drive workflow. If the event references material but provides no readable material, ask for that exact material.

Audit B

Before execution, Audit B rereads the live event state and the applicable Skills. Suppress only an already-applied exact response or an already-sent exact clarification. A different response or corrected question is new work and requires the normal review, execution, and live verification.

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.