← RetenoCONTENT HISTORY

Update to Reteno

Snapshot Nov 18, 2026 · 06:17 UTC · version 0.4.1

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Reteno 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": "Create, edit, inspect or count Reteno dynamic segments with live account definitions and the bundled Segment Designer SDK. Use for audience conditions, exclusions, event windows, segment changes and unsaved audience calculations. Does not require a browser or a saved segment for counting.",
  "included_files": [
    {
      "relative_path": "OPERATING_MANUAL.md",
      "size_in_bytes": 3152
    },
    {
      "relative_path": "agents/claude.yaml",
      "size_in_bytes": 233
    },
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 233
    },
    {
      "relative_path": "references/client/SDK_API_REFERENCE.md",
      "size_in_bytes": 21503
    },
    {
      "relative_path": "references/client/catalogs/condition-operators.md",
      "size_in_bytes": 9087
    },
    {
      "relative_path": "references/schema/segment-output.schema.json",
      "size_in_bytes": 17581
    },
    {
      "relative_path": "scripts/extract_condition_operator_rows.mjs",
      "size_in_bytes": 7162
    },
    {
      "relative_path": "scripts/run_sdk.mjs",
      "size_in_bytes": 11766
    },
    {
      "relative_path": "scripts/segment_catalog_store.mjs",
      "size_in_bytes": 6939
    }
  ],
  "name": "segment-designer",
  "skill_md_contents": "---\nname: segment-designer\ndescription: Create, edit, inspect or count Reteno dynamic segments with live account definitions and the bundled Segment Designer SDK. Use for audience conditions, exclusions, event windows, segment changes and unsaved audience calculations. Does not require a browser or a saved segment for counting.\n---\n\n# Segment Designer\n\nRead [OPERATING_MANUAL.md](OPERATING_MANUAL.md) before building a segment. The local runner\nvalidates and prepares a request; the host calls the selected authenticated Reteno MCP.\nUse the installed skill directory, not a path relative to the user's project.\n\n1. Resolve the selected organization through MCP. Fetch `list_segment_definitions(for_sdk=true)`;\n   for an edit pass the target `segment_id`. Save the manifest and download its `catalogRef`\n   with `<plugin-root>/scripts/transfer.py`. Keep its SHA-256, expiry and account binding.\n2. Read the relevant definitions and [SDK reference](references/client/SDK_API_REFERENCE.md).\n   Resolve exact field, event, application and option IDs through live MCP. Never invent them.\n3. For an edit, call `get_segment(segment_id=..., include_schema=true)` and save the complete\n   result. The runner hydrates its backend schema before applying a bounded SDK mutation.\n4. Write a JavaScript module using the supplied `segment` handle, check each mutation result,\n   and return `segment.finish()`. Run the command in the manual. Review diagnostics and the\n   formula, including include/exclude logic and date interpretation.\n5. Call the tool and arguments from the generated request file through the same MCP connection.\n   Local `persisted:false` is preparation only. Verify the response with\n   `python3 <plugin-root>/scripts/receipts.py segment --response <receipt> [--expected-id <id>]`.\n   The backend verifies retrievability, not byte equality of its normalized schema. Inspect\n   fresh conditions and explain that distinction when exact semantic verification is unavailable.\n6. Retain the destination ID. On an ambiguous create, find the exact name before any retry;\n   never create duplicates because read-back failed. On edit, re-read and reconcile intervening\n   changes rather than overwriting them from an old export. There is no server hash precondition.\n\nFor audience size only, use `--mode count`; call `count_segment_contacts` and verify with\n`receipts.py count`. Never save a segment merely to count. Use `get_segment_contacts` for an\nexisting saved segment. Read [audience guidance](../reteno-analytics/references/audience-counts.md)\nfor population scope, rate limits, unknown outcomes and partial comparisons.\n\nReteno channels only. Viber and Telegram are unavailable even if a generic upstream catalog\nmentions them. Do not import private warehouse data or change contacts.\n"
}

SHA-256 of public snapshot: a68f00ce54346ae70fef6635c6249e84833e83354c1b80f3163aebf243c52f1e