Agent skill · yeachan-heo
harbor
Harbor intake for external work — the captain only handles unresolved decisions. Sweeps incoming issues and PRs, verifies every claim before disposition, reuses every decision already made, and hands the maintainer a docket whose pending items each carry one question with options, recommendation, impact and evidence. Agent-autonomous for facts and for actions covered by standing authorization; signed for every new judgment. Never merges.
What it needs
About 11k tokens when loaded.
What this skill does
Harbor Harbor is the shipyard's intake. External requests — issues, bug reports, feature requests, and (when enabled) external PRs — arrive as raw noise. Harbor turns that noise into evidence, proposals, signed decisions, and authorized executions, so that the captain only ever handles what is genuinely unresolved: a new tradeoff, a new exception, a new authority. Success order. First: zero overreach — nothing happens that nobody authorized. Second: fewer captain judgments and less reading — without skipping ships, auto-rejecting, or parking forever. The four records Every harbor action produces one of four records. They are kept in the tracker itself (comments, labels, links) — the tracker is the only record source; the docket is an index, not a store. Record Minimal content --- --- Verification (evidence) link to the issue/PR and relevant comments; inspection time; head/base or target version; command or method; actual result; what was not verified and why it matters Proposal one explicit question; recommendation and alternative; the exact object set in scope; scope and non-goals; linked evidence; the proposed action; link to harbor's own comment Decision the authorizing party and a verifiable source; what was decided; link to the signed proposal; applicable conditions; allowed actions; which prior decision it follows or supersedes Execution result reference to the authorization and the input version; what was actually done; failures or unknown outcomes; next responsible party if any. Receipt links must reference verified, existing tracker comments — a draft's ID is not a receipt; verify the comment exists before citing it Not every record is its own comment: one consolidated verification comment may cover a sweep, and a decision may carry a combined execution receipt. When a signed proposal materially changes, post a new snapshot that names what it supersedes — never silently edit what was signed. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills yeachan-heo/harbor