canonical-ops-template

Establish a canonical governance template for CTOX ops skills.

2|Updated Apr 12, 2026

Search Tags:#refinement #sqlite #governance #boundaries #canonical-template #ctox #ops-skill

Ready to run

npx skills add https://github.com/metric-space-ai/ctox --skill canonical-ops-template

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: canonical-ops-template
Source: https://github.com/metric-space-ai/ctox/tree/main/skills/system/skill_meta/canonical-ops-template
Command: npx skills add https://github.com/metric-space-ai/ctox --skill canonical-ops-template

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Canonical governance and templating for CTOX ops skills to ensure consistent definitions, boundaries, and durable evidence handling across the skill family.

Core Features & Use Cases

enforces a shared SQLite kernel boundary by skill_key
provides a skeleton layout (SKILL.md frontmatter, purpose, boundaries, operating model, guardrails, resources)
guides refinement with a clear escalation and invariants framework for safe evolution
supports non-execution governance when creating or updating ops-skill families

Quick Start

Follow this canonical template when creating or updating any CTOX ops skill to maintain consistency and inspectability.

Frequently Asked Questions about canonical-ops-template

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

FAQPage Schema

How do I standardize ops skill structure and runtime invariants across a family of skills?▼

A canonical governance template solves ops skill consistency by providing a standard skeleton layout, enforcing a shared SQLite kernel boundary by skill_key, and applying an operator-facing contract for safe evolution and refinement.

What is the best way to enforce consistent boundaries when creating new ops skills?▼

The best way to enforce consistent boundaries is applying a canonical template that mandates explicit skill separation and one shared SQLite kernel, ensuring durable evidence handling and inspectability across the skill family.

How does the shared SQLite kernel boundary work within a governance template?▼

The shared SQLite kernel boundary works by partitioning data access through a unique skill_key for each ops skill, preventing cross-skill interference while maintaining a unified evidence handling and governance standard.

Can I use this canonical template for non-execution governance and refinement workflows?▼

Yes, you can use this canonical template for non-execution governance to guide safe skill refinement, providing a clear escalation and invariants framework for updating ops-skill families without runtime execution.

What limitations should I consider when standardizing ops skills with a canonical template?▼

Limitations include strict adherence to the shared SQLite kernel boundary by skill_key and the mandated skeleton layout, meaning any ops skill refinement must conform to the explicit guardrails and cannot bypass the governance contract.