BF semantic-spacetime
Model and analyze Semantic Spacetime (SST) graphs, distances, trajectories, drift, and model files. Do not use this skill for promise-theory vocabulary and fundamentals without SST modeling; use `promise-theory` for the substrate concepts.
Model and analyze Semantic Spacetime (SST) graphs, distances, trajectories, drift, and model files.
As a process F 50/100 · Will not run — References files that are not bundled: ../promise-theory/SKILL.md, ../agent-evals-and-observability/SKILL.md, ../agent-council/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../promise-theory/SKILL.md - warning
missing-refreference to a missing file: ../agent-evals-and-observability/SKILL.md - warning
missing-refreference to a missing file: ../agent-council/SKILL.md - warning
missing-refreference to a missing file: ../workflow-architect/SKILL.md - warning
missing-refreference to a missing file: ../artifact-pyramids/SKILL.md - warning
missing-refreference to a missing file: ../agent-skills/SKILL.md - warning
missing-refreference to a missing file: ../cli-builder/SKILL.md - warning
missing-refreference to a missing file: templates/sst-model.yaml.tmpl - warning
missing-refreference to a missing file: templates/sst-analysis.md.tmpl
Process rating: all ten parameters 50/100
- 0Tools and files. 9 referenced file(s) missing: ../promise-theory/SKILL.md, ../agent-evals-and-observability/SKILL.md, ../agent-council/SKILL.md
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 7 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 31 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3516 tokens
- low 10 top-level sections: this looks like several domains in one skill
- medium 6 test cases, all positive: not one "should refuse" or "should ask first"
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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 239: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 31 items
- +4Has examples (0 code blocks)
- +4Reference files are cited in the instructions (7 of 7)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.