Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Capture And Organize Notes

ASecurity

Used to capture and organize notes, ideas, quotes, and journal entries with automatic tagging, linking, and knowledge graph maintenance.

19 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsrustgodebuggingapi

Works with

api

Security Analysis

A100/100

Scanned 9/19/2026

Install to Claude Code

$npx -y skills add rondoflow/rondoflow --skill capture-and-organize-notes --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Capture And Organize Notes?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Capture And Organize Notes
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rondoflow-capture-and-organize-notes/badge)](https://www.skillsdirectory.com/skills/rondoflow-capture-and-organize-notes)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: capture-and-organize-notes
description: "Used to capture and organize notes, ideas, quotes, and journal entries with automatic tagging, linking, and knowledge graph maintenance."
category: "Productivity"
author: community
version: "1.0.0"
icon: check-square
---

# Configuration

Run `pwd` and get the `{curDir}`

- **Notes directory:** `{curDir}/slipbox/`
- **Graph index:** `{curDir}/slipbox/.graph/graph.json`
- **Timezone:** User's local timezone (check USER.md or system)

# Note Patterns & Types

### Prefixes
- `> {content}` → quote, contains attributed text.
- `! {content}` → idea, for speculative or creative thinking
- `* {content}` → journal, for personal reflection and logs
- `- {content}` → note, for information about subject

### Delimiters
- `~ {content}` → source (appended after prefix+content combination)
    - Example note with source: `- Content here ~ Source Type, Source Title by Source Author`
    - Example quote with source: `> Content here ~ Source Type, Source Author`

# Workflow

## 1. Capture

When a note is recognized:

1. **Extract content and metadata**
    - Note content
    - Type (quote/idea/journal/note)
    - Source information (if provided)

2. **Generate filename**
    - Format: `YYYYMMDD-HHMMSS-slug.md`
    - Slug: lowercase, hyphenated, from content passed in (max 4-5 words)
    - Example: `20260131-143022-compound-interest.md`

3. **Check for existing source**
    - If source is not provided set `source: null`.
    - If source provided, search existing notes for matching source title (case insensitive)
        - Use existing source if found
        - Otherwise, use provided source as-is
        - **No external API calls** - trust user input

4. **Generate tags**
    - Extract specific objects concepts (nouns)
    - Focus on: people, tools, techniques, systems, specific topics
    - **Avoid broad categories** like "productivity" or "ideas"
    - **Consistency:** Check existing tags before creating new ones
    - 2 or 3 tags per note
    - Examples: `[pomodoro-technique, Cal-Newport, deep-work]`

5. **Create markdown file**

```yaml
---
title: "Generated Note Title from Content"
date: 2026-01-31T14:30:22-05:00
type: note
tags: [specific, object, based, tags]
source:
  title: "Source Title"
  type: "book"
  author: "Author Name"
links: []
---

Note content here in markdown.
```
### Note Titles
- **Descriptive but concise:** 3-8 words
- **Avoid generic:** Not "Thoughts" or "Notes", be specific
- **Question format works:** "Why does X happen?" or "How to Y?"

## 2. Link

After creating a note, find connections:

1. **Search existing notes**
   - Look for related concepts, people, topics
   - Check for overlapping tags

2. **Determine connection type**
   - **related** - Similar topic or theme
   - **extends** - Builds on or expands another note
   - **contradicts** - Opposing viewpoint
   - **references** - Mentions same person/book/concept
   - **supports** - Provides evidence for another note

3. **Add bidirectional links**
   - Update both notes' frontmatter
   - Include reason for connection

**Quality over quantity:** Only link when genuinely related

```yaml
links:
  - id: "20260120-093045-compound-interest"
    type: related
    reason: "Both discuss exponential growth concepts"
```

## 3. Note Validations

3.1: **Validate frontmatter** - Ensure the note has the required fields
    - title
    - date
    - type
    - tags

3.2: **Remove broken links**
    - Check if notes that the new note links to still exist
    - If any files are missing save them to `{curDir}/slipbox/missing.md`

## 4. Update Graph

After capture and linking:

4.1: **Load graph index**
    - Read `{curDir}/slipbox/.graph/graph.json`

4.2: **Add/update note entry**

```json
{
  "notes": {
    "20260131-143022-note-title.md": {
      "title": "Your Note Title",
      "source": {
        "title": "Source Title",
        "type": "book",
        "author": "Author Name"
      },
      "type": "note",
      "tags": ["tag1", "tag2"],
      "links": [
          "20260120-093045-other-note.md",
      ]
    }
  },
  "last_updated": "2026-01-31T14:35:00-05:00"
}
```
4.3: **Remove any entries from graph**
    - Read `{curDir}/slipbox/missing.md`
    - If any notes are found missing remove the entry from the graph.
    - Then remove them from `{curDir}/slipbox/missing.md`

4.4: **Rebuild graph**
    - If corrupted beyond simple note removals, rebuild from the current note files.

4.5: **Write updated graph**
    - Save back to `{curDir}/slipbox/.graph/graph.json`

## Querying

Respond to natural queries like: "Show me notes about X"

**Approach:**
1. Search graph index first (fast); only fall back to file search if needed.
2. Present results with titles, dates, snippets
3. Offer to show full content if relevant

## User Feedback

Keep responses minimal:
- ❌ Don't narrate every step unless debugging

### Example Interaction

**User:** "- The Feynman Technique is about teaching concepts to identify gaps in understanding"

**You:**
1. Create `20260131-163500-feynman-technique.md`
2. Tag: `[Feynman-technique, learning, teaching]`
3. Search for related notes (study techniques, learning methods)
4. Link to any relevant note about learning
5. Update graph index
6. Reply: "Note captured: Feynman Technique"

---

**When to apply this skill:** Whenever user shares content that starts with the defined prefixes the content which follows should be captured for later reference.

Attribution

rondoflowrondoflow
View sourceMore from rondoflow →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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 (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →