knowledge-translator

Convert unstructured content into structured Obsidian knowledge notes with metadata and links.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/Lucien-1127/strata-skill --skill knowledge-translator-lucien-1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: knowledge-translator
Source: https://github.com/Lucien-1127/strata-skill/tree/main/knowledge-translator
Command: npx skills add https://github.com/Lucien-1127/strata-skill --skill knowledge-translator-lucien-1127

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Scattered notes, chat logs, and raw content are hard to organize and retrieve later. This Skill transforms loose material into well-structured Obsidian knowledge notes with consistent metadata, tags, and bidirectional links, making your personal knowledge base searchable and interconnected. ## Core Features & Use Cases - Structured Note Generation: Produces notes with YAML frontmatter (title, tags, aliases, created date) following Obsidian conventions. - Formatted Body Content: Organizes content with core definitions, headings, blockquotes, and bullet lists for readability. - Link Suggestions: Recommends [[bidirectional links]] to connect the new note with related notes in your vault. - Use Case: After a research session, paste raw findings and ask for a structured note; the output is a ready-to-save Obsidian note with tags and links to related concepts. ## Quick Start Convert the following content into a structured Obsidian knowledge note with metadata, tags, and link suggestions.

Frequently Asked Questions about knowledge-translator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert notes into Obsidian format?▼

Provide your raw content and request a structured knowledge note. The output includes YAML frontmatter with title, tags, aliases, and created date, followed by organized body sections and bidirectional link suggestions ready to paste into your Obsidian vault.

What is the best way to structure Obsidian notes?▼

A well-structured Obsidian note starts with YAML frontmatter containing title, tags, aliases, and creation date, followed by a core definition, hierarchical headings, blockquotes, and bullet lists. Ending with [[wikilink]] suggestions connects the note to related concepts.

Does this work with any type of source content?▼

Yes, it accepts scattered or unstructured text such as research notes, chat excerpts, or article drafts. The content is reorganized into a consistent note structure regardless of the original formatting.

When should I not use structured note conversion?▼

Avoid it for content that must preserve exact original wording, such as legal documents or verbatim transcripts, since the process reorganizes and rephrases material. It is designed for knowledge synthesis, not archival fidelity.