note

Save structured notes anchored to tasks with validated content and PII scrubbing.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/kiran-capoor94/wizard --skill note-kiran-capoor94
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: note
Source: https://github.com/kiran-capoor94/wizard/tree/main/src/wizard/skills/note
Command: npx skills add https://github.com/kiran-capoor94/wizard --skill note-kiran-capoor94

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

You need to preserve findings, decisions, documentation, or learnings from investigations or debugging sessions, ensuring they stay accessible for future work.

Core Features & Use Cases

  • Save structured notes anchored to a task or session, including type like investigation, decision, docs, or learnings.
  • Templates guide consistent capture: What happened, rationale, next steps, and references.
  • Retrieval and context surfacing across sessions to reduce rework.

Quick Start

After completing a task, save a note anchored to that task by specifying the task_id, a note_type (investigation, decision, docs, or learnings), and a concrete content field.

Frequently Asked Questions about note

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save investigation notes anchored to a specific task?

To save investigation notes, specify the task_id, select a note_type such as investigation or decision, and provide the concrete content. The Skill validates these inputs and applies PII scrubbing before storing the structured note.

What note templates are available for capturing decisions and learnings?

Templates guide consistent capture by structuring content into What happened, rationale, next steps, and references. Supported note types include investigation, decision, docs, and learnings.

Can I retrieve past debugging session notes across different work sessions?

Yes, the Skill supports retrieval and context surfacing across sessions. This reduces rework by preserving findings and making previous documentation accessible for future tasks.

What task details do I need before creating a structured note?

You need a valid task_id, a note_type from the supported options, and the content field. The Skill validates these three fields to ensure findings are properly anchored before storage.

Does this approach work better than unstructured note-taking for preserving investigation findings?

Structured note-taking with templates ensures consistent capture of what happened, rationale, next steps, and references, reducing rework compared to unstructured methods that lose context across sessions.