Add the MCP server ▸
Assistants and access8 of 8 ▾

Support/Assistants and access

Audit a post before it goes out

Ask your assistant to audit a draft, or run syndera posts audit. Claude reads it against the brand’s site, its rules, its other posts and its Intel brief, and reports what to look at with the source behind each. It changes nothing and blocks nothing.

How-toUpdated 9 Nov 2026

An audit is a careful read before a post goes out. It looks for:

  • a claim the brand’s website doesn’t back up;
  • a broken Always or Never rule, or a line off the brand’s voice;
  • a hook a competitor already owns, or a claim any competitor could make (once the brand has an Intel brief);
  • a repeat of another post, a date that’s off, or something a network treats badly.

Each finding says where it is in the post, what shows it, and usually a fix. Findings are warnings: nothing on the post changes, and nothing stops it from being scheduled.

From your assistant

Ask it to audit a post, or a brand’s drafts before they go out. With the syndera-strategist skill it audits each one, then reads them together for repeats and clashing claims, and offers fixes you can say yes or no to.

Audit next week's Tickleaf posts before they go out.

From the CLI

syndera posts audit <post-id>

--last shows the latest audit without running a new one. --dismiss f1 hides a finding you’ve decided to keep as it is.

From the API

POST /v1/posts/{id}/audit runs one; GET /v1/posts/{id}/audit returns the latest, with stale once the post changed after it. See the API reference.

What it uses

Each audit is one AI call from your plan’s allowance. Running it again replaces the last one.

Was this helpful?