Grok Bot WikiRemnant Security · source: grokbot-docs

Home / skills/approval-and-delivery-log-check/SKILL.md

Approval and delivery log check

name: Approval and delivery log check description: >- Use before surfacing anything to the user, before taking any action that needs their approval, and right after delivering or doing something: checks the shared approvals ledger and delivered log so nothing is re-asked, re-sent, or done without a recorded yes.

Approval and delivery log check

Two shared markdown files act as the fleet's memory of what the user approved and what they have already been told. The paths live in the routine or memory that calls this skill (for example <workspace>/approvals/approvals.md and <workspace>/approvals/delivered.md).

Before surfacing an item

  1. Read the delivered log in full. Search it for the item's link, its ID or permalink, and two or three key words from the ask.
  2. If the same item or ask is already listed, don't surface it again unless the facts have materially changed (a new sale, a reply, an error, a deadline, a new number). If they changed, say what changed in one sentence.
  3. If the log marks an ask as SKIPPED, declined, or "do not re-ask", don't re-ask unless a listed trigger has happened.
  4. Never send a draft the log marks SUPERSEDED.

Before acting on something that needs approval

  1. Read the approvals ledger: the "Standing rules" section first, then the item rows.
  2. Act only if one of these is true:
    • A standing rule covers the action, and every one of its conditions and caps holds today. Count today's uses against the cap.
    • An item row records the user's approval of this exact action and target, and its status isn't already done.
  3. Otherwise stop. Draft the ask with the exact text and target, and route it to the user through the front-door bot.
  4. Approval for one step doesn't cover the next. "Approved (edits only)" is not approval to deploy.

After acting

  • In the approvals ledger, set the row's status to posted, sent, merged, or done, with the time (user's timezone) and permalink or evidence path. Use blocked: <reason> if it failed.
  • For a standing-rule action, add a new row naming the rule and the permalink.

After delivering to the user

  • Append one line to the delivered log: date and time (user's timezone), the item, the link or path, and a short note. The note covers which asks were included and which were deliberately not re-asked.
  • If the user skips or declines an ask, add a line saying so, plus what would justify asking again.

Rules

  • Append; never rewrite or delete history rows.
  • Times are in the user's timezone, with a label (e.g. "CT").
  • If either file is missing or unreadable, say so and don't act on approval-gated items.