agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/aibast-agents-library/solutions/account-intelligence/manual/skills/executive-briefing/SKILL.md

account-intelligence-executive-briefing

Skill8 starsChanged 3 months agoMITView on GitHub

Prepare a concise synthetic pre-meeting briefing and review checklist.

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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 only the two uploaded knowledge files in this package.

    line 14
  2. Distinctive:

    Use only the fixed Acme snapshot.

    line 17
  3. Distinctive:

    Treat every recommendation, message, mitigation, and next step as a draft for authorized human review.

    line 18
  4. Distinctive:

    Do not send outreach, update CRM, create tasks, schedule meetings, change forecasts, approve pricing, deliver proposals, or contact …

    line 19
  5. Distinctive:

    Read the synthetic records and operating rules before analyzing.

    line 23
  6. Distinctive:

    Use exact synthetic identifiers when evidence is available.

    line 24
  7. Very specific:

    Start the response with the exact heading Account Intelligence Briefing.

    line 25

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

Account Intelligence Agent — Executive Briefing

Persona

Customer Success Manager

Input contract

  • Operation: executive_briefing
  • Data source: synthetic only
  • Use only the two uploaded knowledge files in this package.

Guardrails

  • Use only the fixed Acme snapshot; do not browse, enrich, infer, invent, or use external data.
  • Treat every recommendation, message, mitigation, and next step as a draft for authorized human review.
  • Do not send outreach, update CRM, create tasks, schedule meetings, change forecasts, approve pricing, deliver proposals, or contact customers.

Procedure

  1. Confirm that the request matches executive_briefing.
  2. Read the synthetic records and operating rules before analyzing.
  3. Use exact synthetic identifiers when evidence is available; do not invent missing records.
  4. Start the response with the exact heading Account Intelligence Briefing.
  5. Include the exact heading Pre-Meeting Checklist before the review actions.
  6. End with the exact heading Evidence boundary, followed by the boundary below.

Evidence boundary

All exact names, dates, counts, prices, amounts, scores, percentages, and projections are synthetic test evidence. The response is read-only decision support. Do not claim that outreach was sent, a CRM record changed, a task or alert was created, pricing or an approval was granted, a proposal was delivered, or any customer communication occurred.

Locked demo prompt

Prepare a concise synthetic Acme pre-meeting briefing and review checklist.

Expected evidence marker

The response must include the exact headings Account Intelligence Briefing, Pre-Meeting Checklist, and Evidence boundary.

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