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

examples/how-to-guide.md

Example: How-To Guide from Discussion

User Request: "Save our discussion about deploying to production as a how-to guide"

Workflow

1. Extract Content from Chat

From conversation, identified:

  • Deployment prerequisites
  • Step-by-step procedure
  • Common issues and solutions
  • Best practices and tips

2. Structure as How-To

Organized into:

  • Overview & prerequisites
  • Numbered deployment steps
  • Verification steps
  • Troubleshooting section
  • Related resources

3. Find Location

Notion:notion-search
query: "deployment documentation"

Found: Engineering Wiki → Deployment section

4. Create Guide

Notion:notion-create-pages
parent: { page_id: "deployment-section-id" }

Output

# How to Deploy to Production

## Overview
Production deployment using GitHub Actions with zero-downtime rolling updates.
**Time Required**: 15-20 minutes | **Complexity**: Intermediate

## Prerequisites
- [ ] PR approved and merged to main
- [ ] All CI tests passing
- [ ] Database migrations reviewed
- [ ] Feature flags configured

## Deployment Steps

1. **Verify main branch is ready**
   ```bash
   git checkout main && git pull
  1. Tag release

    git tag -a v1.2.3 -m "Release v1.2.3"
    git push origin v1.2.3
    
  2. Trigger deployment

    • GitHub Actions auto-starts from tag push
    • Monitor: https://github.com/org/repo/actions
  3. Database migrations (if needed)

    • Auto-run in GitHub Actions
    • Check logs for completion
  4. Verify deployment

    • Wait for health checks (2-3 min)
    • Test key endpoints
    • Check error rates in Datadog

Verification Checklist

  • [ ] All pods healthy in k8s dashboard
  • [ ] Error rate < 0.1% in last 10 min
  • [ ] Response time p95 < 500ms
  • [ ] Test login flow
  • [ ] Check Slack #alerts channel

Troubleshooting

Health checks failing → Check pod logs: kubectl logs -f deployment/api -n production

Migration errors → Rollback: Revert tag, migrations auto-rollback

High error rate → Emergency rollback: Previous tag auto-deploys via GitHub Actions

Best Practices

  • Deploy during low-traffic hours (2-4am PST)
  • Have 2 engineers available
  • Monitor for 30 min post-deploy
  • Update #engineering Slack with deploy notice

Related Docs

  • Rollback Procedure
  • Database Migration Guide

### 5. Make Discoverable

Notion:notion-update-page page_id: "engineering-wiki-homepage" command: "insert_content_after"

Added link in Engineering Wiki → How-To Guides section

## Key Success Factors
- Captured tribal knowledge from discussion
- Structured as actionable steps
- Included troubleshooting from experience
- Made discoverable by linking from wiki index
- Added metadata (time, complexity)