「obsidian」の検索結果

Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.

日本語の概要は準備中です。原文の説明を表示しています。

Read, search, create, and edit notes in the Obsidian vault.

日本語の概要は準備中です。原文の説明を表示しています。

Segundo cérebro persistente em Markdown — LLM Wiki no padrão Karpathy mantida como bundle Open Knowledge Format v0.2, com fontes imutáveis em raw/ e conceitos citados em wiki/. Use quando o usuário disser "segundo cérebro", "second brain", "adiciona isso ao meu brain", "salva na minha wiki", "ingere esse artigo/PDF/link", "o que minha wiki diz sobre", "o que meu brain sabe sobre", "consulta meu conhecimento", "lint da wiki", ou pedir para acumular conhecimento de fontes de forma durável. NÃO use para notas do Obsidian (pwdev-obsidian), planejamento de features (pwdev-feat) nem PRDs (pwdev-prd).

日本語の概要は準備中です。原文の説明を表示しています。

Read, search, and create notes in the Obsidian vault.

日本語の概要は準備中です。原文の説明を表示しています。

Read, search, create, and edit notes in the Obsidian vault.

日本語の概要は準備中です。原文の説明を表示しています。

Search, create, and manage notes in an explicit Obsidian vault with title-case filenames, wikilinks, index notes, backlinks, and safe vault-root confirmation.

日本語の概要は準備中です。原文の説明を表示しています。

複雑な作業や失敗から、根本原因、次回の行動、問題を見分ける兆候を抽出し、再利用できる学習記録にまとめます。同じ原因の既存記録との重複も整理します。

• 複雑な作業後に学びを残したいとき
• 障害調査の原因と教訓の記録
• 同じ原因の学習記録を統合したいとき

Render Markdown from templates and structured data using Knap CLI. Use when the user asks to apply a Knap template, turn JSON or CSV data into notes, batch-generate Markdown files, or format Defuddle output into a note.

日本語の概要は準備中です。原文の説明を表示しています。

Extract clean Markdown from HTML pages with Defuddle CLI.

日本語の概要は準備中です。原文の説明を表示しています。

标准化实验日志记录——直接上传或读取本地图片、语音和文字，产出带 YAML frontmatter 的 Markdown；可选集成飞书 CLI 与 Obsidian。

日本語の概要は準備中です。原文の説明を表示しています。

Chat with a companion that knows your notes folder (a journal, an Obsidian vault, any .md or .txt files) and every earlier chat, using cognee memory with local databases. Use when someone wants to ask questions about their own notes, or to talk with a companion that remembers past conversations. Runs locally; reads the notes folder, writes only to cognee's memory.

日本語の概要は準備中です。原文の説明を表示しています。

Universal migration from Obsidian, Notion, Logseq, markdown, CSV, JSON, Roam

日本語の概要は準備中です。原文の説明を表示しています。

Use when a Head of Ops, Knowledge Manager, or TPM-Internal needs to author, validate, or clean up company SOPs and internal runbooks (procurement intake, vendor offboarding, incident-comms cascade, employee onboarding) — including 5W2H completeness checks (Who-What-When-Where-Why-How-HowMuch), cross-link and orphan-page validation across a sprawling Notion/Confluence/Obsidian wiki, KB ingestion + hygiene reporting, and runbook step verification (named owner, expected duration, observable success signal, rollback path, escalation contact). Pairs Ishikawa's 5W2H method, Gawande's *The Checklist Manifesto*, ISO 9001, ITIL v4, and Google SRE Workbook runbook discipline with deterministic stdlib-only Python tools that score completeness, detect anti-patterns, and emit prioritized cleanup lists (e.g., "validate this runbook before it goes into rotation", "audit our Confluence wiki for stale and orphaned SOPs").

日本語の概要は準備中です。原文の説明を表示しています。

Read or configure the vault filing methodology and suggest destinations for planned knowledge creation under Generic, LYT, PARA, or Zettelkasten. Use for wiki mode, methodology mode, what is my vault mode, set vault mode, switch to PARA, use LYT, Zettelkasten setup, change mode, configure mode, or methodology routing. This skill does not save content or migrate notes.

日本語の概要は準備中です。原文の説明を表示しています。

Plan and, with explicit network consent, use an optional external Defuddle cleaner to extract article-like HTTPS pages as Markdown. Use for defuddle, clean this URL, strip page clutter, readable Markdown from a web page, or preparing a web source for later wiki ingestion.

日本語の概要は準備中です。原文の説明を表示しています。

Apply the Fable-derived 10-stage OBSERVE, OBSERVE, LISTEN, THINK, CONNECT, CONNECT, FEEL, ACCEPT, CREATE, GROW loop to consequential or ambiguous reasoning and decisions. Use for think this through, deep think, architecture review, postmortem, tradeoff analysis, or challenges to assumptions. This is a reasoning review, not a deterministic vault health check or repair workflow.

日本語の概要は準備中です。原文の説明を表示しています。

Run a bounded, source-grounded research loop, draft a cited dossier, and optionally propose a separately reviewed canonical vault merge. Use when the user wants autonomous or deep research that may access the public web. Triggers: /autoresearch, autoresearch, research this topic, deep dive into, investigate, find everything about, research and file, go research, build a wiki on.

日本語の概要は準備中です。原文の説明を表示しています。

Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta, remote egress requires explicit consent, and unavailable reranking falls back deterministically.

日本語の概要は準備中です。原文の説明を表示しています。

GitHub-dark + 紫蓝环境光 + 三色渐变标题 + GitHub 风代码

日本語の概要は準備中です。原文の説明を表示しています。

产品经理与内容创作者在构建Obsidian知识库或梳理复杂逻辑时，当需要创建思维导图、流程图等可视化画布，使用此技能可自动生成标准.canvas文件，精准配置节点、连线与层级，一键生成完美排版，彻底告别手写JSON的繁琐与报错。

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill for project-scoped literature review built on Sources/Papers, with synthesis landing in Knowledge, writing handoff in Writing, and the default literature canvas under Maps/literature.canvas.

日本語の概要は準備中です。原文の説明を表示しています。

Extract clean Markdown from web pages. In the KB workflow, use it as a utility under obsidian-source-ingestion.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when Zotero is the literature source of truth and the project KB should receive source notes under Sources/Papers plus project-linked synthesis in Knowledge and Writing.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when the user asks to "write an experiment report", "summarize experimental results", "do experiment retrospection", "write a results report", "写实验总结报告", "写实验复盘", or mentions turning completed experiment artifacts into a structured, decision-oriented research report. It assumes strict analysis should come from `results-analysis` first.

日本語の概要は準備中です。原文の説明を表示しています。