notion_synthesize
Synthesize durable ktx wiki pages and semantic-layer sources from staged Notion pages, databases, data-source rows, and clustered Notion evidence. Load when a WorkUnit contains Notion raw files or Notion evidence chunks.
Install / Use
npx skills add Kaelio/ktx --skill notion_synthesizeInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AI & Machine LearningSupported Platforms
Our assessment of notion_synthesize
notion_synthesize scores 89/100 on our quality scale, 416th of 950 AI & Machine Learning skills we index (top 44%).
Its SKILL.md is 7.8 KB long, well organised into 10 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 1,601 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so notion_synthesize is actively maintained.
- Our last check on 2026-10-31 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
notion_synthesize compared with similar skills
All 4 of these similar skills score higher than notion_synthesize; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| notion_synthesize (this skill)by Kaelio | 89 | 1.6k | 2mo ago | SKILL.md |
| claude-memby thedotmack | 100 | 117.6k | today | CLAUDE.md |
| Understand-Anythingby Egonex-AI | 100 | 92.8k | 1d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| CowAgentby zhayujie | 100 | 48.0k | today | CLAUDE.md |
Frequently asked questions
- How do I install notion_synthesize?
- Run
npx skills add Kaelio/ktx --skill notion_synthesize. The install tabs above show the steps for each supported agent. - Which AI agents does notion_synthesize work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is notion_synthesize safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is notion_synthesize still maintained?
- The repository was last updated about 2 months ago, so notion_synthesize is actively maintained.
Skill content
View source on GitHubname: notion_synthesize description: Synthesize durable ktx wiki pages and semantic-layer sources from staged Notion pages, databases, data-source rows, and clustered Notion evidence. Load when a WorkUnit contains Notion raw files or Notion evidence chunks. callers: [memory_agent]
Notion Cluster Synthesis
Use this skill when a WorkUnit contains staged Notion content from pages/**, databases/**, data-sources/**, or clustered Notion evidence.
Role
Each WorkUnit is either a single Notion page/span or a topical cluster of related Notion pages, pre-grouped by embedding similarity. Read the assigned raw files, then write a small set of durable wiki entries and, when applicable, semantic-layer sources that synthesize the WorkUnit's knowledge. Write final memory directly; do not write candidates.
Required Workflow
- Read the WorkUnit notes and rawFiles list. Page content lives in
page.md;metadata.jsonholds title, path, object type, data-source ids, last edited metadata, and properties. - For each assigned page, call
read_raw_file, orread_raw_spanfor oversized pages when the notes specify a span. - Search
wiki_searchfor existing pages that overlap the WorkUnit topics. Prefer updating an existing page over creating a duplicate. - Use
context_evidence_search,context_evidence_read, andcontext_evidence_neighborsto pull supporting chunks when indexed evidence is relevant. PasschunkIdanddocumentIdvalues verbatim as returned by the evidence tools. - Write durable business knowledge with
wiki_write. Aim for a small number of high-quality pages per WorkUnit or cluster. IncluderawPathswith the exact Notion raw files that support each page. - When the Notion content defines a reusable dataset, metric, segment, join rule, source-of-truth mapping, or table with explicit columns, load
sl_capture, discover existing sources first withsl_discoverorsl_read_source, then usesl_write_sourceorsl_edit_sourceonly for a confirmed mapped non-Notion target source. IncluderawPathswith the exact Notion raw files that support the SL action. If no mapped target exists, callemit_unmapped_fallbackand keep the content wiki-only. - For every deleted raw path in the Eviction Set, call
eviction_list, decide retention, thenemit_eviction_decision. Do this even when no wiki write is needed.
What To Capture
Capture durable, reusable company knowledge:
- metric definitions, KPI formulas, named business concepts, and reusable filters
- workflows, policies, ownership rules, approval conventions, and source-of-truth mappings
- data-source row pages that describe tables, columns, semantic models, dashboards, or business entities
- cross-system aliases connecting Notion terms to warehouse, dbt, Looker, Metabase, or MetricFlow names
- caveats, conflicts, supersession notes, and customer/product assumptions affecting future analysis
Skip noisy or transient content:
- meeting notes with no reusable rule
- task lists, project status updates, and time-bounded snapshots
- duplicate docs with no new fact
- database metadata pages when row pages contain the actual business content
- transient announcements and long page summaries
Quality
Prefer fewer, stronger entries. Every wiki entry must cite at least one Notion page or row using its path and last edited date when available. When evidence conflicts, write a conflict note inside the wiki page rather than choosing silently.
If a clustered WorkUnit includes several related pages, synthesize the shared rule or concept instead of writing one thin page per source. For oversized page spans, read only the assigned span unless the WorkUnit explicitly asks for neighboring context.
Search existing wiki pages for the same tables: or sl_refs: frontmatter and for source-of-truth aliases before creating a new page. If an existing page already documents the same warehouse object or business concept, update it instead of creating a differently named duplicate.
Citation Style
## Revenue Recognition
- Booked revenue excludes refunds and test accounts.
- Source: Notion - Company Handbook / Finance / Revenue Recognition, last edited 2026-04-12.
- Conflict note: An older Sales Ops page uses gross revenue before refunds; treat the Finance Handbook as current unless Finance says otherwise.
Semantic-Layer Rules
- Load
sl_capturebefore writing or editing SL sources. - Discover existing sources first with
sl_discover; read existing source YAML before editing. - Prefer overlays on manifest-backed sources over standalone SQL.
- If Notion describes a dashboard or metric but does not define executable logic, write a wiki page and attach
sl_refsonly after confirming the referenced source exists. - Notion
dataSourceCountcounts Notion databases/data sources only. It does not prove that a warehouse/dbt table has or lacks a mapped semantic-layer source. - Do not create SL sources under the Notion connection just because a page mentions a warehouse, dbt, Looker, or Metabase object. Use the mapped warehouse/source connection after discovery, or emit an unmapped fallback and write wiki-only.
- Distinguish fallback reasons precisely: if a non-Notion warehouse/dbt connection exists but
sl_discovercannot find the named table/source, useno_physical_table; reserveno_connection_mappingfor cases where there is no plausible non-Notion target connection at all. - If
sl_discoverresolves the table/source, do not callemit_unmapped_fallbackfor that table. Use the resolved source forsl_refs, overlay edits, or wiki-only documentation. - When calling
emit_unmapped_fallback, pass the table or source identifier astableRef(e.g.tableRef: "<schema>.<table>") - the tool generates the canonical detail string from the reason code andtableRef. Use the optionalclarificationfield only to add context that does not contradict the reason. Do not restate the reason inclarification.
Identifier Verification Protocol
Before writing a wiki page or SL source on any topic:
discover_data({query: "<topic>"})- see what wikis, SL sources, and raw tables already exist. Prefer updating existing pages over creating new ones.
Before emitting any schema.table or schema.table.column into a wiki body,
SL source, tables: frontmatter, sl_refs, or emit_unmapped_fallback:
entity_details({connectionId, targets: [{display: "<identifier>"}]})- confirm the identifier resolves; inspect native types, FK/PK, and sampleValues.- For literal values from the source, such as status codes or plan tiers,
check whether they appear in
entity_detailssampleValues for the relevant column. If sampleValues is short or the sample may have missed real values, run asql_executionprobe with the same warehouse connection id:sql_execution({connectionId, sql: "SELECT DISTINCT <col> FROM <ref> LIMIT 50"}). - If the candidate identifier still does not resolve, do one of:
- Use
sql_execution({connectionId, sql: "SELECT 1 FROM <ref> LIMIT 0"}). If it errors, the identifier is fictional. - Wrap the identifier in
[unverified - from <rawPath>]in the wiki body, citing the exact raw path that mentioned it. - When recording
emit_unmapped_fallbackwithno_physical_table, include the failing probe error inclarification.
- Use
- Never copy
<schema>.<table>placeholder strings from these instructions into output.
Tools
Allowed: read_raw_file, read_raw_span, wiki_search, wiki_read, wiki_write, discover_data, entity_details, sql_execution, sl_discover, sl_read_source, sl_write_source, sl_edit_source, sl_validate, context_evidence_search, context_evidence_read, context_evidence_neighbors, emit_unmapped_fallback, eviction_list, emit_eviction_decision.
Not allowed: context_candidate_write, context_candidate_mark.
Related Skills
claude-mem
117.6kPersistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
Understand-Anything
92.8kGraphs that teach > graphs that impress. Turn any code into an interactive knowledge graph you can explore, search, and ask questions about. Works with Claude Code, Codex, Cursor, Copilot, Gemini CLI, and more.
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
CowAgent
48.0kOpen-source personal AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-agent, multi-model, multi-channel. Lightweight, extensible, one-line install.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
