register-install

Installs the register-check tool into a repository pinned to the tagged git ref the register names.

1|Updated Aug 16, 2026
One-click install
npx skills add https://github.com/Eaiger-Ent/ee-standard --skill register-install-eaiger-ent
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: register-install
Source: https://github.com/Eaiger-Ent/ee-standard/tree/main/plugins/control-register/skills/register-install
Command: npx skills add https://github.com/Eaiger-Ent/ee-standard --skill register-install-eaiger-ent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml.

What problem does it solve? Repositories adopting the ee-standard control register need the register-check executable present before any gate, pre-commit hook, or CI job can run it, but nothing else in the plugin installs it. This Skill adds register-check as a pinned git dependency so every locus that invokes the checker has something to run. ## Core Features & Use Cases - Register-driven pinning: Composes the dependency requirement entirely from the register's tools.register-check.install address and the ecosystem's git_dependency grammar, never hardcoding a URL or tag. - Ecosystem detection from files: Determines the package ecosystem by inspecting manifests and lockfiles (pyproject.toml, uv.lock, package.json, go.mod) rather than asking the user. - Safe, confirmed installs: Shows a plan and asks for confirmation before writing, handles new installs, no-op re-runs, and upgrades distinctly, and verifies via the package manager runner plus lockfile inspection. - Use Case: While adopting the control register into a Python repository, run this Skill so the pre-commit hooks and CI job that call register-check resolve against a pinned, locked version. ## Quick Start Ask the assistant to install the register-check checker into this repository using the register-install skill, pinned to the ref named in controls.yaml.

Frequently Asked Questions about register-install

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

FAQPage Schema
How do I install register-check into my repository?▼

Run the register-install skill, which reads the repository address and tag from controls.yaml, adds register-check as a pinned dev dependency via your package manager (for example uv add --dev), updates the lockfile, and verifies the version through the package manager runner.

Why is register-check pinned to a git tag instead of a branch?▼

A branch-pinned git dependency resolves to whatever the default branch contains at run time, so the checker could change between two runs of one commit. Pinning to a tag keeps the version frozen until someone reviews a deliberate ref change.

Can I install register-check in a non-Python repository?▼

Not currently. Only the python ecosystem declares a git_dependency grammar in the register, so the skill stops and reports that no spelling exists for other ecosystems rather than inventing one. The non-Python adopter case is a known open limitation.

What happens if I re-run the checker installation?▼

Re-running is safe and idempotent. If the pin already matches the register's ref, nothing is written and the version is still verified; if a different ref is pinned, the skill treats it as an upgrade and names both refs in the plan.

Why does register-install not run the full audit afterwards?▼

Running register-check over a repository with no gates deployed reports failures for every control, which misleadingly looks like the install broke something. The full audit is run by register-adopt as its starting state, where that output is meaningful.