Claude Skills for Notion: Turn Notes Into Reviewed Work

Claude skills for Notion are saved prompt instructions that extract action items from meeting notes, review a page for completeness, and turn rough notes into structured tasks. The output is only useful if someone reviews and approves it. These skills make the review faster and more consistent.

Tools like fenbs hold the agreed tasks and decisions after the review. A note reviewed with Claude and then filed in a Notion page is useful in Notion. A note whose agreed actions are also in fenbs is available to any connected assistant, regardless of which AI app picks up the work next.

Why Notion notes often need a skill to become actions

Meeting notes in Notion collect what was said, not what was decided. "We should look into X" is not the same as "Sarah will review X by Friday." A skill that applies that distinction consistently catches the difference every time, not just when the reviewer has time to read carefully.

Reference pages have a different problem: completeness. A product spec that is missing the success criteria or an SOP missing the escalation path is technically present in Notion but functionally incomplete. A review skill checks the structure before the page is shared or referenced in work.

A skill for extracting action items from meeting notes

This skill reads a set of meeting notes and produces a structured list of actions, each with an owner, a description, and a due date if one was mentioned. It flags items that sound like actions but lack a clear owner or date.

Extract action items from the following meeting notes.

Meeting notes:
{{paste the notes}}

For each action item found, output:
  Owner: [person's name or "Unassigned"]
  Action: [one sentence, starts with a verb]
  Due: [date mentioned, or "Not stated"]
  Source: [quote the exact line from the notes that produced this action]

After the list:
  Flagged items (sound like actions but have no clear owner or commitment):
  - [quote each]

  Decisions made in this meeting (not actions, but things agreed):
  - [list each]

  Items needing clarification before work starts:
  - [list each]

Do not infer owners, dates, or commitments that are not in the notes.

The "Source" field is important: it links each action to the specific sentence in the notes that produced it. That link lets the reviewer check whether the action is what was actually said, rather than what Claude interpreted.

A skill for reviewing a Notion page for completeness

A completeness review skill checks a Notion page against a structure you define. Adjust the checklist to match the type of page: a project brief needs different sections than a meeting note or an SOP.

Review the following Notion page for completeness.

Page type: {{e.g., project brief, meeting notes, SOP, product spec, decision record}}
Page content:
{{paste the page text}}

Check each section and mark Present and clear | Present but vague | Missing:

For a project brief:
- [ ] Goal: what success looks like
- [ ] Scope: what is included and what is not
- [ ] Owner: who is accountable
- [ ] Timeline: key dates or milestones
- [ ] Success criteria: how you will know it worked
- [ ] Open questions: what is not yet decided

For a meeting notes page, replace the above with:
- [ ] Attendees
- [ ] Decisions made
- [ ] Actions with owners and due dates
- [ ] Items deferred to a later meeting

For an SOP, replace with:
- [ ] Trigger: when to run this process
- [ ] Steps: numbered, each starting with a verb
- [ ] Decision points: what to do if a step fails
- [ ] Escalation: who to contact if the process cannot complete
- [ ] Owner: who maintains this document

For each "Present but vague" or "Missing": write one sentence on what is needed.
End with: Ready to share: Yes | No | With additions.

Keeping agreed tasks usable across assistants

A Notion page is readable by anyone with access to that workspace. An assistant connected to Notion via MCP can also read it. But the actions agreed in a meeting note, the decisions made, and the next steps for each task are more useful when they live in a structured task record than when they are buried in a page.

After running the extraction skill and reviewing the output, add the agreed actions as tasks in fenbs. Link each task to the Notion source page. If the meeting produced decisions, record those in Decisions and rules. The next session on that work reads the task and the decision without opening the original notes.

When Notion notes and fenbs tasks work together

Notion and fenbs serve different purposes. Notion holds documents: meeting notes, project briefs, SOPs, and reference material that benefits from rich formatting and easy linking. fenbs holds active work: the tasks that came out of those documents, the decisions that constrain them, and the progress notes that carry work between sessions.

The skills here are the bridge. Run the extraction skill on a set of meeting notes, review the output, and move the agreed tasks into fenbs. Link each task to its source page. From that point, the Notion page is the record of what was said and fenbs is the record of what is being done about it.

This separation also makes it easier to archive old notes. When a Notion page is no longer actively referenced, archiving it does not lose the work it produced. The tasks it generated are still in fenbs, linked to the archived page if the original context is ever needed. The active work does not depend on the notes remaining in the working Notion space. This is one of the practical benefits of keeping the record of what is being done in a different place from the record of what was said. Clean archives and an active task list are both easier to maintain when they are separate tools built specifically for each of those two different jobs.

How to do this with fenbs

1. Create a free account and add a project for the work these Notion notes belong to.
2. Add each skill to Skills and prompts: "Extract actions from meeting notes", "Review Notion page for completeness".
3. After a meeting, paste the notes into Claude, run the extraction skill, and review the output.
4. Add the agreed actions as tasks in fenbs. Link to the Notion page in Links and listings.
5. Connect Claude over MCP from Integrations. At the start of the next session, ask Claude to read the tasks and the decisions from that project.

For setting up Notion with Claude Code, see Notion MCP and Claude Code. For general skill patterns, see Claude skills examples. The claude skills marketplace and claude skills files cover importing and sharing skill templates.