ic1558/minutes-recorder
skills/minutes-recorder/SKILL.md
--- name: minutes-recorder version: 1.0.0 category: governance owner: gmx sot: /Users/icmini/0luka/skills/minutes-recorder/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: - decision_register - owner_mapping - accepted_vs_rejected_capture - unresolved_gap_capture - evidence_trace_recording triggers: - meeting_completed
development
Updated Apr 22, 2026
$ install --global
skillsauthnpx skillsauth add ic1558/0luka minutes-recorderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 8:02 PM29.6s1 file scanned
SKILL.md
- name:
- minutes-recorder
- version:
- 1.0.0
- category:
- governance
- owner:
- gmx
- sot:
- /Users/icmini/0luka/skills/minutes-recorder/SKILL.md
- status:
- draft
- governance_mode:
- bounded
minutes-recorder
Purpose
Use this skill to record meeting outcomes (Locked Decisions) in a way that is usable for governance, follow-up, and later WO conversion.
This skill records decisions, not transcript.
Role
GMX acts as the Recorder and Outcome Tracker. GMX does not assume the authority to change the locked outcomes during recording.
When To Use
- A meeting has concluded.
- Decision points were locked by the chair.
- Paths were accepted/rejected/deferred.
- Owners must be recorded.
When Not To Use
- Informal brain-dumps with no concrete decisions.
- Internal agent-to-agent chatter without governance significance.
Workflow
Step 1 — Record metadata
Capture:
- meeting objective
- date/time
- chair
- attendees
- evidence surfaces used
Step 2 — Record each topic
For each topic, record:
- decision question
- evidence considered
- accepted position
- rejected position
- unresolved gap if any
Step 3 — Record owner map
Capture:
- who verifies
- who executes
- who signs off
Step 4 — Record next artifact
For each accepted decision, state:
- WO
- policy update
- repo fix
- parked note
- no action needed
Output Format
Return only:
- meeting metadata
- decision register
- rejected paths
- unresolved items
- owner map
- next artifacts
Failure Modes
- becomes transcript dump.
- no clear accepted/rejected split.
- no owners.
- no next artifact.
- minutes too vague for follow-up.
Boundary Rule
GMX prepares and records the outcomes. The chair remains the final authority on what was "locked."
End of Document
Related Skills
ic1558/skills/auto-workflow-creator
development
VerifiedTrustedCommunity
--- 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
SKILL.mdUpdated May 27, 2026
ic1558/skills/cost-control
tools
VerifiedTrustedCommunity
# 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
SKILL.mdUpdated May 1, 2026
ic1558/skills/verify-first
development
VerifiedTrustedCommunity
--- 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
SKILL.mdUpdated Apr 19, 2026
ic1558/vera
testing
VerifiedTrustedCommunity
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.
SKILL.mdUpdated Apr 19, 2026