document-format

Create standardized knowledge-base documents using templates, schemas, and frontmatter rules.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/leto-labs/jarvis-template --skill document-format
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document-format
Source: https://github.com/leto-labs/jarvis-template/tree/main/.claude/skills/document-format
Command: npx skills add https://github.com/leto-labs/jarvis-template --skill document-format

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create teams can consistently produce properly formatted knowledge-base documents by enforcing workspace conventions, frontmatter schemas, and templates.

Core Features & Use Cases

  • Templates and frontmatter enforcement ensure consistent structure across documents
  • Schema-driven document creation for tasks, projects, people, companies, meetings, bookmarks, and more
  • Guided workflow from loading the schema index to saving in the correct folder with proper links

Quick Start

Create a new document in the appropriate Database folder using the correct schema and template

Frequently Asked Questions about document-format

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

FAQPage Schema
How do I create standardized Obsidian knowledge-base documents with consistent frontmatter?

To create standardized Obsidian knowledge-base documents, apply workspace conventions and template schemas to enforce frontmatter rules and ensure structural consistency across all document types.

What document types are supported by schema-driven document creation?

Schema-driven document creation supports multiple document types including Task, Project, Person, Company, Meeting, and Bookmark, ensuring each follows the Database schema index and per-type README guidance.

How do wikilinks work when saving formatted knowledge-base documents?

Wikilinks connect related documents within the knowledge-base. When saving formatted documents, wikilinks must be properly applied to ensure relational consistency and adherence to the workspace frontmatter rules.

Do I need to manually select a template before creating a new knowledge-base document?

Yes, you must select the correct schema and copy the corresponding template before creating a new knowledge-base document to ensure it is saved with the proper frontmatter in the correct Database folder.

Can I use this schema-driven approach for both meeting notes and project tracking?

Yes, the schema-driven approach supports both meeting notes and project tracking by applying specific template schemas and frontmatter conventions tailored to each document type for consistent knowledge-base formatting.

What is the best way to ensure frontmatter validity across different document types?

The best way to ensure frontmatter validity is to use guided schema-driven workflows that enforce template structures and workspace conventions, automatically validating frontmatter rules for each specific document type.