Run any Skill in Manus with one click

context-hygiene

Stars0

Forks0

UpdatedJuly 15, 2026 at 08:18

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.

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	context-hygiene
description	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.

Context hygiene pass

The context layer is only useful if agents can trust it. Run this audit periodically or when onboarding a new team member.

Steps

Mechanical lint. Run npm run lint:context. Fix every error (missing title/description, broken references: entries, broken wikilinks or relative links). Errors block CI; do these first.
Orphans. The linter warns about files nothing references. For each orphan, decide: link it from the file that should own the relationship, or delete it if it no longer earns its place. Do not leave orphans standing.
Staleness. The linter warns about files untouched for more than 90 days. For each, check it against reality: recent won/lost deals in context/client/, current pricing, live positioning. Update the file or add a dated note explaining why it is still accurate.
Contradictions. Read global/ and icp/ together and flag claims that conflict (two different ICPs, outdated competitor claims in alternative/). Surface contradictions to the team in the PR description rather than silently picking a side.
Ship it. One PR titled context: hygiene pass YYYY-MM-DD, with a summary table: files fixed, orphans resolved, stale files refreshed, contradictions flagged.

Rules

Never invent facts to fill a template. An honest gap beats a plausible lie; leave the section empty with a TODO(owner): marker.
Preserve frontmatter fields you do not understand.

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

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

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	context-hygiene
description	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.

Context hygiene pass

The context layer is only useful if agents can trust it. Run this audit periodically or when onboarding a new team member.

Steps

Mechanical lint. Run npm run lint:context. Fix every error (missing title/description, broken references: entries, broken wikilinks or relative links). Errors block CI; do these first.
Orphans. The linter warns about files nothing references. For each orphan, decide: link it from the file that should own the relationship, or delete it if it no longer earns its place. Do not leave orphans standing.
Staleness. The linter warns about files untouched for more than 90 days. For each, check it against reality: recent won/lost deals in context/client/, current pricing, live positioning. Update the file or add a dated note explaining why it is still accurate.
Contradictions. Read global/ and icp/ together and flag claims that conflict (two different ICPs, outdated competitor claims in alternative/). Surface contradictions to the team in the PR description rather than silently picking a side.
Ship it. One PR titled context: hygiene pass YYYY-MM-DD, with a summary table: files fixed, orphans resolved, stale files refreshed, contradictions flagged.

Rules

Never invent facts to fill a template. An honest gap beats a plausible lie; leave the section empty with a TODO(owner): marker.
Preserve frontmatter fields you do not understand.