daily-briefing
Skill2 starsChanged 5 months agoMITView on GitHub
Run a one-shot morning portfolio digest that ties together health, alerts, macro regime, crowding risk, concentration, and earnings calendar into a single decision-ready brief. Use when the user asks for "morning briefing", "daily digest", "what's happening today?", "what changed overnight?", or "give me the morning rundown". Composes existing MCP tools - no new data sources.
36 other projects use a version of this.
Adopted by
Most recently taken up by
- taylorjamesmacarthur-hub/lovetta-new-job-starter-packtheir own version, first seen Nov 16, 2026
- Alessandro114/scala-mcp-servertheir own version, first seen Nov 8, 2026
- waj-1/waj-plugintheir own version, first seen Nov 8, 2026
- jwm-axoni/claude-workbenchtheir own version, first seen Nov 8, 2026
- tsukhani/jclawtheir own version, first seen Nov 5, 2026
- Suryanandx/qvac-uitheir own version, first seen Nov 1, 2026
Used with
Projects with it also use crm-lookup, spotify and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
QuixiAISkillcrm-lookup
Search, view, update, and merge contacts in the local CRM
Also in 3 projects that use this
QuixiAISkillspotify
Search Spotify, inspect current playback and devices, and control playback with explicit approval
Also in 3 projects that use this
MicrosoftSkillinbox-triage
Use this skill whenever the user asks to clean up, triage, declutter, or archive low-value Outlook inbox mail - "clean up my inbox", "triage my mail", "declutter my inbox", "sort out newsletters", "archive old resolved threads", "/inbox-triage" - to group only newsletters, auto-notifications, past-event meeting logistics, resolved threads, and redundant duplicates into reviewable move-proposals presented for per-bucket approval before any message moves. Do not use for reading mail, drafting or sending replies, deleting mail, executing moves without explicit per-bucket approval, or acting on messages from the user's manager, direct reports, active threads, flagged mail, or labelled/HR/Legal/Finance/Security senders.
Also in 4 projects that use this
MicrosoftSkillimage-gen
Also in 3 projects that use this
AnthropicSkillweather
The optional standing status report ("the weather"): compile open incidents, build health, merge-queue stats, and deploy lag into one always-current report page, and post to the channel only when a defined event fires. Use when the weather routine fires, or when someone asks to run/update the weather report.
Also in 3 projects that use this
SentrySkillnotion
Search, fetch, create, update, and move Notion pages and data sources. Use when users ask to look up docs, specs, notes, meeting notes, project context, roadmaps, trackers, or internal references stored in Notion, or when they explicitly ask to create or edit Notion content.
Also in 3 projects that use this
- +2 more from QuixiAI
Other versions36 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 36
- anthropics/knowledge-work-plugins★ 36ksame name
- vellum-ai/vellum-assistant★ 1.5ksame name
- QuixiAI/agi-memory★ 623same name
- QuixiAI/Hexis★ 623same name
- legalopsconsulting/lpm-skills★ 61same name
- microsoft/dataverse-business-skills★ 51same name
- tsukhani/jclaw★ 42same name
- mgonzalezbaile/personal-assistant★ 8same name
- zime-skills/global★ 8same name
- zime-skills/zime-skills★ 8same name
26 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- adversarial-researchSkill
- auto-rebalanceSkill
- cash-deploymentSkill
- dividend-strategySkill
- earnings-analyzerSkill
- earnings-postmortemSkill
- employer-stockSkill
- health-checkSkill
- macro-impactSkill
- momentum-scannerSkill
- optimize-allocationSkill
- pead-trackerSkill
- perf-optimizerSkill
- portfolio-healthSkill
- portfolio-reviewSkill
- position-reviewSkill
- pre-trade-checkSkill
- profile-setupSkill
- risk-assessmentSkill
- sector-rotationSkill
- stock-analysisSkill
- stock-compareSkill
- tax-loss-reviewSkill
- top-trades-todaySkill
- trade-journalSkill
- trading-deskSkill
- weekly-mirrorSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 3 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 33 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read .claude/context/STATE.md.
- Very specific: line 18
If last_crowding_regime is set, use it as prior context when interpreting positioning signals (flag if regime changed).
- Distinctive: line 30
Call in parallel (no inter-dependencies):
- Distinctive: line 48
Check macro snapshot for these scheduled events TODAY (US Eastern):
- Very specific: line 60
If catalyst flagged, prefix section 1 headline with ⚠️ CATALYST: <event> @ <time> and add section 2 bullet: "Reduce intraday position sizes …
- Very specific: line 66
Always pull capital + accounts from get_profile - never hardcode
- Very specific: line 113
If none apply, write: No active FOMO traps - positioning disciplined.
- Very specific: line 121
If no intraday signals worth surfacing, write: No notable intraday setups.
- Very specific: line 128
After completing the brief, update .claude/context/STATE.md:
- Distinctive: line 137
If tool errors or returns empty, list in section 7 - do NOT fabricate data.
“Common” is measured: kept by at least 6 in 10 of the 33 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Daily Briefing (morning digest)
Goal
One scroll-length brief surfacing what matters today. Composes the MCP tools listed below (8 core + BoC; crypto pair only if held). No new data fetches outside that list.
State check (BEFORE any tool calls)
Read .claude/context/STATE.md. If last_briefing_date equals today's date (YYYY-MM-DD), output:
"Daily briefing already ran today (
last_briefing_date). Skipping re-fetch to save tokens. Re-run with/daily-briefing forceto override." Then stop - do not call any MCP tools.
If last_crowding_regime is set, use it as prior context when interpreting positioning signals (flag if regime changed).
Decision Memory Protocol (load first, log after)
Before forming any view, load prior decisions so verdicts stay consistent across sessions:
mcp__aifolimizer__get_cross_ticker_lessons(max_lessons=3) - portfolio-level win/loss patterns- For any name you issue a per-ticker BUY/SELL/TRIM/HOLD/ADD on, also load
mcp__aifolimizer__get_ticker_decision_history(ticker=…, max_decisions=5) andmcp__aifolimizer__get_ticker_reflection(symbol=…, n=3). If a prior decision exists and this run flips it, state explicitly WHY (new data / catalyst / price); never silently contradict a logged decision.
After output, log every actionable verdict: for each BUY/SELL/TRIM/ADD/HOLD issued, call mcp__aifolimizer__log_recommendation (skill="daily-briefing", ticker, action, conviction, rationale, target_pct, stop_pct). Skipping breaks the cross-session feedback loop and causes drift.
How to run
Call in parallel (no inter-dependencies):
mcp__aifolimizer__get_profilemcp__aifolimizer__get_portfoliomcp__aifolimizer__get_personal_context- usederived(marginal_tax_rate_pct, account_waterfall, horizon) to sharpen the focus list and risk flags (e.g. tax-aware trim guidance, account-placement). Ifpresent == false, keep briefing generic and suggest running/profile-setup.mcp__aifolimizer__get_macro_snapshot(FRED + market regime)mcp__aifolimizer__get_concentration_warningsmcp__aifolimizer__get_triggered_alerts(since_hours=24)mcp__aifolimizer__get_earnings_calendar(next 14d)mcp__aifolimizer__get_positioning_signals(top 15 holdings)mcp__aifolimizer__get_technicals_intraday(top 5 holdings + any focus-list tickers - only if US market is open or pre-market)mcp__aifolimizer__get_boc_snapshot(cheap, 12h cache) - Canadian rate/FX/curve context; surfacecurve_signalin section 4 if invertedmcp__aifolimizer__get_crypto_fear_greed+mcp__aifolimizer__get_crypto_macro- ONLY if portfolio holds crypto; skip both otherwise (list in section 6)
Catalyst day check (FIRST - before anything else)
Catalysts drive intraday moves. Trading without knowing today's catalysts = trading blind.
Check macro snapshot for these scheduled events TODAY (US Eastern):
- FOMC decision / Fed minutes (8 per year, 2pm ET)
- CPI release (monthly, 8:30am ET)
- NFP / jobs report (first Friday monthly, 8:30am ET)
- PCE release (monthly, 8:30am ET)
- GDP advance (quarterly, 8:30am ET)
- VIX > 25 (elevated fear regime - wider stops, smaller size)
- Treasury auction (10Y/30Y reopening - bond-proxy stocks reactive)
- Turn-of-Month window (McConnell & Xu, 1897-2005): last trading day of month OR first 3 trading days of new month. Historically, essentially ALL positive equity returns are concentrated in this 4-day window. If today falls in this window, flag:
📅 TOTM WINDOW - bias long, avoid aggressive intraday shorts, favor momentum adds.
Cross-reference earnings calendar for next 24h (large-cap names only): MSFT/AAPL/NVDA/META/GOOGL/AMZN reporting tonight = next-day gap risk across whole portfolio if mega-cap.
If catalyst flagged, prefix section 1 headline with ⚠️ CATALYST: <event> @ <time> and add section 2 bullet: "Reduce intraday position sizes by 50% until event resolves. Wide stops or no trade."
Investor profile
- Canadian retail investor
- Philosophy: growth stocks, index ETFs, dividends, crypto
- Always pull capital + accounts from
get_profile- never hardcode
Output structure
Single-page brief, ≤ 450 words, this exact order:
1. Headline (one sentence)
Format: [Portfolio value CAD] · [Day Δ %] · [Regime label] · [N alerts last 24h]
Example: $182,300 CAD · -0.7% · bull_high_fear · 3 alerts last 24h
2. What changed (≤ 5 bullets)
Action-significant items only. No filler.
- New triggered alerts (price drop, RSI, earnings, concentration)
- Crowding score regime shifts (if positioning history available - flag consensus → contrarian or vice versa)
- Earnings within 3 days
- Macro regime change (e.g. bull_low_fear → bull_high_fear)
3. Today's focus list (≤ 3 tickers)
Pick from cross of: alerts triggered + earnings imminent + crowding flag. Format per ticker:
TICKER · weight X% · reason · suggested actionSuggested action is one of: review, trim, hedge, hold, add (small).
4. Risks on radar
- Single-position concentration > 10%
- Sector concentration > 35%
- Consensus-crowded names with negative day change > 3% (late-entry risk materializing)
- Yield curve / VIX / Fear-Greed extremes if macro snapshot flags; inverted
curve_signalfromget_boc_snapshotis a Canadian recession flag - Crypto sleeve (only if held):
get_crypto_fear_greedextreme (≤20 fear / ≥80 greed) + falling DefiLlama TVL = risk-off in crypto
5. Anti-FOMO traps (only surface real ones - else one line)
Behavioral guardrail. Built from data ALREADY fetched (crowding + day-change + earnings) - no new tool calls. List ≤ 3, each as TRAP · ticker · horizon · why · the disciplined move.
Horizon scope (READ FIRST - the logic inverts): the traps below are calibrated for swing / position / long-term entries. For intraday momentum trades the crowding + narrative-spike logic is REVERSED - riding the crowd is the edge, not the trap. Tag each trap with the horizon it bites. Never flag an intraday momentum scalp with a long-horizon crowding trap.
Swing / position / long-term traps:
- Chase-the-consensus:
crowding_label == consensus(score ≥ 70) on a name with a positive day → late-entry, negative expected alpha over weeks-months. Move: defer / size down, not add. - Narrative spike:
headline_velocity_ratio > 1.5(news surge) + crowding consensus → story-driven, not fundamental. Move: wait for velocity to cool before sizing. - Green-day add urge: holding already > 8% weight up > 5% on the day → adding on strength concentrates risk at a local high. Move: hold, revisit on pullback to support.
- Pre-print gamble: earnings within 3 days + urge to add a position-trade → binary bet, not a thesis. Move: no new size until after the print.
Intraday traps (the discipline is exit-rules, NOT crowd-avoidance):
- No-stop scalp: intraday entry without a hard stop + time-stop. Move: define both before entry or no trade.
- Late chase: entering after price already ran > 2 ATR / RSI(2) extreme - the move is spent. Move: wait for VWAP reclaim or next setup.
- Overstay: intraday thesis but holding past your time-stop into close → it's now an unplanned swing. Move: flatten or consciously convert with a swing stop.
If none apply, write: No active FOMO traps - positioning disciplined.
6. Intraday addendum (only if US market open or pre-market)
From get_technicals_intraday on focus-list + top 5 by weight, surface:
- Names with
intraday_score >= 0.7ANDvolume_spike >= 1.5→ "active setup" - Names with
opening_range_break == "below"AND held weight > 3% → "intraday weakness on size" - Gap names:
abs(gap_pct) >= 3→ "gap watch" Format per line:TICKER · intraday_score · VWAP $X.XX (Δ Y.Y%) · OR break: <dir> · noteIf no intraday signals worth surfacing, write:No notable intraday setups.
7. Skipped today
One line listing tools/checks that returned empty or stale data. Example: Skipped: crypto (no holdings), tax-loss (no underwater positions), intraday (market closed).
After output - write STATE.md
After completing the brief, update .claude/context/STATE.md:
last_briefing_date: today's date (YYYY-MM-DD)last_crowding_regime: crowding_label from positioning signals (consensus/neutral/contrarian) - same vocabulary asget_positioning_signalsso the next run's prior-context comparison is validactive_alerts: count of triggered alerts fromget_triggered_alertsopen_recs: count of open recommendations (from brief context if available)
Rules
- Direct. No hedging, no "you may want to consider".
- If tool errors or returns empty, list in section 7 - do NOT fabricate data.
- Currency: CAD aggregate unless user in specific account.
- Crowding rule (per CLAUDE.md): if
crowding_label == consensusAND ticker in focus list, default action skews towardtrimorhold, NOTadd. - One-shot - do not chain into another skill unless user asks.
Gotchas
get_triggered_alertsread-only - does NOT re-evaluate rules. If user wants fresh evaluation, callrun_alerts_nowfirst (only if explicitly requested - adds 5-10s).- TSX (.TO) tickers may have null crowding fields → label "neutral" by fallback. Don't treat as real signal.
- Macro regime label
bull_low_fearcan co-exist with portfolio-level red day - regime is market-wide, day-change is portfolio-specific. Don't conflate. - Earnings calendar is yfinance - sparse for non-US listings. Cross-check IR pages for TSX names if stake is large.
- "What changed" requires comparing to prior brief. If running fresh (no prior), say so in section 2 - don't invent comparisons.
get_technicals_intradayreturns empty dict outside US market hours - that is correct, list "intraday (market closed)" in skipped section, do not error- Catalyst check is REQUIRED - never skip it. If macro snapshot data is unavailable, default to assuming a quiet day BUT explicitly state "catalyst data unavailable - assume normal" in the headline. Better to be wrong about a quiet day than to miss a Fed day.
- Earnings catalyst list (mega-caps reporting in next 24h) only matters for big names - TSX small-caps reporting do not move SPY. Filter
get_earnings_calendarto weight > 2% of portfolio OR market_cap > $500B before flagging as portfolio-wide catalyst.
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.

