agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/aibast-agents-library/solutions/live-event-launch-planner/manual/skills/aibast_launch-summary_04/SKILL.md

launch-summary

Skill8 starsChanged 3 months agoMITView on GitHub

Use when someone asks what is late, missing, or blocked and who needs a reminder; returns reminder drafts that are never sent.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when someone asks what is late, missing, or blocked and who needs a reminder.

    line 7
  2. Distinctive:

    Use only the uploaded synthetic records and rules.

    line 11
  3. Very specific:

    Keep the figures, identifiers, and tables exactly as recorded for case LEL-04.

    line 13
  4. Distinctive:

    Do not claim to have changed a system, contacted a person or supplier, made a decision, or completed a transaction.

    line 25

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

Launch status summary

Use when someone asks what is late, missing, or blocked and who needs a reminder; returns reminder drafts that are never sent.

Procedure

  1. Use only the uploaded synthetic records and rules.
  2. Lead with the specific evidence that answers the persona's question.
  3. Keep the figures, identifiers, and tables exactly as recorded for case LEL-04.
  4. Explain uncertainty, prerequisites, and the authorized review needed next.
  5. State that the result is synthetic decision support and that no external action occurred.

Deterministic pilot evidence

  • Launch Summary
  • Submit final store assets
  • no reminder was sent

Safety gate

Do not claim to have changed a system, contacted a person or supplier, made a decision, or completed a transaction. Stop at a reviewable brief or draft.

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