← ClayCONTENT HISTORY

Update to Clay

Snapshot Nov 18, 2026 · 06:19 UTC · version 2.38.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Clay and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Review Clay sequence (formerly campaign) email copy as the intended recipient and identify only material, actionable objections.",
  "included_files": [],
  "name": "sequences-reviewing",
  "skill_md_contents": "---\nname: sequences-reviewing\ndescription: Review Clay sequence (formerly campaign) email copy as the intended recipient and identify only material, actionable objections.\n---\n\n# Clay sequence reviewing\n\nBefore using this skill, read the `clay` entry skill if you haven’t already this session, and follow its access guidance.\n\nIf the `sequences` skill is not already loaded, load it before acting. Use it for sequence discovery, context, target selection, commands, and mutation boundaries. Use this skill for sequence-review decisions.\n\nUse this skill after drafting or revising sequence copy, or when the user asks for a review. The same agent that writes the copy performs the review.\n\nBecome the specific intended recipient: busy, skeptical, and triaging the inbox. Read from that person's actual situation, not as a generic copy editor. Center the review on one honest question: “Why wouldn’t I respond?”\n\n## Review order\n\nReview message strategy before copy execution. Determine whether the recipient, situation, problem or opportunity, mechanism, value, offer, and requested response form a credible reason to engage. Then review how clearly and effectively the copy executes that strategy.\n\nUse specificity, credibility, relevance, value exchange, ask size, and spam patterns as lenses rather than a checklist. Raise only concerns that would materially affect the intended recipient. Never invent an objection when the copy is strong.\n\n## Critiques and revisions\n\nKeep each critique concise and self-contained. Identify:\n\n- the exact email or passage targeted;\n- the recipient's material concern; and\n- the direction of the change that would address it.\n\nFor a targeted change, read enough surrounding sequence copy to detect a material contradiction it would introduce or expose. Keep this check scoped; do not turn it into a full-sequence audit. Never change linked copy outside the requested scope. Flag the contradiction and ask the user through the question tool to expand the scope before changing that copy.\n\nWhen revision is requested, revise only the affected passage and preserve everything else. For review-only work, return the critique without rewriting or mutating the sequence.\n\n## Stop conditions\n\nStop the review loop when no material copy-fixable concern remains. Also stop when an issue requires missing facts or proof, the choice is a judgment call with no clearly better option, another change would only polish already-effective copy, or the offer or strategy must change before copy can improve.\n\nPut non-copy-fixable concerns under `Unresolved`. Do not rewrite around missing evidence or a strategy problem.\n"
}

SHA-256 of public snapshot: 98c7843ccc245a9be76b1177d85583d33adfa0922354ef6f6634e92a67ad93aa