bgsd-context-init

Validate the bGSD context block and parse required JSON fields.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/gonz0w/bgsd-oc --skill bgsd-context-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bgsd-context-init
Source: https://github.com/gonz0w/bgsd-oc/tree/main/skills/bgsd-context-init
Command: npx skills add https://github.com/gonz0w/bgsd-oc --skill bgsd-context-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and validates the standard initialization preamble used by all bGSD workflows, ensuring the <bgsd-context> block is present, auto-injected by the plugin, and parsed consistently to avoid duplication.

Core Features & Use Cases

  • Centralized 2-paragraph preamble used across all workflows to detect the context block and display a uniform error if missing.
  • Shared JSON parsing pattern that standardizes how workflow fields are extracted from context.
  • After the <skill:bgsd-context-init /> tag, individual workflows can specify their own field lists as needed.

Quick Start

Add the <skill:bgsd-context-init /> tag to initialize workflows with the shared preamble.

Frequently Asked Questions about bgsd-context-init

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

FAQPage Schema
How do I standardize workflow initialization context across multiple plugins?

To standardize workflow initialization context, use a centralized preamble that detects and validates a shared JSON context block before parsing. This ensures all workflows apply a uniform parsing pattern and display a common error message if the block is missing.

Why does my workflow fail to parse required fields from the startup JSON block?

Workflow JSON parsing fails when the auto-injected context block is missing or not detected by the initialization preamble. Enforcing a standardized detection pattern ensures required fields are consistently extracted from the shared JSON block during startup.

How do I display a uniform error message when a shared JSON context block is missing?

To display a uniform error message for a missing JSON context block, implement a centralized initialization preamble that validates the block's presence. This enforces consistent detection and prevents duplication across all dependent workflows.

Can I specify custom required fields after applying a shared workflow initialization pattern?

Yes, you can specify custom required fields after applying a shared initialization pattern. Once the standardized preamble detects and validates the shared JSON context block, individual workflows can define their own specific field extraction lists.

What is the best way to avoid duplicating initialization logic across multiple workflows?

The best way to avoid duplicating initialization logic is to centralize the validation and parsing of the shared JSON context block. A single preamble tag enforces consistent block detection and field extraction across all workflows without repeating the startup code.