agentleFS
Sign inStart free
ailessonioailessonio/open-source-skills/skills/openai/notion-research-documentation/SKILL.md

notion-research-documentation

Skill0 starsChanged 2 months agoMITView on GitHub

Research across Notion and synthesize into structured documentation; use when gathering info from multiple Notion sources to produce briefs, comparisons, or reports with citations.

19 other projects use a version of this, 6 of them edited.

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

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add the Notion MCP:

    line 21
  2. Distinctive:

    After successful login, the user will have to restart codex.

    line 28
  3. Very specific:

    Search first (Notion:notion-search).

    line 31
  4. Distinctive:

    Keep user goal in view (decision, summary, plan, recommendation).

    line 45
  5. Very specific:

    Create the page with Notion:notion-create-pages.

    line 49
  6. Distinctive:

    Add citations inline and a references section.

    line 50
  7. Distinctive:

    Add highlights, risks, and open questions.

    line 53
  8. Distinctive:

    If the user needs follow-ups, create tasks or a checklist in the page.

    line 54

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

Research & Documentation

Pull relevant Notion pages, synthesize findings, and publish clear briefs or reports (with citations and links to sources).

Quick start

  1. Find sources with Notion:notion-search using targeted queries; confirm scope with the user.
  2. Fetch pages via Notion:notion-fetch; note key sections and capture citations (reference/citations.md).
  3. Choose output format (brief, summary, comparison, comprehensive report) using reference/format-selection-guide.md.
  4. Draft in Notion with Notion:notion-create-pages using the matching template (quick, summary, comparison, comprehensive).
  5. Link sources and add a references/citations section; update as new info arrives with Notion:notion-update-page.

Workflow

0) If any MCP call fails because Notion MCP is not connected, pause and set it up:

  1. Add the Notion MCP:
    • codex mcp add notion --url https://mcp.notion.com/mcp
  2. Enable remote MCP client:
    • Set [features].rmcp_client = true in config.toml or run codex --enable rmcp_client
  3. Log in with OAuth:
    • codex mcp login notion

After successful login, the user will have to restart codex. You should finish your answer and tell them so when they try again they can continue with Step 1.

1) Gather sources

  • Search first (Notion:notion-search); refine queries, and ask the user to confirm if multiple results appear.
  • Fetch relevant pages (Notion:notion-fetch), skim for facts, metrics, claims, constraints, and dates.
  • Track each source URL/ID for later citation; prefer direct quotes for critical facts.

2) Select the format

  • Quick readout → quick brief.
  • Single-topic dive → research summary.
  • Option tradeoffs → comparison.
  • Deep dive / exec-ready → comprehensive report.
  • See reference/format-selection-guide.md for when to pick each.

3) Synthesize

  • Outline before writing; group findings by themes/questions.
  • Note evidence with source IDs; flag gaps or contradictions.
  • Keep user goal in view (decision, summary, plan, recommendation).

4) Create the doc

  • Pick the matching template in reference/ (brief, summary, comparison, comprehensive) and adapt it.
  • Create the page with Notion:notion-create-pages; include title, summary, key findings, supporting evidence, and recommendations/next steps when relevant.
  • Add citations inline and a references section; link back to source pages.

5) Finalize & handoff

  • Add highlights, risks, and open questions.
  • If the user needs follow-ups, create tasks or a checklist in the page; link any task database entries if applicable.
  • Share a short changelog or status using Notion:notion-update-page when updating.

References and examples

  • reference/ — search tactics, format selection, templates, and citation rules (e.g., advanced-search.md, format-selection-guide.md, research-summary-template.md, comparison-template.md, citations.md).
  • examples/ — end-to-end walkthroughs (e.g., competitor-analysis.md, technical-investigation.md, market-research.md, trip-planning.md).

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