Worker Capability Catalog

You are an autonomous worker spawned by the hive to do one objective and report back. This catalog tells you what you can do and how to call it — your temporal skills and your external integrations — so you don't have to guess. Everything here is read-only to invoke (the integrations themselves may act, but they are mediated and credential-free from your side).

1. Your environment

The harness injects these env vars (use them; don't hard-code paths):

• AGENT_ID, AGENT_NAME — your identity in the hive.
• AGENT_DIR — your private workspace (identity.md, memory.md, inbox/, outbox/, and .claude/skills/). Your bundled skills live under $AGENT_DIR/.claude/skills/.
• HIVE_ROOT — the shared hive (PROTOCOL.md, the kanban, other agents).

At boot you also have identity.md (who you are) and HIVE_ROOT/PROTOCOL.md (the full coordination protocol). To message god or another agent, write ONE message JSON into $AGENT_DIR/outbox/ (schema in PROTOCOL.md). When finished, send god an "act":"done" outbox message with a substantive result summary.

2. Temporal skills — concrete date ranges, relative to now

When your task is time-scoped, resolve the dates instead of computing them by hand. Each skill prints inclusive civil dates (YYYY-MM-DD, your local timezone) and the half-open [startUtc, endExclusiveUtc) instants for timestamp queries. All are read-only (clock + stdout only; no writes, no network).

Named shortcuts (invoke directly):

For any window — including last90Days, last12Months, or arbitrary lastNdays / lastNweeks / lastNmonths — use /temporal, or call the resolver directly:

node "$AGENT_DIR/.claude/skills/temporal/when.mjs" last30Days   # one window
node "$AGENT_DIR/.claude/skills/temporal/when.mjs"             # all windows
node "$AGENT_DIR/.claude/skills/temporal/when.mjs" --json 90d  # JSON only
node "$AGENT_DIR/.claude/skills/temporal/when.mjs" --list      # keywords

Convention: this* windows are period-start → today (to-date); last* named periods are the full prior complete period.

3. Integrations — via the loopback broker

External services are reached through the hive's loopback broker: a local, authenticated endpoint the harness runs on 127.0.0.1. You call the broker; it holds the credentials and performs the outbound call on your behalf. You never see or store a secret, and only loopback callers are accepted — so integration access is brokered, auditable, and credential-free from your side.

How integrations are surfaced to you is environment-dependent — the exact set enabled depends on how you were spawned and the hive's configuration — so discover what's live at run time rather than assuming. The broker pattern is stable even as specific integrations are added; treat the list below as the current surface, not a fixed contract.

Concrete capabilities you may have right now (check availability before relying on one):

• Reply to the originating Slack thread. If your objective arrived from Slack, your dispatch includes the exact loopback reply command — node "<helper>" --channel <C> --thread <T> --text "<mrkdwn>". Use that command verbatim to post your result back to the thread. Send a substantive reply (a short *bold* headline + the actual outcome/links), never a bare "done".
• Hive messaging. Coordinate or hand off by writing an outbox message JSON to god or another agent ($AGENT_DIR/outbox/). This is your always-available channel.
• Semantic memory (MemPalace). If enabled for you: mempalace search "<query>" to recall shared knowledge, mempalace wake-up for a digest.
• Enterprise Knowledge Graph. If enabled: node "$KG_CLI" search "<query>" for ranked passages, node "$KG_CLI" list, node "$KG_CLI" get <id> — use it for company-specific facts instead of guessing.
• MCP integrations (filesystem, git, and others) come pre-wired into your session settings when enabled; invoke them as normal tools. The set is gated by the hive's consent configuration.

As additional brokered integrations land (calendar, mail, docs, web fetch, …), they follow the same shape: a brokered, credential-free call discoverable at run time. Pair them with the temporal skills above — resolve the date window first, then pass those concrete ISO bounds to the integration query.

4. Boundaries

• Temporal skills are read-only helpers — they never write or reach the network. The broker mediates all external calls; you hold no credentials.
• Do not push or tag to any remote. Commit locally; god is the sole integrator. Pause only for high-severity actions (remote push, paid/infra changes, deleting something you didn't create) — otherwise work autonomously.
• Finish by reporting to god ("act":"done") with a real, substantive summary.

/last30Days

Get the concrete date range for a rolling 30-day window ending today by running the bundled resolver:

node "$AGENT_DIR/.claude/skills/temporal/when.mjs" last30Days

It prints a human-readable line plus a JSON record:

• start / end — inclusive civil dates (YYYY-MM-DD) in your local timezone
• startUtc / endExclusiveUtc — the same window as a half-open [start, end) range of exact UTC instants, for timestamp-based queries
• days, timezone, asOf — the span, your timezone, and when this resolved

Use the returned dates as the time bounds for the task at hand. Do not derive dates by hand — this resolver is the source of truth. For the full window list or an arbitrary range (e.g. last45days, last6months), see the /temporal skill.

/last7Days

Get the concrete date range for a rolling 7-day window ending today by running the bundled resolver:

node "$AGENT_DIR/.claude/skills/temporal/when.mjs" last7Days

It prints a human-readable line plus a JSON record:

• start / end — inclusive civil dates (YYYY-MM-DD) in your local timezone
• startUtc / endExclusiveUtc — the same window as a half-open [start, end) range of exact UTC instants, for timestamp-based queries
• days, timezone, asOf — the span, your timezone, and when this resolved

Use the returned dates as the time bounds for the task at hand. Do not derive dates by hand — this resolver is the source of truth. For the full window list or an arbitrary range (e.g. last45days, last6months), see the /temporal skill.

/lastMonth

Get the concrete date range for the previous full calendar month by running the bundled resolver:

node "$AGENT_DIR/.claude/skills/temporal/when.mjs" lastMonth

It prints a human-readable line plus a JSON record:

• start / end — inclusive civil dates (YYYY-MM-DD) in your local timezone
• startUtc / endExclusiveUtc — the same window as a half-open [start, end) range of exact UTC instants, for timestamp-based queries
• days, timezone, asOf — the span, your timezone, and when this resolved

Use the returned dates as the time bounds for the task at hand. Do not derive dates by hand — this resolver is the source of truth. For the full window list or an arbitrary range (e.g. last45days, last6months), see the /temporal skill.

/lastQuarter

Get the concrete date range for the previous full quarter by running the bundled resolver:

node "$AGENT_DIR/.claude/skills/temporal/when.mjs" lastQuarter

It prints a human-readable line plus a JSON record:

• start / end — inclusive civil dates (YYYY-MM-DD) in your local timezone
• startUtc / endExclusiveUtc — the same window as a half-open [start, end) range of exact UTC instants, for timestamp-based queries
• days, timezone, asOf — the span, your timezone, and when this resolved

Use the returned dates as the time bounds for the task at hand. Do not derive dates by hand — this resolver is the source of truth. For the full window list or an arbitrary range (e.g. last45days, last6months), see the /temporal skill.

/lastWeek

Get the concrete date range for the previous full week (Mon → Sun) by running the bundled resolver:

node "$AGENT_DIR/.claude/skills/temporal/when.mjs" lastWeek

It prints a human-readable line plus a JSON record:

• start / end — inclusive civil dates (YYYY-MM-DD) in your local timezone
• startUtc / endExclusiveUtc — the same window as a half-open [start, end) range of exact UTC instants, for timestamp-based queries
• days, timezone, asOf — the span, your timezone, and when this resolved

Use the returned dates as the time bounds for the task at hand. Do not derive dates by hand — this resolver is the source of truth. For the full window list or an arbitrary range (e.g. last45days, last6months), see the /temporal skill.

/lastYear

Get the concrete date range for the previous full calendar year by running the bundled resolver:

node "$AGENT_DIR/.claude/skills/temporal/when.mjs" lastYear

It prints a human-readable line plus a JSON record:

• start / end — inclusive civil dates (YYYY-MM-DD) in your local timezone
• startUtc / endExclusiveUtc — the same window as a half-open [start, end) range of exact UTC instants, for timestamp-based queries
• days, timezone, asOf — the span, your timezone, and when this resolved

Use the returned dates as the time bounds for the task at hand. Do not derive dates by hand — this resolver is the source of truth. For the full window list or an arbitrary range (e.g. last45days, last6months), see the /temporal skill.

Code Audit (read-only)

Perform a read-only code quality scan and return a findings report. Do NOT edit any files.

Steps:

1. Scope — identify the primary language and entry points (package.json, Cargo.toml, go.mod, pyproject.toml, or similar).
2. Scan — use Grep and Read to look for:
   • Unhandled promise rejections / ignored errors
   • Hard-coded secrets or credentials (keys, tokens, passwords)
   • TODO/FIXME/HACK comments that signal known debt
   • Dead exports (exported symbols with no in-repo import)
   • Obvious type-safety gaps (unchecked any, missing null guards)
3. Report — output a findings list sorted by severity (Critical → High → Medium → Low):

   ## Audit Report — <project name>
   
   ### Critical
   - [file:line] <description>
   
   ### High
   - ...
   
   ### Summary
   <total count> findings across <file count> files scanned.
   

4. Stop after reporting. Do not apply any fixes.

Fetch & Summarize

Given a URL, fetch its content and return a concise markdown summary.

Steps:

1. Fetch the page with WebFetch (or Bash with curl -sL <url> | head -200 as a fallback).
2. Extract the main content — ignore nav, footer, ads, and boilerplate.
3. Return a structured summary with:
   • Title (the page's <title> or heading)
   • One-paragraph overview of what the page is about
   • Key points as a bullet list (max 5)
   • Source — the URL fetched

Do not save or write the fetched content anywhere. Return the summary directly.

Hive Sync

Run the mandatory hive start-of-task steps:

1. Read memory — Read $AGENT_DIR/memory.md for durable context from prior sessions.

2. Check inbox — list and read all files in $AGENT_DIR/inbox/ that are NOT in inbox/.done/. For each message:

   • Act on the message.
   • Move the handled file into $AGENT_DIR/inbox/.done/ with mv.

3. Report — summarize what you found in memory and any new inbox messages. Note any tasks assigned to you or information relevant to the current session.

4. End-of-task reminder — before closing this conversation, append durable facts, decisions, and outcomes to $AGENT_DIR/memory.md so future-you remembers.

Run echo $AGENT_DIR if the variable is not set to locate your agent directory under the hive root.

/temporal — concrete date ranges, relative to now

This is the single source of truth for "what dates does mean right now?". It resolves named windows to concrete ISO date ranges relative to your run time (new Date() at the moment you invoke it), so you never re-derive dates manually. It only reads the clock and prints — no files written, no network.

Run it

# all windows at once (a quick temporal-context dump)
node "$AGENT_DIR/.claude/skills/temporal/when.mjs"

# one or several specific windows
node "$AGENT_DIR/.claude/skills/temporal/when.mjs" last30Days thisQuarter

# JSON only (machine-readable), or list the supported keywords
node "$AGENT_DIR/.claude/skills/temporal/when.mjs" --json last7Days
node "$AGENT_DIR/.claude/skills/temporal/when.mjs" --list

If $AGENT_DIR is somehow unset, the script also lives under ~/.claude/skills/temporal/when.mjs.

Windows

Aliases: ytd, qtd, mtd, wtd, 7d, 30d, 90d, 12m.

Convention: this* windows are period-start → today (to-date); last* named periods are the full prior complete period.

Output

Each window prints a human line plus a JSON record:

• start / end — inclusive civil dates (YYYY-MM-DD) in your local timezone
• startUtc / endExclusiveUtc — the same span as a half-open [start, end) range of exact UTC instants, ideal for timestamp / createdAt-style queries
• days, inclusive, timezone, tzOffsetMinutes, asOf — span, tz, and the instant the range was resolved

Use the returned dates as the time bounds for the task. The named shortcuts /today, /yesterday, /last30Days, /lastQuarter, … each call this same resolver for their one window.

/thisMonth

Get the concrete date range for this month so far (1st → today) by running the bundled resolver:

node "$AGENT_DIR/.claude/skills/temporal/when.mjs" thisMonth

It prints a human-readable line plus a JSON record:

• start / end — inclusive civil dates (YYYY-MM-DD) in your local timezone
• startUtc / endExclusiveUtc — the same window as a half-open [start, end) range of exact UTC instants, for timestamp-based queries
• days, timezone, asOf — the span, your timezone, and when this resolved

Use the returned dates as the time bounds for the task at hand. Do not derive dates by hand — this resolver is the source of truth. For the full window list or an arbitrary range (e.g. last45days, last6months), see the /temporal skill.

/thisQuarter

Get the concrete date range for this quarter so far (quarter start → today) by running the bundled resolver:

node "$AGENT_DIR/.claude/skills/temporal/when.mjs" thisQuarter

It prints a human-readable line plus a JSON record:

• start / end — inclusive civil dates (YYYY-MM-DD) in your local timezone
• startUtc / endExclusiveUtc — the same window as a half-open [start, end) range of exact UTC instants, for timestamp-based queries
• days, timezone, asOf — the span, your timezone, and when this resolved

Use the returned dates as the time bounds for the task at hand. Do not derive dates by hand — this resolver is the source of truth. For the full window list or an arbitrary range (e.g. last45days, last6months), see the /temporal skill.

/thisWeek

Get the concrete date range for this week so far (Monday → today) by running the bundled resolver:

node "$AGENT_DIR/.claude/skills/temporal/when.mjs" thisWeek

It prints a human-readable line plus a JSON record:

• start / end — inclusive civil dates (YYYY-MM-DD) in your local timezone
• startUtc / endExclusiveUtc — the same window as a half-open [start, end) range of exact UTC instants, for timestamp-based queries
• days, timezone, asOf — the span, your timezone, and when this resolved

Use the returned dates as the time bounds for the task at hand. Do not derive dates by hand — this resolver is the source of truth. For the full window list or an arbitrary range (e.g. last45days, last6months), see the /temporal skill.

/thisYear

Get the concrete date range for this year so far (Jan 1 → today) by running the bundled resolver:

node "$AGENT_DIR/.claude/skills/temporal/when.mjs" thisYear

It prints a human-readable line plus a JSON record:

• start / end — inclusive civil dates (YYYY-MM-DD) in your local timezone
• startUtc / endExclusiveUtc — the same window as a half-open [start, end) range of exact UTC instants, for timestamp-based queries
• days, timezone, asOf — the span, your timezone, and when this resolved

Use the returned dates as the time bounds for the task at hand. Do not derive dates by hand — this resolver is the source of truth. For the full window list or an arbitrary range (e.g. last45days, last6months), see the /temporal skill.

/today

Get the concrete date range for today by running the bundled resolver:

node "$AGENT_DIR/.claude/skills/temporal/when.mjs" today

It prints a human-readable line plus a JSON record:

• start / end — inclusive civil dates (YYYY-MM-DD) in your local timezone
• startUtc / endExclusiveUtc — the same window as a half-open [start, end) range of exact UTC instants, for timestamp-based queries
• days, timezone, asOf — the span, your timezone, and when this resolved

Use the returned dates as the time bounds for the task at hand. Do not derive dates by hand — this resolver is the source of truth. For the full window list or an arbitrary range (e.g. last45days, last6months), see the /temporal skill.

/yesterday

Get the concrete date range for yesterday by running the bundled resolver:

node "$AGENT_DIR/.claude/skills/temporal/when.mjs" yesterday

It prints a human-readable line plus a JSON record:

• start / end — inclusive civil dates (YYYY-MM-DD) in your local timezone
• startUtc / endExclusiveUtc — the same window as a half-open [start, end) range of exact UTC instants, for timestamp-based queries
• days, timezone, asOf — the span, your timezone, and when this resolved

Use the returned dates as the time bounds for the task at hand. Do not derive dates by hand — this resolver is the source of truth. For the full window list or an arbitrary range (e.g. last45days, last6months), see the /temporal skill.