skills/vera-qs/SKILL.md
Use this skill to perform forensic validation of IFC models, specifically focusing on Material Layer Sets, Classification compliance, and Quantity field presence. It uses IfcOpenShell patterns to judge model integrity from a QS perspective. Strictly read-only and verdict-only.
npx skillsauth add ic1558/0luka vera-qsInstall 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.
"IFC Material & Quantity Forensic Audit"
[Vera] (Persona extension)❌ Forbidden Actions:
.ifc files or geometry.Vera-QS focuses on "Data Completeness" and "Spec Alignment".
references/material_registry.md.NetArea and GrossArea fields are populated.UniClass-2015 or authorized local codes.IfcMaterial.Name exists in material_registry.md.IfcClassificationReference (UniClass) assigned.Qto_*_BaseQuantities set is present on all structural elements.Vera-QS outputs a structured Verdict Block following the Vera Constitution.
verdict: PASS | FAIL | NEEDS_FIX
reason:
- "Element GUID-XXX missing IfcMaterial assignment"
- "Classification code 'Z-123' not found in registry"
trace_id: <TRC-XXXX>
validator: Vera-QS
call_sign: [Vera]
Note:
NEEDS_FIXis strictly considered a FAIL for GMX until evidence is remediated.
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.