create-data

Generate structured data files with METADATA, CONTENT, and CLOSING blocks.

Updated Dec 10, 2025
One-click install
npx skills add https://github.com/Creative-Workz-Studio-LLC/bereshit --skill create-data
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-data
Source: https://github.com/Creative-Workz-Studio-LLC/bereshit/tree/main/word/claude/skills/create-data
Command: npx skills add https://github.com/Creative-Workz-Studio-LLC/bereshit --skill create-data

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires cws.studio/pkg/util/fs/toml, cws.studio/skills/create-data/scripts/pkg/config, cws.studio/skills/create-data/scripts/pkg/datagen, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Manually creating structured data files (configs, settings, glossary entries) is error-prone and inconsistent; this skill enforces a reliable, machine-friendly 3-block format for rapid generation.

Core Features & Use Cases

  • 3-block data structure enforcement: METADATA, CONTENT, CLOSING for every file.
  • Template-driven workflow: reuse seeds to ensure consistency and validation.
  • Use case: generate a new config file with proper fields, or create a glossary entry with machine-parseable data.

Quick Start

Create a new 3-block data file from the templates and fill METADATA, CONTENT, and CLOSING with your specific values.

Frequently Asked Questions about create-data

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

FAQPage Schema
How do I automate structured data file creation with consistent formatting?▼

You can automate structured data file creation using a template-driven workflow that enforces a uniform 3-block format, filling METADATA, CONTENT, and CLOSING sections with validation for consistent generation.

What is the 3-block format for generating config and glossary files?▼

The 3-block format structures machine-parseable data into METADATA, CONTENT, and CLOSING blocks, ensuring every generated config or glossary file maintains strict consistency and reliability.

How do I generate a new config file with proper fields and validation?▼

To generate a new config file with proper fields, apply the template-driven workflow to fill the METADATA, CONTENT, and CLOSING blocks, which enforces field consistency and validation automatically.

Can I reuse templates to create multiple glossary entries?▼

Yes, you can reuse template seeds to create multiple glossary entries, ensuring machine-parseable data consistency and validation across every generated file without manual formatting errors.

Why does manual structured data file creation fail?▼

Manual structured data file creation fails because it is error-prone and inconsistent, lacking the automated template-driven enforcement of METADATA, CONTENT, and CLOSING blocks needed for reliable machine-parseable output.

Does this data generation approach work for mapping files?▼

Yes, this template-driven data generation approach works for mapping files by applying the uniform 3-block structure and validation to ensure consistency across configs, glossaries, and mappings.