메뉴
Advanced Obsidian knowledge management using callouts, properties, and wikilinks. Aligned with the Gold Standard.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Treat the Obsidian vault as operational memory, not just note storage. Focus on retrieval quality, metadata integrity, and safe consolidation.
Write X/Twitter posts, tweet drafts, shitposts, and short threads for engineering or startup topics. Use this when the user asks for a tweet, X post, shitpost, post draft, or wants social copy for Twitter/X. Always return 3 distinct variants, each inside its own code block, unless the user explicitly asks for one.
Send messages to Discord channels via webhook or bot
Where logs live and when to write them — errors, daily, system
Write and publish tech articles to Dev.to.
Modify your own source code, understand project structure, add new features.
SOC 직업 분류 기준
| name | obsidian-pro |
| description | Advanced Obsidian knowledge management using callouts, properties, and wikilinks. Aligned with the Gold Standard. |
| metadata | {"version":"1.1.0","author":"openclawgotchi","capabilities":["callouts","properties","wikilinks","canvas","hierarchical-tags"],"openclaw":{"emoji":"💎","always":false}} |
Use these rules to make notes "Obsidian-native", structured, and part of a high-quality knowledge base.
Semantic formatting is mandatory. Always use Obsidian Callouts:
> [!abstract] Abstract: Brief TL;DR or summary of the note.> [!quote] Raw: Mandatory. Full original text from the user message. Do not truncate.> [!info] Details: For additional context, metrics, or technical specs.> [!todo] Actions: Detected tasks or next steps.Every note MUST start with this exact YAML block. Metadata is critical for Dataview and organization.
---
id: "YYYY-MM-DD-HHMMSS"
type: "vault-note"
note_type: "memo" # memo, research, plan, asset, issue, insight
created: "YYYY-MM-DDTHH:MM:SS"
source: "telegram" # telegram, discord, system
project: "project-slug"
topic: "sub-topic"
status: "seedling" # seedling (draft), budding (developing), evergreen (ready)
tags:
- "type/memo" # Hierarchical: type/*
- "area/product" # Hierarchical: area/*
- "status/seedling" # Hierarchical: status/* (must match status field)
---
[[Project Hub Name]] or [[Topic Name]].[[projects/project-slug]]) and relevant Area ([[topics/sub-topic]]).notes/: Main storage for atomic notes.projects/: Hub pages for specific projects (e.g., bitdive.md).topics/: Index pages for broad areas (e.g., product.md).attachments/: For images and files.#memo. Always use #type/memo or #area/marketing.#status/* tag matches the status field.vault_search before creating. Extend existing notes if they cover the same core thought.vault_write(path, content): Use the Gold Standard template above.vault_read(path): Check existing content before any edit.vault_list(path): Map out the structure.vault_search(query): Find link targets and prevent duplicates.