Obsidian Skills for OpenClaw Agents

cross-platform-memory-hub

@jinyu12166

Cross-platform persistent memory system for AI agents: session continuity, task tracking, decision records, and project context across coding sessions. Free tier provides templates and adapter configurations. Paid tier enables cross-platform synchronization execution via clawtip verification.

Article Fetcher（文章抓取+Notion/Obsidian知识库存档）

@ajayhao

抓取微信公众号、小红书、豆瓣、知乎文章，自动上传 OSS 图片，LLM 智能提取关键词，一键存档到 Obsidian 本地知识库（可选 Notion）

知乎抓取.SKILL

@handsomestwei

知乎收藏夹与文章内容抓取：API/Playwright 多级降级、Cookie 持久化与保活、批量正文与图片、断点续传、可选写入 Obsidian。| Zhihu collection scraping, batch article fetch, Obsidian export.

Obsidian CLI

@adolago

Skill for the official Obsidian CLI (v1.12+). Complete vault automation including files, daily notes, search, tasks, tags, properties, links, bookmarks, base...

Web Search Rules

@englandtong

Verify and govern web research intake

obsidian-memory-system

@jinyu12166

Obsidian persistent memory system: AI-delivered session continuity, task tracking, decision records, and project context for AI agents. Payment verification via clawtip. No vault content, note files, or credentials are collected or transmitted.

Clip2MD

@kllb520

Use clip2md to configure an access token, save web pages or article URLs as Markdown clipping tasks, check remaining daily/permanent quota, query task status, and wait for clipping completion or failure. Use when the user mentions clip2md, 剪藏, clip, 保存网页为 Markdown, 查询额度, 提交链接, 查询任务, 等待剪藏完成, or wants

Obsidian CLI(免费版)

@thcjp

Obsidian CLI工具免费版是一款面向个人知识管理场景的命令行辅助Skill，让AI Agent能够直接通过命令行操作Obsidian笔记库，实现笔记的创建、读取、搜索和基础管理。核心能力：文件读写与列表、全文搜索与标签查询、Daily Notes日常笔记、基础任务管理、属性读写。Use when 需要项目管理、任务规划、进度跟踪、团队协作时使用。不适用于实际人员绩效评估.

Drawio Diagram Builder

@holdyounger

Create, edit, replicate, and iteratively refine editable research and technical diagrams in diagrams.net/draw.io (.drawio XML) from prompts, papers, repositories, screenshots, or existing diagrams. Use when asked to generate a scientific figure, paper method diagram, ML/system architecture diagram,

Agent Social Reader

@hermiod99-vibe

Empower your AI agent to read and summarize specific public web or social media links from TikTok, Instagram, X (Twitter), YouTube, Facebook, Reddit, LinkedIn, Threads, Pinterest, Bluesky, Twitch, Snapchat, Kick, Lemon8, Douyin, Xiaohongshu, Weibo, Bilibili, Kuaishou, Xigua, Zhihu, WeChat Official

AI 书童

@yamyeed

AI 书童，辅助阅读、学习、考试、写作与信息收集。当用户说"书童"、"伴读"、"背书"、"考我"、"查典故"、"整理书架"、"复习"、"备考"、"誊抄"、"代写"、"找书"、"学术动态"、"读书笔记"、"阅读计划"、"知识管理"、"晒书"、"盘点笔记"、"整理知识库"、"补书"、"修补笔记"、"完善笔记"、"抄书...

LifeOS

@quanru

Read, query and edit a LifeOS / Obsidian PARA vault (notes, tasks, periodic notes, theme notes, tags, AI Wiki) from the command line via the `lifeos` CLI — h...

Obsidian CLI(专业版)

@thcjp

专业版Obsidian命令行管理工具，支持文件操作、模板、插件、同步、历史、开发调试及TUI交互，适合高级用户和团队协作。

AgentLens Social Connector

@inkad-code

Official AgentLens skill for retrieving public social media links through the AgentLens API, summarizing and interpreting the returned content/media, and saving the result to a user-confirmed knowledge base when the AI agent has the required capability. Use when the user shares a TikTok, Instagram,

article-organizer-builder

@kakahilda

生成器技能（元技能）——专为 Obsidian 用户设计：当用户想构建/生成一个「文章收藏整理」类 Skill（把公众号/网页文章批量提炼为结构化笔记、按主题分类归档进 vault 收藏夹、三依据去重防重复收藏、清理源文件）时使用； 生成的笔记自动带 frontmatter 标签、相关笔记双链与单一总索引 MOC，直接织入 Obsidian 知识图谱。 也用于把个人化的收藏整理 skill 转换为可复用的通用模板。触发词：构建收藏整理skill、生成文章整理skill、 收藏整理skill怎么做、做一个文章归档skill、obsidian收藏整理、article organizer skill

Set up and use Talamus as durable, local-first memory for AI agents. Use when an agent needs to initialize or diagnose a Talamus brain, ingest files or repos...

科研工作区 (research-ops)

@tomuiv

科研项目工作区通用方法论（跨项目 / 跨机，零项目专有路径）。把「本地文件 + Zotero + Obsidian + 飞书」四层按「每类内容一个真源」组织：项目 ID 命名、本地目录模板（README/STATE/scripts/data/results/output + chats + buffer）、组级 INDEX 登记表、跨机同步纪律、同步操作「双端确认」。当用户要"新建/整理科研项目、搭建组目录、登记项目索引、把项目映射到 Zotero/Obsidian/飞书、导出对话存档、处理 buffer、检查跨机同步"时使用。本 skill 只给通用规则与参数化脚本；**具体组名/路径/collection/文件夹由各项目 AGENTS.md 特化**（见 §8）。

OBSIDIAN

@psprosen-dev

Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.

Openclaw Obsidian

@lanjelin

Read, search, create, edit, and safely refactor an Obsidian Markdown vault directly through files, without Obsidian or an Obsidian CLI.

Check an LLM wiki's health and fix what it finds: broken links, leaked credentials, orphaned and unreferenced pages, missing frontmatter or descriptions, stale pages, oversized pages and duplicate titles. Ships a zero-dependency Python checker for markdown folders ([[wikilinks]] and relative links, Obsidian-compatible). Use on a schedule, before committing or merging wiki changes, after a refactor, or when an agent reports it cannot find a page.

Start a new LLM wiki or bring an existing folder of notes or Obsidian vault under maintenance: write the SCHEMA page that tells every agent the wiki's domain, folder layout, page types, frontmatter, tags and thresholds, and point each agent's instructions file at it. Use when creating a knowledge base that agents will maintain, when a wiki has no schema page, or when agents keep writing pages in inconsistent shapes.

Rules for an LLM wiki that several agents, machines or people write to: read before writing, detect concurrent edits, prefer small edits to rewrites, attribute every change with a note, derive the index and log instead of hand-editing shared files, and keep scoped content where only the right readers see it. Use when more than one agent or person maintains the same wiki, or when setting up a wiki for a team or an agent fleet.

File a decision, finding or fact into an LLM wiki the right way: find the page that already covers it, make the smallest edit that records it, keep frontmatter and dates current, link it to its neighbors, cite where it came from, and leave a change note. Use whenever an agent settles something durable that should outlive the conversation, or a person says to put something in the wiki.

Read an LLM wiki before working in it or answering from it: the schema page, the catalog of page descriptions, recent changes, then a targeted search and the canonical page for the topic. Use at the start of any task that will read or change a shared markdown wiki, and before asking a person to repeat context the wiki may already hold.

Review what agents recently wrote to an LLM wiki: read each change as a diff, accept, fix or revert it with a note, promote drafts that pass, and send a person a short digest of what changed and what needs their call. Use daily or weekly on a wiki that agents write to, when drafts are waiting for approval, or after a burst of agent writes such as a large ingest.

Capture what an agent session settled into an LLM wiki before it is lost: at the end of a task or session (or over saved transcripts), pick out decisions, verified facts, corrections and working procedures, drop the chatter, and file each item on the page that owns it. Use when a session or task ends, before context is compacted, when a person says to remember something, or on a schedule over past agent sessions (Claude Code, Codex, Hermes, OpenClaw).

Fact-check an LLM wiki against its own sources: pick the pages where an error would do the most harm, pull out the checkable claims, open each cited source and mark every claim supported, outdated, unsupported, unsourced or unreachable, then correct the page and every page that copied the claim. Use on a schedule, before a decision relies on a page, after a large ingest, or when a page's claims are in doubt.

Restructure an LLM wiki without breaking it: split oversized pages into focused linked pages, merge duplicate pages, rename or move pages, and archive superseded ones, rewriting every inbound link and confirming zero broken links afterwards. Use when a page passes about 200 lines, when two pages cover the same topic, when the folder layout changes, or when a page is superseded.

Handle contradictions and outdated claims in an LLM wiki without silently overwriting: compare dates, provenance and the current system of record, replace only when one side is clearly authoritative, otherwise keep both claims side by side, mark the page contested or lower its confidence, and escalate material conflicts to a person. Use when a new source disagrees with a page, when two pages disagree, or when a fact on a page may no longer be true.

Answer a question from an LLM wiki: find and read the relevant pages, answer with the page paths you relied on, check anything mutable at its original source, say plainly what the wiki does not cover, and file substantial answers back as query pages so the research compounds. Use when a person asks something the wiki may cover, or after an answer took real research.

Compile a source (article, paper, transcript, meeting notes, doc, dataset) into an LLM wiki with provenance: keep an immutable raw copy with a hash, update every existing page the source touches instead of writing one summary page, cite the source at each claim, and label how far each claim can be trusted. Use when adding a new source to a wiki or when asked to read something and add it to the wiki.