Imlazy bootstrap

Skill hnikoloski/imlazy/skills/imlazy-bootstrap

Token-efficient tier-routed agent orchestrator 40+ skills, 19 agents, Obsidian vault. Works with Claude Code, OpenCode, Codex CLI.

Install

npx -y skills add hnikoloski/imlazy --skill imlazy-bootstrap

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

26 days oldThe repository was created 26 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Bootstrap skill loaded on every session — detects /imlazy and "i am lazy" triggers, routes through imlazy-router for tier-aware execution

SKILL.md

2.1 KB, as published. Nobody here has run it

imlazy-bootstrap

Triggers

When the user message starts with /imlazy <task> or i am lazy, <task> (at the start of a message or as a clear prefix), invoke Skill(imlazy-router) with the task description.

Additionally, detect VAULT triggers: "vault init", "vault save", "vault search", "create vault" — route these to Skill(imlazy-router) for vault-tier classification.

Do NOT trigger on "i am lazy" appearing mid-paragraph or without an actionable verb (e.g., "i am lazy and tired today" is not a trigger — no action to route).

The slash command /imlazy is a hard trigger. The chat phrase requires a clear actionable ask.

The 1% rule

If a skill might apply to what you are doing, invoke it before responding. After triggering, the router decides which workflow skills to load — you do not need to pre-load anything yourself.

Instruction priority

User instructions in CLAUDE.md / AGENTS.md take precedence over imlazy skills, which take precedence over default system behavior. The router never overrides explicit user requests — if the user says "skip the plan", honor it.

Quick-tier completion gate

For Quick-tier tasks (classified as such by imlazy-router), before claiming completion:

Run the relevant verification command — test suite, build, or git diff for content-only edits.
Confirm exit code 0 and the intended change is present in the output.
If verification passes: claim completion, you are done.
If verification fails: do NOT claim completion. Escalate to Standard tier:
- Invoke Skill(imlazy-tdd) and Skill(imlazy-planning) (light mode).
- Invoke Skill(imlazy-learn) with predicted=quick, actual=standard, and a 50-char task summary.
- Continue with the broader skill set loaded — do not restart the task from scratch.

What this skill does not do

This bootstrap deliberately omits red-flags tables, rationalization lists, and workflow philosophy — those live in the tier-specific skills, loaded lazily by the router.