skills/meeting-chair-support/SKILL.md
--- name: meeting-chair-support version: 1.0.0 category: governance owner: gmx sot: /Users/icmini/0luka/skills/meeting-chair-support/SKILL.md status: draft governance_mode: bounded mandatory_read: - /Users/icmini/0luka/core_brain/governance/AGENTS.yaml - /Users/icmini/0luka/CONTRACT.yaml - /Users/icmini/0luka/skills/manifest.md capabilities: - speaking_order_support - drift_detection - closure_rule_support - escalation_recommendation - bounded_reply_constraints triggers: - acti
npx skillsauth add ic1558/0luka meeting-chair-supportInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill to support a live meeting chair (Boss, GG, or CLC) by monitoring discussion flow, enforcing reply constraints, and providing signals for topic closure.
This skill helps the chair. It does not replace the chair.
GMX acts as the Chair Support and Drift Detector. GMX does not assume the chair's decision authority unless explicitly delegated.
Confirm who holds decision authority:
Examples:
Put the highest-leverage evidence holders first.
Detect:
For each topic, tell the chair:
Return only:
GMX supports and assists the chair. The chair remains the sole sovereign decision-lock.
End of Document
development
--- name: auto-workflow-creator description: Create a new skill from a workflow you just performed. Generates a valid 3-layer Anthropic-style skill — YAML frontmatter (name + description + triggers), imperative instruction body, and optional scripts/ subdirectory — and prints the registration commands per target runtime (Claude Code auto-discovers from ~/.claude/skills/; Codex needs an explicit [[skills.config]] entry in ~/.codex/config.toml; OpenCode needs a registry entry in ~/.opencode/openco
tools
# Cost-Control Skill Enforce token discipline and model routing optimization (Flash vs Pro) via the Gemini CLI 0.40 Gemma local router for governed-agent workflows. ## Guidelines - **Preference for Local/RTK/File Tools:** Always prioritize local tools (ls, read_file, grep_search) and RTK for initial data gathering before calling model logic. - **Flash-First Routing:** - Route all routine code analysis, file reads, summarization, search, and classification tasks to `gemini-3.5-flash-preview` o
development
--- name: verify-first description: Run verification gates before and after code changes, prioritize health and regressions, and fail closed on missing evidence. Mandatory Read: YES --- # Verify First Mandatory Read: YES ## Workflow 1. Capture baseline verify results. 2. Apply minimal changes. 3. Re-run targeted and system-level verify commands. 4. Report explicit pass/fail evidence. ## Caps - Run deterministic verification commands. - Compare before/after outcomes. - Block claims without pr
testing
Use this skill when you need to perform a READ-ONLY forensic validation of a completed task (evidence), verify compliance against a TaskSpec, or issue a formal verdict (PASS/FAIL) before GMX approval. Strictly forbids modification or execution.