plugin-options-schema-author

Enforce shared optionsSchema and uiSchema contracts across kanban-lite providers.

5|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/borgius/kanban-lite --skill plugin-options-schema-author
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-options-schema-author
Source: https://github.com/borgius/kanban-lite/tree/main/.agents/skills/plugin-options-schema-author
Command: npx skills add https://github.com/borgius/kanban-lite --skill plugin-options-schema-author

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes and maintains consistent plugin options schemas across kanban-lite providers, preventing drift in options, uiSchema, and secret metadata.

Core Features & Use Cases

  • Centralizes schema ownership for plugin options and UI metadata to ensure a single source of truth.
  • Applies across provider exports, UI panels, SDKs, CLI tools, and tests, with documented workflows.
  • Use Case: When updating a provider, run this skill to align optionsSchema metadata, ensure secret masking, and propagate changes to docs and tests.

Quick Start

Create or update the shared Plugin Options schema for a provider using kanban-lite.

Frequently Asked Questions about plugin-options-schema-author

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

FAQPage Schema
How do I standardize plugin options schemas across multiple providers?

To standardize plugin options schemas across multiple providers, enforce a shared optionsSchema and uiSchema contract that aligns schema definitions, UI metadata, and secret field masking. This ensures uniform behavior and configuration consistency.

What is a uiSchema contract for plugin settings editors?

A uiSchema contract for plugin settings editors defines how JSON Forms render optionsSchema fields in the UI. It aligns UI components with schema validation rules to ensure consistent configuration interfaces across different providers.

How do I prevent schema drift when updating kanban-lite provider options?

Prevent schema drift when updating kanban-lite provider options by centralizing schema ownership through a single source of truth. Run schema alignment checks to propagate optionsSchema updates, ensure secret masking, and update documentation and tests.

Does this schema validation approach support secret field metadata masking?

Yes, this schema validation approach supports secret field metadata masking. It aligns secret metadata within the optionsSchema and uiSchema contracts to ensure sensitive configuration values are properly masked across provider exports and UI panels.

Can I use JSON Forms provider options with this schema standardization method?

Yes, you can use JSON Forms provider options with this schema standardization method. It specifically enforces a shared optionsSchema and uiSchema contract designed to support schema-driven plugin settings editors built on JSON Forms.

What are the limitations of manually maintaining optionsSchema and uiSchema across providers?

Manually maintaining optionsSchema and uiSchema across providers introduces configuration drift, breaks secret metadata masking consistency, and desynchronizes documentation and tests. Enforcing a shared contract mitigates these issues by centralizing schema ownership.