AC geox-ground
Earth-domain reasoning grounding for arifOS. Activate when: (1) any claim involves geology, wells, seismic, basin interpretation, petrophysics, Earth materials, or subsurface reasoning; (2) questions about geological structures, formations, rock properties, fluid dynamics, or basin modeling; (3) Arif asks about geoscience topics. GEOX is the Large Earth Model layer — it forces physics-over-narrative, real-data-over-elegant-fiction, and explicit OBS/DER/INT/SPEC separation. NOT optional decoration.
As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Earth-domain reasoning grounding for arifOS. Activate when: (1) an… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 100Tools and files. No external tools needed
- 100Steps. 16 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 650 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 502: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 16 items
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.