doc-bd-data

Create and revise BD-DATA documents with frontmatter keys and data boundaries.

1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-bd-data
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-bd-data
Source: https://github.com/tsuji-tomonori/diopside-v3/tree/main/.opencode/skills/doc-bd-data
Command: npx skills add https://github.com/tsuji-tomonori/diopside-v3 --skill doc-bd-data

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that BD-DATA (Data Architecture) documents are created and revised according to diopside's Obsidian operational guidelines, specifically focusing on defining data collection boundaries and data design principles.

Core Features & Use Cases

  • Standardized Document Creation: Generates new BD-DATA-* documents adhering to strict frontmatter and content requirements.
  • Data Boundary Definition: Helps in clearly specifying data collection scopes, including what is in-scope (e.g., official posts, appearances) and what is out-of-scope (e.g., private, limited).
  • Data Governance: Establishes principles for data separation of concerns (collection, normalization, indexing, distribution) and manages related documentation links.
  • Use Case: When introducing a new data source for the YouTube archive, use this skill to create the BD-DATA-XXX document, clearly defining which videos will be collected and why others will be excluded, ensuring compliance with diopside's documentation standards.

Quick Start

Use the doc-bd-data skill to create a new BD-DATA document for defining data collection boundaries.

Frequently Asked Questions about doc-bd-data

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

FAQPage Schema
How do I standardize data architecture documentation in Obsidian?

To standardize data architecture documentation in Obsidian, generate BD-DATA documents with mandated frontmatter keys, enforce data collection boundaries, and run validation scripts for glossary linking and vault integrity checks.

What is the best way to define data collection boundaries for content management?

Defining data collection boundaries requires explicitly separating in-scope data like official posts from out-of-scope private data, ensuring your content management pipeline maintains clear separation of concerns for collection and normalization.

How to create a new data source document using Obsidian operational guidelines?

To create a data source document using Obsidian operational guidelines, instantiate a BD-DATA template defining data retention policies, processing pipeline stages, and related documentation links to ensure vault standardization.

Does this data architecture standardization approach enforce separation of concerns for processing pipelines?

Yes, this data architecture standardization enforces separation of concerns by mandating explicit boundaries between data collection, normalization, indexing, and distribution stages within the processing pipelines.

Why do my Obsidian vault integrity checks fail when linking glossary terms?

Obsidian vault integrity checks fail when glossary terms are mislinked because the validation scripts mandate strict adherence to frontmatter keys and data governance principles defined in the diopside documentation standards.