Skip to content
Back to skills

Obsidian Rate Limits

ASecurity

Handle Obsidian file system operations and throttling patterns. Use when processing many files, handling bulk operations, or preventing performance issues from excessive operations. Trigger with phrases like "obsidian rate limit", "obsidian bulk operations", "obsidian file throttling", "obsidian performance limits".

  • 4 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 10, 2026
documentationjavascriptjavaperformance

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 10, 2026

npx -y skills add micsapp/micstec-skills --skill obsidian-rate-limits --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Obsidian Rate Limits?

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

Security grade badge for Obsidian Rate Limits
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/micsapp-obsidian-rate-limits/badge)](https://www.skillsdirectory.com/skills/micsapp-obsidian-rate-limits)

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
---
name: obsidian-rate-limits
description: |
  Handle Obsidian file system operations and throttling patterns.
  Use when processing many files, handling bulk operations,
  or preventing performance issues from excessive operations.
  Trigger with phrases like "obsidian rate limit", "obsidian bulk operations",
  "obsidian file throttling", "obsidian performance limits".
allowed-tools: Read, Write, Edit
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
compatible-with: claude-code, codex, openclaw
---
# Obsidian Rate Limits

## Overview
Throttling patterns for Obsidian plugin file system operations. Obsidian runs on Electron with single-threaded UI -- excessive vault operations freeze the interface and risk data corruption.

## Prerequisites
- Understanding of Obsidian's event loop
- Familiarity with async JavaScript patterns
- Awareness of vault size impact on operations

## Instructions

### Step 1: Throttled File Operations

### Step 2: Batch Read with UI Yielding

### Step 3: Debounced Event Handlers

### Step 4: Progress Feedback for Long Operations

For full implementation details and code examples, load:
`references/implementation-guide.md`

## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| UI freezes | Too many sync operations | Batch with UI yielding |
| Data corruption | Concurrent writes to same file | Queue writes, serialize per file |
| Memory pressure | Reading all files at once | Process in batches |
| Missed events | Over-debouncing | Set reasonable debounce (300-500ms) |

## Resources
- [Obsidian Performance Tips](https://docs.obsidian.md/Plugins/Guides/Performance)

## Output

- Configuration files or code changes applied to the project
- Validation report confirming correct implementation
- Summary of changes made and their rationale

See [ORM implementation details](${CLAUDE_SKILL_DIR}/references/implementation.md) for output format specifications.

## Examples

**Basic usage**: Apply obsidian rate limits to a standard project setup with default configuration options.

**Advanced scenario**: Customize obsidian rate limits for production environments with multiple constraints and team-specific requirements.

Files in this skill

  • SKILL.md2.2 KB
  • references/implementation-guide.md3.1 KB
  • references/implementation.md5.9 KB

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…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.