smithery.ai

mechanics-check

Audit SENTINEL game data integrity. Validates regions, jobs, vehicles, and favors against schema enums.

First seen Apr 12, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsBash, Read, Glob, Grep

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,089 B
  • docs SUMMARY.md 126 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Mechanics Integrity Check

Validate SENTINEL game data consistency to catch bugs before they surface during play.

When to Use

  • After modifying regions.json, job templates, or favor costs
  • Before committing game data changes
  • When adding new factions, regions, or mission types
  • After updating schema enums
  • Periodic health checks on game data

How to Run

Quick Check (Recommended)

Run the validation script directly:

python C:/dev/SENTINEL/sentinel-agent/scripts/check_mechanics.py

JSON Output (for CI/automation)

python C:/dev/SENTINEL/sentinel-agent/scripts/check_mechanics.py --json

Present Results

Format the output as an actionable checklist:

## Mechanics Health Report

### Status: [HEALTHY | NEEDS ATTENTION | BROKEN]

### Issues Found
- [ ] Issue 1 (ERROR) — must fix
- [ ] Issue 2 (WARNING) — should investigate
- [ ] Issue 3 (INFO) — informational

### Recommendations
- ...

What It Checks

Regions (data/regions.json)

  • All 11 Region enum values have entries
  • primaryfaction and contestedby reference valid faction IDs
  • adjacent lists contain valid region IDs
  • Adjacency is bidirectional (if A→B then B→A)

Jobs (data/jobs/*.json)

  • faction matches FactionName enum (display names)
  • type matches MissionType enum
  • region (if present) matches Region enum
  • opposing_factions contain valid faction names
  • requiresvehicletags exist in at least one vehicle
  • requiresvehicletype matches actual vehicle types

Vehicles (tuicommands.py VEHICLEDATA)

  • All job-required tags exist in at least one vehicle
  • Reports orphan tags (defined but not used by any job) as INFO

Favors (systems/favors.py)

  • All FavorType values have costs defined
  • All Disposition levels have favor mappings and cost modifiers

Severity Levels

Severity Meaning Action
ERROR Breaks game functionality Must fix
WARNING Inconsistency that may work Should investigate
INFO Suggestion or design note Optional

Exit Codes

Code Meaning
0 All checks passed (HEALTHY)
1 Warnings only (NEEDS ATTENTION)
2 Errors found (BROKEN)

Tips

  • Run after any schema.py changes that add/remove enum values
  • The check is read-only — it never modifies files
  • JSON output can be filtered with jq:

``bash python check_mechanics.py --json | jq '.issues[] | select(.severity == "error")' ``

  • Orphan vehicle tags (INFO) are not bugs — they're future-proofing for jobs not yet written

Data Sources

Data Location
Schema enums src/state/schema.py
Regions data/regions.json
Jobs data/jobs/*.json
Vehicles src/interface/tui_commands.py
Favors src/systems/favors.py