Index of every page on this site: llms.txt
All skills
makenotion avatar

/knowledge-capture

@016c74f official
Run it yourself

Captures conversations and supplied notes as Notion wiki pages, how-to guides, FAQs, decision records, or retrospectives. Use when saving or updating durable knowledge from existing context; use research-documentation when new source discovery and synthesis is the main task.

  • 18 files
  • 50.2 KB
  • Updated 2 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/makenotion/claude-code-notion-plugin/knowledge-capture

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencedecision-log-database.md

≈647 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Decision Log Database (ADR - Architecture Decision Records)

Purpose: Track important decisions with context and rationale.

Schema

Property Type Options Purpose
Decision title - What was decided
Date date - When decision was made
Status select Proposed, Accepted, Superseded, Deprecated Current decision status
Domain select Architecture, Product, Business, Design, Operations Decision category
Impact select High, Medium, Low Expected impact level
Deciders people - Who made the decision
Stakeholders people - Who's affected by decision
Related Decisions relation Links to other decisions Context and dependencies

Usage

Create decision records with properties:
{
  "Decision": "Use PostgreSQL for Primary Database",
  "Date": "2025-10-15",
  "Status": "Accepted",
  "Domain": "Architecture",
  "Impact": "High",
  "Deciders": [tech_lead, architect],
  "Stakeholders": [eng_team]
}

Content Template

Each decision page should include:

  • Context: Why this decision was needed
  • Decision: What was decided
  • Rationale: Why this option was chosen
  • Options Considered: Alternatives and trade-offs
  • Consequences: Expected outcomes (positive and negative)
  • Implementation: How decision will be executed

Views

Recent Decisions: Sort by Date descending Active Decisions: Filter where Status = "Accepted" By Domain: Group by Domain High Impact: Filter where Impact = "High" Pending: Filter where Status = "Proposed"

Best Practices

  1. Document immediately: Record decisions when made, while context is fresh
  2. Include alternatives: Show what was considered and why it wasn't chosen
  3. Track superseded decisions: Update status when decisions change
  4. Link related decisions: Use relations to show dependencies
  5. Review periodically: Check if old decisions are still valid

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 016c74f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 2 weeks ago

README badge

README badge for makenotion/claude-code-notion-plugin/knowledge-capture