Weekly Market Recap Writer logo

Weekly Market Recap Writer

Community
latour-ai
weekly-market-recap-writer

Turn a set of links, notes, and data points the user provides into a client-ready weekly market recap — what happened, why it matters, neutral tone, every claim sourced, no predictions, no advice. For IR teams, client advisors, wealth managers, and anyone who sends a weekly note. Trigger on phrases like "write the weekly recap," "market recap from these links," "weekly commentary," "client market update," "turn these notes into the Friday note," "weekly wrap," or when the user provides a batch of market links/data and wants a polished recap. Do NOT use for quarterly LP letters — use the lp-update-generator skill. Do NOT use for curated newsletter link roundups — use the roundup-newsletter skill. Do NOT use when the user wants market analysis researched from scratch — this skill writes from what the user supplies.

Overview

Publisherlatour-ai
Repositoryskills
Skill nameweekly-market-recap-writer
Stars
69
Forks
4
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by latour-ai on GitHub. Read the source before you install it.

Installation

Install the Weekly Market Recap Writer AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/latour-ai/skills/tree/main/weekly-market-recap-writer
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/latour-ai/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/weekly-market-recap-writer .claude/skills/weekly-market-recap-writer
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Weekly Market Recap Writer in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Weekly Market Recap Writer on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Weekly Market Recap Writer is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Weekly Market Recap Writer

Turn the week's raw material — links, jotted notes, data points — into a clean weekly market recap: what happened, why it matters, neutral tone, zero predictions, zero advice. Every claim is traceable to a source the user supplied (or is flagged as unsourced), because in a client-facing document, "where did this number come from?" must always have an answer.

Why this skill exists

The weekly note is the most reliably recurring writing task in client-facing finance, and it eats Friday afternoons. The inputs already exist — a folder of links, a few Bloomberg screenshots described in notes, three things the PM mentioned — but assembling them into something a client can read takes two hours and carries real compliance risk if a stray prediction or unsourced number slips in. This skill does the assembly under strict rules: it writes only from what the user provided, it attributes everything, and it refuses the two things that get weekly notes pulled by compliance — forecasts and advice.

Inputs

Required:

  • The week's raw material: links, pasted articles, notes, data points, bullet fragments. Anything goes in; only sourced material comes out as fact.

Optional (defaults applied and labeled if absent):

  • Audience: client-facing or internal (default: client-facing — the stricter standard)
  • Length: short (~300 words), standard (~600), long (~1,000) (default: standard)
  • Sections/format preferences, prior recaps to match voice
  • Firm context: strategies or asset classes the readers care about, so emphasis lands right
  • As-of date for the week being covered (default: infer from the materials and label it)
  • If your AI has web access and the user provides bare links, fetch them to read the content; if fetching fails, say so rather than summarizing from the URL text.

Missing-input behavior: Never block on missing preferences — apply the defaults above and state them at the top of the draft. The one thing never assumed is a market fact: if the user's materials don't establish it, it doesn't appear as fact.

How it works

  1. Inventory the materials. List what was provided, what each source is (publication, data point, user note), and the date of each. Flag anything stale relative to the week being covered.
  2. Sort claims into three bins:
    • Sourced fact — established by a provided link/document: usable, with attribution
    • User assertion — stated in the user's notes without a source: usable only as flagged ("per your notes — no source provided")
    • Neither — gaps the user might expect covered (e.g., no rates material in a week the Fed met): listed at the end as gaps, never filled from memory
  3. Structure the week. Group into 3–5 themes that organize the materials (e.g., central banks, earnings, a sector story, a notable data release). The materials drive the themes — don't impose a template the inputs can't support.
  4. Write "what happened" tight and attributed. Each factual statement traces to a provided source. Market levels and moves appear only if the user's materials contain them, always with the as-of date.
  5. Write "why it matters" without crossing the line. Context and mechanism are fine ("higher rates raise discount rates on long-duration assets"); forecasts are not ("we expect rates to fall"). Attribute third-party views as views ("Strategists at [firm] argue..."), never adopt them as the note's own.
  6. Run the compliance self-scrub (see Guardrails), then assemble with the source list and the unsourced-claims flag box.

Output format

Length follows the substance: cover what the task needs and leave out filler sections, restated summaries, and boilerplate.

# Weekly Market Recap — Week of [date range]
Audience: [client-facing / internal] | Length: [setting] 
[If defaults were assumed: "Assumed: client-facing, standard length."]

## [Theme 1 — e.g., "Central banks: the week's main event"]
[What happened — attributed. Why it matters — mechanism and context, no
forecasts.]

## [Theme 2]
...

## [Theme 3]
...

## The week in brief
[3–6 one-line items that didn't merit a section, each attributed.]

---
**Sources:** [numbered list: every provided source used, with date accessed/published]

**⚠ Unsourced items (from your notes — verify before sending):**
- "[claim]" — no source provided

**Gaps:** [topics a reader might expect this week that the materials didn't cover]

**Compliance reminder:** This draft is for internal review. Client-facing
market commentary typically requires compliance review before distribution —
route this through your firm's process. This note contains no investment
advice or recommendations and should stay that way through editing.

For internal audience, the compliance reminder shortens to one line and tone may be more direct, but sourcing discipline is identical.

Guardrails

  • No predictions, period. Nothing about what markets, rates, or prices will do — including hedged versions ("could continue to," "may face pressure"). Mechanism and history are allowed; forecasts are not. Third-party forecasts appear only as attributed views. Words like "will," "expect," "likely," "should," "forecast," and "poised to" usually signal a forecast.
  • No advice. No "investors should," no "we favor," no positioning suggestions, no "opportunities." If the user's notes contain advice-flavored lines, move them to the unsourced/flagged box with a note. "We recommend" and "attractive" fall in the same category.
  • Every claim attributed. Facts trace to a provided source with date; user assertions are flagged as unsourced in the dedicated box, never silently woven in as fact.
  • Never fill gaps from memory. No market levels, moves, or events from the AI's own knowledge — if it wasn't in the materials, it goes in "Gaps." This is absolute: a plausible-but-wrong S&P level in a client note is the worst failure mode this skill has.
  • Neutral tone. No cheerleading, no doom. "Equities fell" not "markets were crushed."
  • As-of dates on all data. Weekly notes get forwarded weeks later; undated numbers become wrong numbers.
  • Compliance reminder is mandatory on every client-facing draft and may not be removed by the skill.

Example prompt

"Friday note time. Here are six links from this week (Fed minutes coverage, two earnings stories, an oil piece), plus my notes: 'S&P roughly flat on the week, 10yr backed up ~15bps — check exact numbers.' Client-facing, standard length, neutral. Flag anything I gave you without a source."

Frequently asked questions

What does the Weekly Market Recap Writer AI skill do?

Turn a set of links, notes, and data points the user provides into a client-ready weekly market recap — what happened, why it matters, neutral tone, every claim sourced, no predictions, no advice. For IR teams, client advisors, wealth managers, and anyone who sends a weekly note. Trigger on phrases like "write the weekly recap," "market recap from these links," "weekly commentary," "client market update," "turn these notes into the Friday note," "weekly wrap," or when the user provides a batch of market links/data and wants a polished recap. Do NOT use for quarterly LP letters — use the lp-...

Why use Weekly Market Recap Writer on TypingMind?

Because you install it once and use it with any model. Weekly Market Recap Writer is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Weekly Market Recap Writer in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/latour-ai/skills/tree/main/weekly-market-recap-writer. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Weekly Market Recap Writer?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Weekly Market Recap Writer?

As many as you like. As long as a model supports skills, you can use Weekly Market Recap Writer with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Weekly Market Recap Writer AI skill free?

Yes. It is published on GitHub by latour-ai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇