agentleFS
Sign inStart free
hebertzhuhebertzhu/agent-foundry/skills/notion-meeting-intelligence/SKILL.md

notion-meeting-intelligence

Skill0 starsChanged 8 months agoMITView on GitHub

Use when the user wants to prepare agendas, pre-reads, or decision notes from Notion context; gather prior docs first, tailor the structure to the meeting type, and create a page that is ready to share.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-deep-links, helium-mcp and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ComposioHQSkill

    agent-deep-links

    Build, validate, and troubleshoot deep links for Codex, Cursor, VS Code, Visual Studio, and similar tools. Use when users ask for clickable links (especially in Slack) that open threads, files, folders, or app settings.

    Also in 3 projects that use this

  • ComposioHQSkill

    helium-mcp

    Search real-time news with bias scoring, get live stock/ETF/crypto data with AI analysis, ML options pricing, balanced news synthesis, and meme search via the Helium MCP server.

    Also in 3 projects that use this

  • petestewartSkill

    datadog-logs

    Query Datadog logs via the Logs Search API v2. Use when the user asks to "check the logs", "search logs", "find errors in Datadog", "look up logs for", "show me production logs", "check for errors", "search Datadog", or any request involving log search, error investigation, or production debugging that requires Datadog log data.

    Also in 3 projects that use this

  • MicrosoftSkill

    deploy-pipeline

    Triggers a Power Platform Pipeline deployment run for a Power Pages solution. Selects a target stage, validates the package, optionally configures deployment settings (environment variables, connection references), then deploys and polls for completion. Use when asked to: "deploy pipeline", "run pipeline", "trigger deployment", "deploy to staging", "deploy to production", "run power platform pipeline", "deploy solution via pipeline", "promote solution", "push to staging", "push to production".

    Also in 3 projects that use this

  • ArogyaReddySkill

    raffle-winner-picker

    Picks random winners from lists, spreadsheets, or Google Sheets for giveaways, raffles, and contests. Ensures fair, unbiased selection with transparency.

    Also in 5 projects that use this

  • +7 more from ComposioHQ

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 5

    Distinctive

    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 for meeting prep, agenda building, pre-read drafting, follow-up notes, and decision-oriented meeting documents in Notion.

    line 9
  2. Distinctive:

    Add follow-up actions or unresolved questions so the page remains useful after the meeting, not just before it.

    line 16
  3. Distinctive:

    Keep outputs concise, decision-ready, and friendly to async readers.

    line 20
  4. Distinctive:

    Do not generate a generic agenda when the meeting outcome is still unclear.

    line 23
  5. Distinctive:

    Do not omit prior decisions or blockers that materially change what the meeting should cover.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “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

Notion Meeting Intelligence

Intent

  • Use for meeting prep, agenda building, pre-read drafting, follow-up notes, and decision-oriented meeting documents in Notion.

Default operating pattern

  1. Confirm the meeting goal, attendees, decisions needed, and any time or owner constraints.
  2. Pull the most relevant prior context from Notion before drafting: specs, prior notes, action items, decisions, and open risks.
  3. Choose the format that matches the meeting: status review, planning, decision, retro, 1:1, or brainstorming.
  4. Build a shareable page with agenda items, timeboxes, owners, linked context, and explicit expected outcomes.
  5. Add follow-up actions or unresolved questions so the page remains useful after the meeting, not just before it.

Pack fit

  • Included in: knowledge-ops
  • Keep outputs concise, decision-ready, and friendly to async readers.

Boundary

  • Do not generate a generic agenda when the meeting outcome is still unclear.
  • Do not omit prior decisions or blockers that materially change what the meeting should cover.

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