op-bucket-routerlisted

Use as the fallback router when the user's task isn't covered by any other core `op-*` skill — checks the user's personal bucket library (`~/.achron-spine/bucket/INDEX.md`, which has both a Skills table and a Chapters table) for a matching entry and loads only the matched file. Fires when another router would normally handle the task but no core chapter covers it (project-specific recipe, stack-specific pattern, user's personal convention, reference for their own architecture), or the user says "do this the way I usually do" / "use my X skill" / "check my bucket" / "is there anything in my chapters about this?". Never invents bucket entries — only routes to existing ones — and never fires on the `/bucket curate` or `/bucket suggest` slash commands (those are op-curate / op-suggest).
TimTGelhard/ACHRON-spine · ★ 1 · API & Backend · score 74

Install: claude install-skill TimTGelhard/ACHRON-spine

# op-bucket-router — personal library fallback The bucket holds the user's *personal* library — both **skills** (procedures fired on a trigger) and **chapters** (references loaded for context). This skill is the router into both tables. Core skills always win — this fires only when none of them matched. ## Bucket-loop gate Read `~/.claude/achron-spine-profile.md` `## Spine defaults` → `Bucket loop:`. If `off`: - Implicit fallback fires (no core skill matched) → silent skip; treat as "no bucket support" and answer from the spine + chapters alone. - Explicit user request ("use my bucket", "do this the way I usually do") → still route. The user knows the bucket exists; honor the ask one-shot. The profile setting changes the *automatic fallback* behavior, not explicit invocation. Default if the field is absent: `off` (the audit-recommended default after the round-6 flip — a user who never ran `/onboard` shouldn't have implicit bucket fallback firing on every uncaught task; explicit invocation still works). ## When this fires - No core `op-*` skill matched the user's task **and** the task looks like it could be a learned pattern or a personal reference (project recipe, stack-specific deploy, user's personal review style, "how does my X work"). - The user explicitly says: "use my bucket," "do this the way I usually do," "check my X skill," "is there a skill for this?," "anything in my chapters about Y?" - Before recommending a new skill or chapter to a user, check whether on