AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

notion-knowledge-capture

Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.

Original source
openai
License
MIT
Pinned revision
49f948faa9258a0c61caceaf225e179651397431

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read openai--notion-knowledge-capture at revision 49f948faa9258a0c61caceaf225e179651397431, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 13

reference/how-to-guide-database.md

How-To Guide Database

Purpose: Procedural documentation for common tasks.

Schema

| Property | Type | Options | Purpose | |----------|------|---------|---------| | Title | title | - | "How to [Task]" | | Complexity | select | Beginner, Intermediate, Advanced | Skill level required | | Time Required | number | - | Estimated minutes to complete | | Prerequisites | relation | Links to other guides | Required knowledge | | Category | select | Development, Deployment, Testing, Tools | Task category | | Last Tested | date | - | When procedure was verified | | Tags | multi_select | - | Technology/tool tags |

Usage

Create how-to guides with properties:
{
  "Title": "How to Set Up Local Development Environment",
  "Complexity": "Beginner",
  "Time Required": 30,
  "Category": "Development",
  "Last Tested": "2025-10-01",
  "Tags": "setup, environment, docker"
}

Best Practices

  1. Use consistent naming: Always start with "How to..."
  2. Test procedures: Verify steps work before publishing
  3. Include time estimates: Help users plan their time
  4. Link prerequisites: Make dependencies clear
  5. Update regularly: Re-test procedures when tools/systems change