← SynopticCONTENT HISTORY

Update to Synoptic

Snapshot Nov 17, 2026 · 00:12 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Synoptic 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": "Configure supported Synoptic source monitors and custom scraper targets for Twitter/X accounts, keywords, hashtags, cashtags, queries, follows or profile changes, Telegram channels, and GitHub repositories. Use when the user wants ongoing collection or a change to monitored sources.",
  "included_files": [],
  "name": "configure-source-monitoring",
  "skill_md_contents": "---\nname: configure-source-monitoring\ndescription: Configure supported Synoptic source monitors and custom scraper targets for Twitter/X accounts, keywords, hashtags, cashtags, queries, follows or profile changes, Telegram channels, and GitHub repositories. Use when the user wants ongoing collection or a change to monitored sources.\n---\n\n# Configure source monitoring\n\nSet up monitoring with existing Synoptic feeds and their supported target configuration. Creating a publishing stream does not set up a scraper. Coverage, target formats, update speed, delays, and account limits vary by feed.\n\n## Select the monitor and targets\n\nFind candidate feeds with `search`, then inspect them with `get_stream`. A Twitter/X feed for account posts, search queries, follows/unfollows, or profile changes does not cover the others. Telegram channels and GitHub repository activity need their matching provider feed. For news, filings, government releases, and other event feeds, use the source families in [read-streams](../read-streams/SKILL.md).\n\nFor a configurable feed, read `customTargetsData.targetType`, `targetTypeInstruction`, `targetValidationRegex`, and the target-count limits. Use the target syntax and case the feed requires. Handles, numeric account IDs, channel URLs, repository paths, keywords, hashtags, cashtags, and full search expressions are not interchangeable. There is no identity lookup tool; do not infer a numeric ID from a display name. Get a missing identifier from the user or a verified source before writing. A regex match validates syntax, not identity or source availability.\n\nIf an existing feed covers the request without custom targets, follow it when the user's setup request authorizes that. If no suitable configurable feed exists, explain what is missing. If the user asks to send a custom stream request, use [request-stream-or-feature](../request-stream-or-feature/SKILL.md); a submitted request is not an active monitor.\n\n## Save the selection\n\nCheck existing follows with `streams_following`. If the user asked to monitor an eligible stream they do not follow, call `follow_stream` before reading its target selection. Then read current targets with `get_stream_custom_targets`. Followers get their own selection; owners get the union of all followers' targets, which must not be copied as a personal selection. Report entitlement or target-limit errors; do not substitute a different monitor.\n\nChanging targets requires a direct subscription to the stream with a target allowance. A follow, package access, or organization access is not enough. With `subscriptions.read`, `get_stream_subscription` shows the direct subscription and its target allowance. If the entitlement is missing, explain what to set up in Synoptic; these tools cannot purchase it.\n\nUse `patch_stream_custom_targets` with `add` or `remove` for a narrow change. `set_stream_custom_targets` replaces the whole selection; an empty list clears it. Preserve unrelated targets. Posts for removed targets stop reaching the user; open Synoptic app feeds apply the change after they reconnect. Removed targets are then removed from the user's collection sources limited to specific targets; such a source left with no targets is deleted. `get_stream_custom_targets` needs `streams.read`; `set_stream_custom_targets` needs `following.write` and `workspace.write`; `patch_stream_custom_targets` also needs `following.read`.\n\nUse [manage-workspace](../manage-workspace/SKILL.md) to combine feeds in dashboards and apply include/exclude keywords, regex, or AI filters. Collection filters change which posts appear in a collection, not the scraper's targets.\n\n## Report what is established\n\nConfirm saved targets from the tool result, and use `get_stream_posts` to check recent updates when relevant. Report the stage reached: feed found, access obtained, targets saved, collection configured, or matching posts observed. An empty history page does not prove failure, and old matching posts do not prove the new targets are collecting. No tool reports scraper health.\n\nFor delivery into another application, use [connect-feed-to-app](../connect-feed-to-app/SKILL.md). Reading posts in this conversation does not start a background watch or keep an external consumer connected.\n"
}

SHA-256 of public snapshot: 4e7bfb76b459db23850552dbe492e28a8f037a2b6ef4964e5b6390faf5fa8082