Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

log-day

Étoiles0

Forks0

Mis à jour15 juillet 2026 à 08:18

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.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

getcargohq

getcargohq/cargo-manifest

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en études de marché et spécialistes en marketingProfessions des affaires et des opérations financières·SOC 13-1161

SKILL.md

readonly

name	log-day
description	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.

Log the day

Two minutes, not a status report. The log exists so that next Monday's plan and next Friday's review are written from what actually happened rather than from memory.

Steps

Write cadence/log/YYYY-MM-DD.md from cadence/log/_template.md:
- What moved. Concrete: a call happened, a play shipped, a number changed. Not "worked on outbound".
- What is stuck. Anything that did not resolve today.
- Worth remembering. A thing you heard that might become knowledge: an objection, a signal, a competitor mention, a reason a deal was won.
Route the stuck items. Anything under "What is stuck" that will not resolve tomorrow goes into cadence/carryover.md with today's date and a week count of 1. Do not let it live only in the log, where it will be forgotten.
Route the observations. For each item under "Worth remembering", check context/ for an existing file on the same claim:
- Second independent occurrence? It clears the repetition bar. Use the capture-feedback skill to promote it into context/ with the right confidence: level.
- First occurrence? Leave it in the log. One observation is an anecdote. Say so, and do not write it into context.

Rules

Append-only. Never edit yesterday's log to make it look better; add a dated addendum instead.
Absolute dates in the filename and the frontmatter.
Do not fabricate. If the user says "good call today", ask which account rather than inventing an outcome.

Plus depuis ce dépôt

même dépôt

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

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

weekly-review

getcargohq/cargo-manifest

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.

2026-07-150

name	log-day
description	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.

Log the day

Two minutes, not a status report. The log exists so that next Monday's plan and next Friday's review are written from what actually happened rather than from memory.

Steps

Write cadence/log/YYYY-MM-DD.md from cadence/log/_template.md:
- What moved. Concrete: a call happened, a play shipped, a number changed. Not "worked on outbound".
- What is stuck. Anything that did not resolve today.
- Worth remembering. A thing you heard that might become knowledge: an objection, a signal, a competitor mention, a reason a deal was won.
Route the stuck items. Anything under "What is stuck" that will not resolve tomorrow goes into cadence/carryover.md with today's date and a week count of 1. Do not let it live only in the log, where it will be forgotten.
Route the observations. For each item under "Worth remembering", check context/ for an existing file on the same claim:
- Second independent occurrence? It clears the repetition bar. Use the capture-feedback skill to promote it into context/ with the right confidence: level.
- First occurrence? Leave it in the log. One observation is an anecdote. Say so, and do not write it into context.

Rules

Append-only. Never edit yesterday's log to make it look better; add a dated addendum instead.
Absolute dates in the filename and the frontmatter.
Do not fabricate. If the user says "good call today", ask which account rather than inventing an outcome.