Systems Lab

Agent skill

review

A full pass over one tool in the Software directory, confirming everything on the row is still true, and the only skill that moves Last reviewed after creation stamped it.

activeNeeds a keyDeclared tools490 words

Filed under Onboarding, retention and expansion.

From sarahcallmesmadds/gtm-operator · 27 skills · 0 · pushed 2026-09-02

What it does when it runs

A full pass over one tool in the Software directory, confirming everything on the row is still true, and the only skill that moves Last reviewed after creation stamped it. Use before a renewal, when somebody who owned a tool leaves, when a row's freshness stamp is old, or when the user says "review this tool", "is this row still right", "sweep the directory". Stamps the date only on a confirmed pass; writes nothing without an explicit yes.

Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
  • mcp__*__notion-fetch
  • mcp__*__notion-query-data-sources
  • mcp__*__notion-update-page
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
  • Write
  • Bash(node:*)
  • mcp__*__notion-fetch
  • mcp__*__notion-query-data-sources
  • mcp__*__notion-update-page
Actions present in the files
shellwrites files

Ask about review

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah

Install it

View source on GitHub ↗
git clone --depth 1 --filter=blob:none --sparse https://github.com/sarahcallmesmadds/gtm-operator.git /tmp/gtm-operator
git -C /tmp/gtm-operator sparse-checkout set "plugins/software/skills/review"
mkdir -p ~/.claude/skills/review
cp -R "/tmp/gtm-operator/plugins/software/skills/review/." ~/.claude/skills/review/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

Or take the whole library

This repo ships a .claude-plugin manifest, so Claude Code can install all 27 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.

/plugin marketplace add sarahcallmesmadds/gtm-operator
/plugin

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Before you install: this skill will not complete its job on a bare agent. It needs mcp__*__notion-fetch, mcp__*__notion-query-data-sources, mcp__*__notion-update-page, which you have to obtain separately.

The skill

Source on GitHub ↗

Reproduced in full from sarahcallmesmadds/gtm-operator/blob/a93c6e98a742d183823691197b8d9be9edd114c6/plugins/software/skills/review/SKILL.md, which is licensed MIT (repository). 490 words, 6 headings.

review

What "reviewed" means, and holding the line on it.

The failure mode this skill exists to prevent: a sweep that opens forty rows, changes nothing, stamps forty dates, and leaves a directory that looks maintained and is not. A review that finds nothing wrong is a real review and stamps the date. A review that did not look is not. The difference is whether each group was actually asked about.

How this skill works

node "${CLAUDE_PLUGIN_ROOT}/scripts/software.js" review <changes.json> <existing.json> [--confirmed] --today YYYY-MM-DD
node "${CLAUDE_PLUGIN_ROOT}/scripts/software.js" prove-update <output.json> <readback.json>

Fetch the row and save the whole page. Walk the groups in order, asking about each:

  1. Who owns it. Owner, technical owner, admins, billing owner — still the right people? Somebody who left is cleared or replaced by name.
  2. What we pay and until when. The contract dates, the notice deadline, the cost, how it renews. Before a renewal this group is the reason the review is happening.
  3. What it holds. The security group — and do not change those answers without asking, because they came from somewhere, and replacing them silently loses the fact that they were checked.
  4. Whether it is still in use. Status, audience, what is wired to it. A tool being wound down moves to Sunsetting, the one state somebody outside the owning team needs to see. A tool that is gone goes to Retired; the row stays. A change to Integrates with is reported, never written: it is a relation, no plugin here has measured a relation write on this surface, and the script refuses the field. Name what should be linked or unlinked so a person can make the change in Notion — the blast-radius map is maintained by people, through what a review surfaces.

The stamp

After the walk, ask plainly: did this count as actually confirming the row? Only a yes earns --confirmed, and only --confirmed moves Last reviewed. The same gate process:update uses for Verified by. Changes found along the way are written either way; the date is what the confirmation governs.

Batch mode

Reviewing forty rows in a sitting is real use and its shape is deliberately undesigned (open question 1 in plugins/software/SKILLS.md). Until it is designed: one row at a time, each with its own walk and its own confirmation. Refuse the shortcut of one confirmation covering forty rows — that is the forty stamped dates with nothing confirmed.

Then prove it

Send the update, re-fetch the page, and run prove-update with the command's own output. The stamp is proved by the date coming back, not by the call returning.

What this skill does not do

  • Does not stamp on a glance. No confirmation, no date.
  • Does not archive or delete a row. Retired keeps the history.
  • Does not change the security group silently.
  • Does not create rows or fill person fields nobody named.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what review does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.