Skip to content
Back to skills

Learning Database

ASecurity

Imported skill learning_database from openai

  • 3 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 11, 2026
researchgodatabase

Security analysis

A100/100

Scanned September 11, 2026

npx -y skills add bitwikiorg/skills.md --skill learning_database --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Learning Database?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Learning Database
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bitwikiorg-learning-database/badge)](https://www.skillsdirectory.com/skills/bitwikiorg-learning-database)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
description: Imported skill learning_database from openai
name: learning_database
signature: 8ceaa72bc7ab944ce1084df6233001c05b65d06ee5913a23caf760f248236e83
source: /a0/tmp/skills_research/openai/skills/.curated/notion-knowledge-capture/reference/learning-database.md
---

# Learning/Post-Mortem Database

**Purpose**: Capture learnings from incidents, projects, or experiences.

## Schema

| Property | Type | Options | Purpose |
|----------|------|---------|---------|
| **Title** | title | - | Event or project name |
| **Date** | date | - | When it happened |
| **Type** | select | Incident, Project, Experiment, Retrospective | Learning type |
| **Severity** | select | Critical, Major, Minor | Impact level (for incidents) |
| **Team** | people | - | Who was involved |
| **Key Learnings** | number | - | Count of learnings |
| **Action Items** | relation | Links to tasks | Follow-up actions |

## Content Template

Each learning page should include:
- **What Happened**: Situation description
- **What Went Well**: Success factors
- **What Didn't Go Well**: Problems encountered
- **Root Causes**: Why things happened
- **Learnings**: Key takeaways
- **Action Items**: Improvements to implement

## Best Practices

1. **Blameless approach**: Focus on systems and processes, not individuals
2. **Document quickly**: Capture while memory is fresh
3. **Identify root causes**: Go beyond surface-level problems
4. **Create action items**: Turn learnings into improvements
5. **Follow up**: Track that action items are completed
6. **Share widely**: Make learnings accessible to entire team

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…