weekly-signals
Skill0 starsChanged 3 months agoMITView on GitHub
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.
In this repository17 other files it gives its agents.
- backlinksSkill
- challengeSkill
- connectSkill
- expandSkill
- fix-nested-code-fencesSkill
- ghostSkill
- ingestSkill
- learnedSkill
- mapSkill
- meetingSkill
- obsidianSkill
- source-mineSkill
- traceSkill
- vault-indexSkill
- vault-lintSkill
- vault-retrieveSkill
- weekly-learningsSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Don't: write to the Weekly Review automatically — output for Shane to paste manually.
- Distinctive: line 15
If count > 0: "Your Inbox has N unprocessed items.
- Distinctive: line 18
Read these files from the vault:
- Distinctive: line 22
Follow Qwen Protocol with:
- Distinctive: line 31
If Qwen is unavailable:
- Distinctive: line 35
Read the following files via bash:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- 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
- Determine the current week's date range (Monday–Sunday, YYYY-MM-DD format)
- Read these files from the vault:
Context/patterns.mdContext/accountability.md- All
Daily Notes/[date].mdfiles for the current week (read each that exists)
- Follow Qwen Protocol 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
- Output Qwen's
resultto Shane — do NOT write to the Weekly Review automatically. Shane pastes it manually. - Offer to explain any pattern or signal in more detail.
Fallback (if qwen unavailable)
If Qwen is unavailable:
- Check inbox — same as main step 1
- Determine the current week's Monday–Sunday date range (YYYY-MM-DD)
- 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
- 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
- Output the following block to Shane (do NOT write to vault — Shane pastes manually):
## 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] - Offer to explain any signal in more detail
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

