optimization-compass-maintenance

Maintains Optimization Compass knowledge, data, and GitHub Pages releases through validated canonical workflows.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/mryk814/optimization-compass --skill optimization-compass-maintenance-mryk814
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: optimization-compass-maintenance
Source: https://github.com/mryk814/optimization-compass/tree/main/.agents/skills/optimization-compass-maintenance
Command: npx skills add https://github.com/mryk814/optimization-compass --skill optimization-compass-maintenance-mryk814

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintaining the Optimization Compass repository requires editing canonical knowledge sources without corrupting generated artifacts, breaking stable entity IDs, or silently changing dataset releases. This Skill enforces the correct authority files, evidence rules, and validation tiers for every change type. ## Core Features & Use Cases - Task Classification: Routes every request into one of eight classes (prose correction, content addition, Gallery case, comparison, problem instance, canonical entity, visualization scenario, or release/publishing) with a matching recipe. - Invariant Enforcement: Blocks hand-editing of generated outputs such as knowledge.sqlite, site/public/data, and release files, and requires authoritative sources for factual claims. - Tiered Validation: Prescribes Tier A/B/C validation commands (pytest, ruff, mypy, site builds, Playwright E2E) matched to change risk. - Use Case: When adding a new optimization method article or publishing a dataset release to GitHub Pages, follow the recipes to edit only canonical inputs, regenerate projections, and verify deployment identity with the pages checkpoint script. ## Quick Start Ask the assistant to add a new Gallery case to the Optimization Compass repository following the maintenance skill's recipe and validation tier.

Frequently Asked Questions about optimization-compass-maintenance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new optimization method to the Optimization Compass dataset?▼

Follow Recipe F: confirm identity and aliases, add source rows first, then add canonical rows and relations in a dedicated migration registered in dataset_release.py. Add content, focused tests, and run the full Tier B validation suite.

How do I publish the Optimization Compass site to GitHub Pages?▼

Use Recipe H after explicit authorization: run scripts/pages_checkpoint.py, batch changes, regenerate all projections, build the site, run local E2E gates, push once, and verify the deployment with --require-published.

Can I edit generated files like knowledge.sqlite or site/public/data directly?▼

No. Generated authority outputs must never be hand-edited. Fix the canonical inputs and regenerate using the prescribed build commands, then inspect the git diff of generated files.

What validation tier is required for adding a Gallery case?▼

Gallery cases require Tier B validation: ruff, mypy, pytest, verify-data, content and licensing checks, staged dataset rebuild, site parity, unit tests, and a production site build.

When should the maintenance workflow stop and report instead of editing?▼

Stop when a new ID namespace is needed, an authoritative source is unavailable, entities may be duplicates, migration ordering is unclear, or only generated files appear editable. Report the unresolved decision rather than inventing values.