Decision topic

Manage knowledge, meetings, and project context

Pick by source: meeting notes, personal knowledge, project instructions, support tickets, or team workspace memory.

Last meaningful review July 21, 2026

Start here

You need knowledge turned into decisions, memory, or reusable context without confusing personal notes, project rules, and customer records.

This topic coversmeeting notes · action items · personal knowledge bases · project context · support-ticket synthesis

Not this topicsecret storage · guaranteed autonomous memory · customer decisions without review

Choose your scene

Pick the closest situation, not the perfect one.

Each scene hides the noisy marketplace ranking behind one practical recommendation, one optional alternative, and one fallback when a public skill is not the right intervention.

I need meeting notes turned into decisions and action items.

I have notes or a transcript and need decisions, owners, dates, and follow-up.

Decision moment

Choose meeting intelligence over generic summarization.

Not this

If you need audio transcription itself, use a transcription skill first.

Recommended skillSource

notion-meeting-intelligence

It fits meeting intelligence and structured follow-up in a workspace.

Use when: Use it when Notion is the knowledge destination.
Avoid when: Avoid it when the source is not meeting material.
Signal: OpenAI curated skill source.

Recommended skillSource

lark-workflow-meeting-summary

It is a high-install meeting workflow in the Lark/Feishu ecosystem.

Use when: Use it for Lark/Feishu meeting summaries.
Avoid when: Avoid it outside that workspace.
Signal: skills.sh all-time: 441,145 installs in open.feishu.cn source.

No skill

Consent and privacy check

Confirm recording and sharing permissions.

Use when: Use it before processing sensitive meetings.
Avoid when: Do not summarize unauthorized recordings.
Signal: Meetings can contain private or regulated information.

I need to organize personal notes or a knowledge base.

I have scattered notes, files, or links and want a structure I can maintain.

Decision moment

Choose knowledge capture and organization, not project policy.

Not this

If the knowledge is agent project rules, use project context.

Recommended skillSource

notion-knowledge-capture

It is a direct fit for capturing and structuring knowledge in Notion.

Use when: Use it for personal or team Notion knowledge bases.
Avoid when: Avoid it for local Obsidian-only vaults.
Signal: OpenAI curated skill source.

Recommended skillSource

firecrawl-knowledge-ingest

It fits turning web or document sources into reusable knowledge.

Use when: Use it when source ingestion is the main job.
Avoid when: Avoid it for private notes without access controls.
Signal: skills.sh all-time: 29,141 installs; official Firecrawl workflow source.

Adapt

Knowledge taxonomy first

Define projects, topics, archive rules, and retrieval goals.

Use when: Use it before large imports.
Avoid when: Do not import everything into an unusable structure.
Signal: A skill can organize, but it needs stable buckets.

I need better project instructions or agent memory.

The agent keeps forgetting project rules or mixing local context with general knowledge.

Decision moment

Choose project context governance over personal knowledge management.

Not this

If this is a personal note system, use personal knowledge.

Recommended skillSource

define-goal

It helps set durable working objectives and context boundaries before agent work.

Use when: Use it for scoped project goals and handoffs.
Avoid when: Avoid it as a magic long-term memory system.
Signal: OpenAI curated skill source.

Recommended skillSource

self-improving-agent

It is relevant when project learnings should feed back into durable agent behavior.

Use when: Use it for recurring project learning loops.
Avoid when: Avoid it for secrets or private credentials.
Signal: skills.sh all-time: 32,105 installs.

Build

Project instruction file

Create or revise AGENTS.md/CLAUDE.md/project docs.

Use when: Use it for durable team instructions.
Avoid when: Do not rely on hidden chat memory for policy.
Signal: Local rules should live in the repository, not only in a public skill.

I need support tickets summarized into reusable knowledge.

I have customer conversations and want recurring issues, gaps, or FAQ drafts.

Decision moment

Choose support synthesis with privacy and review boundaries.

Not this

If you need to send customer replies automatically, this scene is not enough.

Recommended skillSource

firecrawl-knowledge-base

It fits turning repeated source material into knowledge-base output.

Use when: Use it for issue clustering and knowledge-base drafts.
Avoid when: Avoid it for autonomous compensation or policy decisions.
Signal: skills.sh all-time: 29,332 installs.

Recommended skillSource

notion-research-documentation

It fits writing structured internal docs from gathered evidence.

Use when: Use it when Notion is the review destination.
Avoid when: Avoid it for live customer response automation.
Signal: OpenAI curated skill source.

No skill

Human support approval

Route drafts through support owners before publishing.

Use when: Use it for customer-impacting content.
Avoid when: Do not send replies without review.
Signal: Customer-facing conclusions can affect trust and policy.

Why this topic exists

skills.sh shows Lark meeting/workflow skills, Notion curated skills, and knowledge-base workflows; OpenAI curated skills include Notion knowledge capture and meeting intelligence.

skills.sh: lark-minutes and lark-workflow-meeting-summary appear as high-install workplace skills.
OpenAI curated skills include notion-knowledge-capture and notion-meeting-intelligence.
Firecrawl knowledge-base workflows appear in skills.sh install data.

Still unsure?

Describe the job in your own words.

Request a topic or scene ↗