From workflows
Organize Obsidian notes according to clawd's preferences. Use when user asks to "organize notes", "move notes to right folder", "clean up vault", "tidy vault", "file this note", or when creating new notes in the Obsidian vault. Also use when moving, renaming, or categorizing notes, or when the vault root has stray files.
npx claudepluginhub edwinhu/workflows --plugin workflowsThis skill uses the workspace's default tool permissions.
Clawd's Obsidian vault follows the PARA method. Every note belongs in a specific folder — nothing lives in the vault root.
Implements Playwright E2E testing patterns: Page Object Model, test organization, configuration, reporters, artifacts, and CI/CD integration for stable suites.
Guides Next.js 16+ Turbopack for faster dev via incremental bundling, FS caching, and HMR; covers webpack comparison, bundle analysis, and production builds.
Discovers and evaluates Laravel packages via LaraPlugins.io MCP. Searches by keyword/feature, filters by health score, Laravel/PHP compatibility; fetches details, metrics, and version history.
Clawd's Obsidian vault follows the PARA method. Every note belongs in a specific folder — nothing lives in the vault root.
Vault/
├── 0. Inbox/ # Unsorted captures, quick notes
├── 1. Projects/ # Active projects with deadlines
├── 2. Areas/ # Ongoing responsibilities
├── 3. Resources/ # Reference material
│ ├── People/ # Notes about individuals
│ ├── References/ # Technical references (APIs, tools, comparisons)
│ ├── Concepts/ # Ideas, frameworks, mental models
│ └── ... # Other resource categories as needed
├── 4. Archive/ # Completed/inactive items
└── Templates/ # Note templates
| Note Type | Folder | Example |
|---|---|---|
| Person (colleague, contact, public figure) | 3. Resources/People/ | Jeffrey Peck - PSLRA Lobbyist.md |
| API docs, tool guides, tech comparisons | 3. Resources/References/ | Claude API - Streaming Responses.md |
| Concepts, frameworks, mental models | 3. Resources/Concepts/ | Efficient Market Hypothesis.md |
| Active project with a deadline | 1. Projects/ | Current research, course prep |
| Ongoing responsibility (no end date) | 2. Areas/ | Teaching, health, finances |
| Quick capture, unsorted | 0. Inbox/ | To be filed later |
| Done, no longer active | 4. Archive/ | Past projects, old references |
Titles should be descriptive and include context so they're findable without opening the note:
Full Name - Role or Context.md (e.g., Jeffrey Peck - PSLRA Lobbyist.md)Tool/Topic - Specific Aspect.md (e.g., jq - Container Compatibility Notes.md)Avoid generic titles like Meeting Notes.md or Ideas.md — add the date, person, or topic.
3. Resources/) rather than the root0. Inbox/ is the right temporary home — but follow up by filing it properly1. Projects/ to 4. Archive/