# Weekly Signals

> Use when /weekly-signals is invoked or during weekly review. Reads patterns.md and the week's daily notes, surfaces deferral patterns and flagged items, and outputs a paste-ready Accountability Signals block for the Weekly Review.

- Skill: `slogsdon/weekly-signals` (Agent Skill)
- Install (CLI): `npx skillmds@latest add slogsdon/weekly-signals`
- Raw SKILL.md: https://api.skillmd.com/api/skills/slogsdon/weekly-signals/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: slogsdon (https://skillmd.com/u/slogsdon)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/slogsdon/weekly-signals

---


# Skill: /weekly-signals

Aggregate the week's accountability signals into a paste-ready block — deferral patterns, logging gaps, and OKR alignment — without auto-writing to vault.

**Don't:** write to the Weekly Review automatically — output for Shane to paste manually. Don't skip the inbox check — uncleaned inboxes skew the signal.

## Steps

1. **Check inbox** — count non-fixture files in `Inbox/` (exclude: `Inbox Processing.md`, `todo.md`, `Chores.md`)
   - If count > 0: "Your Inbox has N unprocessed items. Run /inbox-process first, or continue with the weekly review?"
   - If count = 0: proceed
2. Determine the current week's date range (Monday–Sunday, YYYY-MM-DD format)
3. Read these files from the vault:
   - `Context/patterns.md`
   - `Context/accountability.md`
   - All `Daily Notes/[date].md` files for the current week (read each that exists)
4. Follow [Qwen Protocol](../_lib/qwen-protocol.md) with:
   - `task`: "You are Shane's weekly accountability analyst. Review this week's daily notes and patterns.md (provided). Surface: (1) tasks deferred 2+ times this week, (2) any PATTERN ALERT items, (3) logging gaps (days with no session log), (4) OKR alignment score — what % of logged work maps to the 3 active OKRs? Output a markdown block titled '## Accountability Signals' ready to paste into a Weekly Review note. Be honest, not cheerful."
   - `skill`: "weekly-signals"
   - `context`: content of all files concatenated
5. Output Qwen's `result` to Shane — do NOT write to the Weekly Review automatically. Shane pastes it manually.
6. Offer to explain any pattern or signal in more detail.

## Fallback (if qwen unavailable)

If Qwen is unavailable:

1. **Check inbox** — same as main step 1
2. Determine the current week's Monday–Sunday date range (YYYY-MM-DD)
3. Read the following files via bash:
   - `obsidian read file="Context/patterns"`
   - `obsidian read file="Context/accountability"`
   - `obsidian read file="Daily Notes/[date]"` for each date in the week that exists
4. Aggregate signals:
   - **Deferred 2+ times this week:** count how many EOD Audits each task appeared in as deferred
   - **PATTERN ALERTs:** collect any PATTERN ALERT lines from the week's EOD Audits
   - **Logging gaps:** note any days where the session log was empty or missing
   - **OKR alignment:** for each day's session log, classify each logged item as OKR-aligned or not; compute a rough percentage
5. Output the following block to Shane (do NOT write to vault — Shane pastes manually):
   ```markdown
   ## Accountability Signals — Week of [Monday date]

   **Deferred 2+ times:**
   - [task] — deferred [N] times

   **Pattern Alerts:**
   - [PATTERN ALERT items from patterns.md with 3+ deferrals]

   **Logging Gaps:** [days with no session log, or "none"]

   **OKR Alignment:** ~[N]% of logged work mapped to active OKRs
   - Aligned: [examples]
   - Off-OKR: [examples]
   ```
6. Offer to explain any signal in more detail