Skip to content
Back to skills

Event Sweep

ASecurity

Sweep Quartr events for active (and monitoring) theses into a Daily Intel triage note. Use when user says "event sweep", "what's on the calendar this week", "Monday sweep", or after a conference week. Triage only — figures destined for a thesis go through /transcript, /filing, or /slides.

  • 3 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 11, 2026
researchgobash

Security analysis

A100/100

Scanned November 8, 2026

npx -y skills add jameswong2011/InvestmentVault --skill event-sweep --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Event Sweep?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Event Sweep
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jameswong2011-event-sweep/badge)](https://www.skillsdirectory.com/skills/jameswong2011-event-sweep)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: event-sweep
description: Sweep Quartr events for active (and monitoring) theses into a Daily Intel triage note. Use when user says "event sweep", "what's on the calendar this week", "Monday sweep", or after a conference week. Triage only — figures destined for a thesis go through /transcript, /filing, or /slides.
model: opus
effort: max
allowed-tools: Read Grep Glob Edit Write Bash(date * mkdir * ls * cp *)
---

**Follow CLAUDE.md Writing Standards strictly.** Lead with the count and the thesis-touching flags. Event Sweep is a scanning surface, not a research note.

Codify the 2026-09-09 first-run artefact. Writes `Daily Intel/YYYY-MM-DD - Event Sweep.md`. Does **not** create Research notes, does **not** `/sync`, does **not** edit theses. Highlights end with `→ /transcript TICKER --event ID` (or `/filing` / `/slides`).

Per `_shared/quartr.md`: summaries are Quartr-generated pointers and Q&A extracts are triage, never evidence.

## Arguments

`$ARGUMENTS`:
- empty / `week` — lookback 7d + forward 7d (default; Monday morning)
- `--from YYYY-MM-DD --to YYYY-MM-DD` — explicit window
- `--conference` — also `list_conferences` in the window and expand named conferences that intersect the book

## Step 0: Pre-flight

Vault-wide lock per `_shared/preflight.md` Procedure 1. Timeout 10 minutes. Rename-marker glob: warn-only (this skill does not edit theses).

Read `_shared/quartr.md`. Read `.data/quartr_watchlists.json` if present. If `monitoring_id` is 0 or missing, sweep Vault Active (30182) only and report `ℹ️ Vault Monitoring watchlist not seeded — run /watchlist-sync`.

## Step 1: Universe

`list_events` on watchlist 30182 (and monitoring_id if set) with `startDate` = window start minus 1 day, `endDate` = window end plus 1 day, `order: desc`, `expand: ["documents", "expectedContent", "transcript"]`. Cache per the contract.

Classify each event:
- **transcript-bearing** — a transcript document or `read_transcript` succeeds
- **happened-no-transcript** — event date ≤ today, no transcript yet
- **upcoming** — event date > today

Do not call `read_transcript` on every event. For transcript-bearing events, prefer `get_event_summary`; pull `read_transcript section: qna` only for the events that survive Step 2 (cap 8 Q&A extracts per run).

## Step 2: Thesis-touching highlights

For each transcript-bearing or summary-bearing event, grep the matching thesis (via `quartr_id:` / watchlist JSON) for Outstanding Questions, Conviction Triggers, and the last 5 Log entries. Flag when the summary/Q&A names a variable those sections already wrote.

Cap **6 highlights**. Rank: live-book Full/High first, then named trigger/OQ hits, then cross-thesis signals (one event that names another vault ticker).

Each highlight is 2–4 sentences + `→ /transcript TICKER --event ID` (or `/filing` / `/slides` when the payload is a document, not a call). Cross-thesis flags name both tickers.

## Step 3: Write the Daily Intel note

Filename: `Daily Intel/YYYY-MM-DD - Event Sweep.md`. If a file for today exists, overwrite (regenerated scanning surface, like a news brief — not an immutable research note).

```yaml
---
date: YYYY-MM-DD
tags: [meta, daily-intel, event-sweep]
window: YYYY-MM-DD..YYYY-MM-DD
---
```

Body skeleton (match the 2026-09-09 note):
1. One-line count: `N events across M names · T transcript-bearing · H happened-no-transcript · U upcoming · watchlist drift: +X/−Y`
2. Triage disclaimer (verbatim): summaries are Quartr-generated pointers and Q&A extracts are triage, never evidence. Any figure destined for a thesis goes through `/transcript`.
3. `## Thesis-touching highlights` — numbered, with `/transcript --event` commands
4. `## By company` — one `### TICKER — event title (date)` per transcript-bearing event, with event URL, 3–8 Q&A bullets citing paragraph URLs, or a short summary if no Q&A
5. `## Appearances without transcripts` — bullets; note that the next Monday sweep catches late conference transcripts
6. `## Upcoming week` — day-by-day, bold live-book names
7. `## Coverage gaps` — watchlist vs `status: active` set-diff (should be none after `/watchlist-sync`); list monitoring names not on the Monitoring list

Do not `/sync`. Do not append thesis Logs.

## Step 4: `_hot.md`

Per `_shared/hot-md-contract.md`. Active Research Thread: one dated line `YYYY-MM-DD: event sweep — [N] highlights, top flag [TICKER]`. Open Questions: only for highlights that touch a Conviction Trigger (dedupe by ticker + `event sweep`).

## Step 5: Report + lock release

```
✓ /event-sweep complete
Window:     [start] → [end]
Events:     [N] ([T] transcript-bearing)
Highlights: [list of TICKER — one-liner]
Note:       [[Daily Intel/YYYY-MM-DD - Event Sweep]]
Next:       pick highlights via /ingest --from-sweep  OR  run the printed /transcript --event commands
```

Release lock per preflight §1.7.

## Design constraints

1. **Triage, never evidence.** Q&A extracts stay in Daily Intel. The thesis spine is written by `/transcript` / `/filing` / `/slides`.
2. **No auto-sync.** A sweep that `/sync`s would launder Quartr summaries into sector notes.
3. **Cap Q&A extracts at 8 events.** Unbounded `read_transcript` blows context; the rest wait for a picked `/transcript`.
4. **Do not ingest Quartr Edge.** Editorial profiles are an inside-view engine.
5. **Monday launchd runs this skill via grok** (`com.investmentvault.event-sweep`). All weekly jobs share that runner.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.