edition-data-author

Create and validate Shadowrun edition catalog items in JSON with kebab-case IDs.

1|1|Updated Nov 14, 2025
One-click install
npx skills add https://github.com/Jasrags/ShadowMaster --skill edition-data-author
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: edition-data-author
Source: https://github.com/Jasrags/ShadowMaster/tree/main/.claude/skills/edition-data-author
Command: npx skills add https://github.com/Jasrags/ShadowMaster --skill edition-data-author

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams create and validate catalog items for Shadowrun edition JSON files, ensuring consistent IDs, categories, and references across editions.

Core Features & Use Cases

  • Generate new catalog entries for spells, qualities, gear, augmentations, weapons, armor, and complex forms.
  • Validate existing core-rulebook.json or sourcebook JSON to ensure naming conventions and reference integrity (e.g., IDs, category slugs, page references).
  • Integrate with the edition data workflow to enforce kebab-case identifiers and YAML frontmatter presence.

Quick Start

Run the edition data author workflow to scaffold a new catalog item and run the validation step on the targeted data file.

Frequently Asked Questions about edition-data-author

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

FAQPage Schema
How do I validate Shadowrun edition JSON catalog items?

Generate Shadowrun edition catalog entries by running the data author workflow to scaffold new items for spells, qualities, gear, weapons, armor, foci, and complex forms. It ensures proper kebab-case IDs and required fields like name and description.

Why does my edition data validation fail on naming conventions?

YAML frontmatter is required in Shadowrun edition catalog items to ensure consistent metadata structure across the JSON data. The validation workflow checks for its presence alongside required name and description fields.

What's the best way to audit existing Shadowrun sourcebook JSON files?

Validate Shadowrun edition JSON for SR5 and other editions by applying the data author workflow to existing core-rulebook or sourcebook files. It audits spells, qualities, gear, augmentations, weapons, armor, foci, and complex forms.

How do I scaffold a new catalog entry for Shadowrun spells or gear?

Scaffold a new catalog entry for Shadowrun spells or gear by running the edition data author workflow. It generates items with proper kebab-case IDs, required name and description fields, and YAML frontmatter for the /data/editions JSON.

Does the edition data workflow support both SR5 and other Shadowrun editions?

The edition data workflow supports both SR5 and other Shadowrun editions by applying consistent validation rules to the /data/editions JSON. It enforces kebab-case identifiers and reference integrity across all supported edition types.

What required fields must Shadowrun edition catalog items include?

Shadowrun edition catalog items must include required fields name and description, along with YAML frontmatter and kebab-case IDs. The validation workflow enforces these fields to maintain consistent catalog data across editions.