agentleFS
Sign inStart free
hebertzhuhebertzhu/agent-foundry/skills/notion-knowledge-capture/SKILL.md

notion-knowledge-capture

Skill0 starsChanged 8 months agoMITView on GitHub

Use when the user wants to turn chats, decisions, notes, or learnings into structured Notion pages; search existing context first, choose the right destination, then create or update pages with links, owners, and reusable structure.

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use meeting-notes-and-actions, pr-review-ci-fix 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

    meeting-notes-and-actions

    Turn meeting transcripts or rough notes into crisp summaries with decisions, risks, and owner-tagged action items; use for Zoom/Meet/Teams transcripts, call notes, or long meeting chats to generate share-ready outputs.

    Also in 4 projects that use this

  • ComposioHQSkill

    pr-review-ci-fix

    Automated PR review and CI auto-fix for GitHub and GitLab using the Composio CLI. Pulls diffs, fetches failing job logs, posts review comments, and loops fix commits until checks go green.

    Also in 4 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

  • +8 more from ComposioHQ

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 6

    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 capturing conversations, decisions, FAQs, how-tos, wiki pages, and reusable internal knowledge in Notion.

    line 9
  2. Distinctive:

    Use the current host's Notion connector or MCP integration to search for existing related pages before creating duplicates.

    line 13
  3. Distinctive:

    Create or update the page, then link it back to the most relevant hub pages, specs, or tasks.

    line 16
  4. Distinctive:

    Prefer durable, linkable knowledge over raw meeting notes or chat transcripts.

    line 20
  5. Distinctive:

    Do not create duplicate documentation if an existing page only needs an update.

    line 23
  6. Distinctive:

    Do not flatten nuanced decisions into a vague summary.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 18 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 Knowledge Capture

Intent

  • Use for capturing conversations, decisions, FAQs, how-tos, wiki pages, and reusable internal knowledge in Notion.

Default operating pattern

  1. Clarify what is being captured, who the audience is, and whether this should create a new page or update an existing one.
  2. Use the current host's Notion connector or MCP integration to search for existing related pages before creating duplicates.
  3. Pick the right destination: wiki page, documentation database, decision log, FAQ collection, or learning archive.
  4. Structure the content so future readers can reuse it quickly: summary, context, decisions, links, owners, and follow-up items.
  5. Create or update the page, then link it back to the most relevant hub pages, specs, or tasks.

Pack fit

  • Included in: knowledge-ops
  • Prefer durable, linkable knowledge over raw meeting notes or chat transcripts.

Boundary

  • Do not create duplicate documentation if an existing page only needs an update.
  • Do not flatten nuanced decisions into a vague summary; preserve rationale and open questions.

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