6DuckLearn Skills

pkm synthesis

Use for turning saved notes, research, memory, and prior decisions into a clear synthesis with themes, contradictions, carry-forward insights, and next actions.

knowledge-management Tags: pkm, synthesis, notes, research, memory, decision-support, codex-workflow

PKM Synthesis

Use this skill when accumulated notes, saved articles, meeting memory, or prior decisions need to become a clear decision memo or next-action brief.

This is a curated, model-agnostic skill template. It helps Codex or another LLM runtime synthesize information, but it should not pretend thin notes are strong evidence.

Problem This Skill Solves

Personal knowledge systems often collect more context than a person can use. The hard part is not storing more notes. The hard part is finding what changed, what conflicts, and what should carry forward.

This skill turns noisy knowledge into a focused synthesis that supports a current question.

Inputs

  • Synthesis question
  • Source notes, links, transcripts, or memories
  • Time window or project boundary
  • Decision that the synthesis should support
  • Known conflicts, uncertainty, or stale information

Step-by-Step Onboarding Guide

  1. Start with one synthesis question.
  2. Paste only the notes, links, or memories that may answer that question.
  3. Ask Codex to cluster the material by theme.
  4. Ask it to identify contradictions, stale assumptions, and changed beliefs.
  5. Require evidence labels: direct source, memory-derived, inference, or open question.
  6. Convert the synthesis into a decision memo, learning note, or next-action checklist.
  7. Save only the carry-forward insight, not the full transcript dump.

Example Use Case

Target user: a founder or product operator with many AI/RSS notes and daily growth drafts.

Workflow:

  1. Export the last week of notes, draft posts, and article summaries.
  2. Use this skill to answer: "What themes should shape next week's product marketing?"
  3. Ask Codex to separate repeated signals from one-off noise.
  4. Ask for contradictions, risks, and what evidence is still missing.
  5. Turn the result into a short planning memo.

Expected artifact: a synthesis memo with themes, evidence, contradictions, carry-forward insights, and next actions.

Workflow

  1. Define the synthesis question.
  2. Gather only the relevant notes and memory.
  3. Cluster recurring themes.
  4. Identify contradictions, drift, and changed beliefs.
  5. Extract what should carry forward into the next decision.
  6. End with clear questions, actions, or thesis updates.

Output Contract

Return:

  • synthesis question
  • source set used
  • top themes
  • contradictions or drift
  • evidence labels
  • carry-forward insight
  • unresolved questions
  • next actions

Guardrails

  • Do not turn weak notes into false certainty.
  • Do not flatten meaningful disagreement across time.
  • Do not summarize everything when a few patterns matter most.
  • If the notes are thin, noisy, or stale, say so.
  • Separate what the sources say from what you infer.

Related skills

  • gemini market research competitive intel — Use Gemini Deep Research for competitive analysis, audience persona profiling, A/B test ad copy, and SEM keyword generation
  • domain product research — Use for product, company, competitor, and moat research grounded in 6DuckLearn data, local memory, and explicit evidence lanes.
  • go to market — Use for product launches, PR angles, campaign calendars, and approval-gated marketing drafts across online channels for software or physical products.
  • interview script — Create a structured customer interview script with JTBD probing questions, warm-up, core exploration, and wrap-up sections. Follows The Mom Test principles — no leading questions, no pitching, focus on past behavior. Use when preparing for user interviews, creating interview guides, or planning discovery research.