edwinhu/obsidian-organize
skills/obsidian-organize/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add edwinhu/workflows obsidian-organizeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 5:35 PM29.2s1 file scanned
SKILL.md
- name:
- obsidian-organize
- description:
- >-
- user-invocable:
- false
Obsidian Note Organization
Clawd's Obsidian vault follows the PARA method. Every note belongs in a specific folder — nothing lives in the vault root.
Folder Structure
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
Placement Rules
| 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 |
Naming Conventions
Titles should be descriptive and include context so they're findable without opening the note:
- People:
Full Name - Role or Context.md(e.g.,Jeffrey Peck - PSLRA Lobbyist.md) - References:
Tool/Topic - Specific Aspect.md(e.g.,jq - Container Compatibility Notes.md) - Projects: Use the project's natural name
Avoid generic titles like Meeting Notes.md or Ideas.md — add the date, person, or topic.
Vault Hygiene
- The vault root directory should contain only folders, never loose notes
- If a note doesn't clearly fit a subcategory, place it in the parent PARA folder (e.g.,
3. Resources/) rather than the root - When in doubt,
0. Inbox/is the right temporary home — but follow up by filing it properly - Periodically move completed projects from
1. Projects/to4. Archive/
Related Skills
edwinhu/npx-ownership-panel
development
VerifiedTrustedCommunity
Build the meeting-level proxy-voting × ownership panel on the WRDS SGE grid — ISS N-PX fund votes reduced to (item × block) direction cells, joined to institutional and mutual-fund ownership. Use when working with risk.voteanalysis_npx, N-PX fund-level votes, ISS→CRSP fund linking, index/passive/active voting blocks, or a proxy-voting panel that needs ownership attached.
17SKILL.mdUpdated Jul 28, 2026
edwinhu/crsp-v2
development
VerifiedTrustedCommunity
Use when "CRSP CIZ", "CRSP v2", "CRSP flat file format 2.0", "crsp.dsf_v2 / msf_v2", "StkDlySecurityData", "StkMthSecurityData", "StkSecurityInfoHist", "stocknames_v2", "DlyRet / MthRet / DlyPrc / MthPrc", "SHRCD or EXCHCD equivalent in new CRSP", "SIZ to CIZ migration", "CRSP data after 2024", "CRSP delisting returns", "CRSP cumulative adjustment factors", "CRSP index INDNO / INDFAM", or any CRSP stock/index query where the legacy SIZ column names no longer exist.
17SKILL.mdUpdated Jul 28, 2026
edwinhu/fuzzy-name-matching
development
VerifiedTrustedCommunity
Use when linking or deduping datasets by entity name rather than a shared key — 'fuzzy match', 'fuzzy name matching', 'entity resolution', 'record linkage', 'match company/person names', 'dedupe entity names', 'name-based join', 'bridge identifiers' (CIK ↔ permno ↔ gvkey ↔ wficn ↔ EIN ↔ personid), or any use of char n-gram TF-IDF, cosine similarity on names, `sparse_dot_topn`, or RapidFuzz at scale.
17SKILL.mdUpdated Jul 23, 2026
edwinhu/ds-tables
development
VerifiedTrustedCommunity
Use when building a publication-quality table in Python — 'regression table', 'results table', 'summary statistics table', 'etable', 'coefplot', 'great_tables', 'GT', 'gt table', 'format a table for the paper', 'export table to LaTeX/HTML', significance stars, spanners, or column formatting for a table headed into a paper, slide deck, or notebook.
17SKILL.mdUpdated Jul 23, 2026