claude-note

🥈Silver

Claude-note automates note-taking and documentation for operations teams. It integrates with Claude Code and VSCode to streamline workflows, reducing manual effort. Ideal for developers and operations staff managing complex projects.

3180Updated 2w ago

Intermediate30min to implementautomation

Saves ~45 min per use

Quick InstallView Source

git clone https://github.com/twtrubiks/claude-note.git

Works with:

Claude

Overview

About This Skill

How to Use

1. **Capture Meeting Notes**: Use Claude Code or VSCode to record meeting notes in a structured format (e.g., Markdown, JSON, or plain text). Include timestamps, attendees, and key discussions. 2. **Run claude-note**: Paste the prompt template into your AI tool (Claude/ChatGPT) and replace `[MEETING_NOTES]` with your actual notes. For large meetings, break notes into sections (e.g., by agenda item) for better results. 3. **Review and Refine**: Check the generated summary for accuracy. Add missing details like responsible parties or deadlines if they weren’t explicitly stated in the notes. 4. **Integrate into Workflow**: Save the output as a Markdown file in your project’s `/docs` folder or sync it to tools like Notion/Jira using their APIs. Use the `Technical Details` section to auto-generate config files or tickets. 5. **Automate Repetitive Tasks**: For recurring meetings (e.g., sprint standups), create a template with placeholders like `[MEETING_DATE]` or `[TEAM_NAME]` to standardize outputs. Store templates in a shared directory for team access.

Setup & Installation

Quick Install

No install command available. Check the GitHub repository for manual installation instructions.

Alternative Install (Git Clone)

git clone https://github.com/twtrubiks/claude-note

Requirements

Claude Code or compatible AI agent
Works with: Claude

Quick Start Guide

Install the Skill

Copy the install command above and run it in your terminal.

Open Your AI Agent

Launch Claude Code, Cursor, or your preferred AI coding agent.

Try It Out

Use the prompt template or examples below to test the skill.

Customize

Adapt the skill to your specific use case and workflow.

Usage Examples

Prompt Template

Generate a structured summary of the key decisions, action items, and technical details from the following [MEETING_NOTES]. Format the output as a Markdown document with sections: **Decisions**, **Action Items**, **Technical Details**, and **Next Steps**. Include timestamps and responsible parties where applicable. Prioritize clarity and actionability for the operations team. Meeting notes: [MEETING_NOTES]

Example Output

**claude-note Summary Report**
*Generated on: 2024-05-20*

**Decisions**
1. **API Rate Limiting**: Approved the implementation of a 1000 requests/hour limit for the `/data` endpoint to prevent abuse. (Approved by: Sarah Chen, CTO)
2. **Infrastructure Costs**: Budget approved for migrating the staging environment to AWS Graviton instances, reducing costs by ~30%. (Approved by: Mark Reynolds, VP of Engineering)

**Action Items**
| Task | Owner | Deadline | Status |
|------|-------|----------|--------|
| Implement API rate limiting in `api-gateway` service | DevOps Team (Lead: Alex) | 2024-05-27 | Pending |
| Update Terraform configs for Graviton migration | Infrastructure Team | 2024-06-03 | In Progress |
| Schedule load testing for new rate limits | QA Team | 2024-06-05 | Not Started |

**Technical Details**
- **Rate Limiting**: Using Redis-based token bucket algorithm. Configuration stored in `config/rate_limits.yaml`.
- **Graviton Migration**: Requires ARM64-compatible Docker images. Current blockers: `legacy-service-A` not compatible.
- **Load Testing**: Will use Locust with 1000 concurrent users simulating real-world traffic patterns.

**Next Steps**
1. Alex to finalize rate limiting implementation by EOD Friday.
2. Infrastructure Team to resolve ARM64 compatibility issues by May 28.
3. QA Team to validate performance metrics post-migration by June 7.

*Document generated by claude-note for operations team reference.*