Run any Skill in Manus with one click

weekly-review

Stars0

Forks0

UpdatedJuly 15, 2026 at 08:18

Digest the outputs archive into durable context. Use for the weekly GTM review, or whenever asked what happened recently and what we learned. Reads recent outputs entries, summarizes results, and proposes context updates as a PR. This is the repo's memory flywheel.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

getcargohq

getcargohq/cargo-manifest

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Market Research Analysts and Marketing SpecialistsBusiness and Financial Operations Occupations·SOC 13-1161

SKILL.md

readonly

name	weekly-review
description	Digest the outputs archive into durable context. Use for the weekly GTM review, or whenever asked what happened recently and what we learned. Reads recent outputs entries, summarizes results, and proposes context updates as a PR. This is the repo's memory flywheel.

Weekly review: outputs to context

outputs/ is what happened. context/ is what we know. This skill moves learning from the first to the second, so the repo gets smarter every week.

Steps

Collect. List outputs/ entries from the last 7 days (directory names start with the date). Read each entry's summary.
Summarize. Write outputs/YYYY-MM-DD-weekly-review/README.md with:
- What ran (plays, campaigns, research) and headline numbers.
- What worked, what failed, with evidence.
- Open questions.
Extract durable learning. For each finding that changes what we know, propose the matching context edit:
- A new objection heard twice or more: context/objection/<slug>.md.
- A win or loss with a clear reason: update context/client/ and context/proof/.
- A signal that predicted a conversion: context/signal/<slug>.md.
- Messaging that outperformed: note it in the relevant context/motion/. Apply the repetition rule: a claim goes into context after it shows up independently at least twice. Once is an anecdote.
Ship. One PR: the review entry in outputs/ plus the proposed context edits. The PR description separates "observed" (outputs) from "concluded" (context changes) so reviewers can push back on conclusions.

Rules

Outputs entries are append-only. Never rewrite last week's entry.
If nothing meets the repetition bar, say so; an empty context diff is a valid review.

More from this repository

same repository

capture-feedback

getcargohq/cargo-manifest

Turn something heard in the field into durable context, at the right confidence level. Use when the user relays an objection, a competitor mention, a win or loss reason, a signal, or any claim from a call, and asks to remember it. Enforces the repetition rule and the confidence ladder.

2026-07-150

context-hygiene

getcargohq/cargo-manifest

Audit and repair the context layer. Use when asked to clean up context, before a quarterly review, or when the knowledge graph feels stale. Finds missing frontmatter, broken references, orphan files, and stale content, then fixes them file by file.

2026-07-150

gtm-repo

getcargohq/cargo-manifest

How this GTM repository works. Load when orienting in this repo, deciding where a change belongs, or explaining the layer conventions to someone. Covers the layers, the dependency direction, the PR workflow, the confidence ladder, and where each kind of change goes.

2026-07-150

log-day

getcargohq/cargo-manifest

Write today's entry in the cadence log. Use at the end of a working day, or when the user recaps what happened. Captures what moved, what is stuck, and anything worth remembering, then routes stuck items to carryover and repeated observations toward context.

2026-07-150

new-motion

getcargohq/cargo-manifest

Scaffold a new GTM motion end to end across all three layers. Use whenever creating a new motion, campaign, play, or automation in this repo, so the narrative (context), the implementation (infra), and the regression suite (evals) ship together and never drift apart. Enforces the outreach hypothesis rule.

2026-07-150

plan-week

getcargohq/cargo-manifest

Plan the coming week in the cadence layer. Use every Monday, or whenever asked what this week should focus on. Pulls from plan/ and open initiatives/, carries over unresolved items, and writes cadence/weekly/YYYY-Www.md. Escalates anything that has slipped three weeks into a decision instead of a task.

2026-07-150

name	weekly-review
description	Digest the outputs archive into durable context. Use for the weekly GTM review, or whenever asked what happened recently and what we learned. Reads recent outputs entries, summarizes results, and proposes context updates as a PR. This is the repo's memory flywheel.

Weekly review: outputs to context

outputs/ is what happened. context/ is what we know. This skill moves learning from the first to the second, so the repo gets smarter every week.

Steps

Collect. List outputs/ entries from the last 7 days (directory names start with the date). Read each entry's summary.
Summarize. Write outputs/YYYY-MM-DD-weekly-review/README.md with:
- What ran (plays, campaigns, research) and headline numbers.
- What worked, what failed, with evidence.
- Open questions.
Extract durable learning. For each finding that changes what we know, propose the matching context edit:
- A new objection heard twice or more: context/objection/<slug>.md.
- A win or loss with a clear reason: update context/client/ and context/proof/.
- A signal that predicted a conversion: context/signal/<slug>.md.
- Messaging that outperformed: note it in the relevant context/motion/. Apply the repetition rule: a claim goes into context after it shows up independently at least twice. Once is an anecdote.
Ship. One PR: the review entry in outputs/ plus the proposed context edits. The PR description separates "observed" (outputs) from "concluded" (context changes) so reviewers can push back on conclusions.

Rules

Outputs entries are append-only. Never rewrite last week's entry.
If nothing meets the repetition bar, say so; an empty context diff is a valid review.