config-seeder

Seed JSON config files into workflow tables for session startup.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/mehdic/CDC --skill config-seeder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: config-seeder
Source: https://github.com/mehdic/CDC/tree/main/.claude/skills/config-seeder
Command: npx skills add https://github.com/mehdic/CDC --skill config-seeder

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It seeds the necessary workflow configuration data (transitions, markers, rules) into the database at session initialization, ensuring consistent routing and gating from the first spawn.

Core Features & Use Cases

  • Seeds transitions, agent markers, and special rules into the database
  • Intended to run once at session start to bootstrap orchestration behavior
  • Ensures consistent, testable routing without manual DB edits

Quick Start

Run the seeder to populate the database with all transitions, markers, and rules before spawning any agents.

Frequently Asked Questions about config-seeder

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

FAQPage Schema
How do I seed workflow configuration into the database at session startup?

Seed workflow configuration by running the seeder to populate workflow_transitions, agent_markers, and workflow_special_rules tables from JSON config files before any agents spawn. This initializes routing, markers, and rules consistently without manual database edits.

What configuration data does the seeder populate?

The seeder loads JSON configuration files and writes three database tables: workflow_transitions for routing logic, agent_markers for agent gating, and workflow_special_rules for conditional behavior. It reports exact counts on success or error messages on failure.

When should I run the seeder in my workflow?

Run the seeder exactly once before spawning any agents to bootstrap orchestration behavior. It must execute during session initialization when the database is pre-initialized and config files are accessible or available as dev-mode symlinks.

What do I need before using the seeder?

You need a pre-initialized database and accessible JSON configuration files containing transitions, markers, and rules. Dev-mode symlinks are supported as an alternative to direct file paths.

Can I use the seeder to update existing workflow rules?

The seeder is designed for initial bootstrapping at session startup, not for runtime updates. It seeds the full configuration once to establish consistent routing and gating from first spawn.