← LinkedditCONTENT HISTORY
WHAT CHANGED
Update to Linkeddit
Snapshot Nov 5, 2026 · 01:16 UTC · version 1.0.2
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Linkeddit and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Turn Linkeddit competitor monitors, briefs, switching signals, and page snapshots into an evidence-backed competitive update or battlecard when users ask about competitor moves or market changes.",
"included_files": [],
"name": "competitor-intelligence-brief",
"skill_md_contents": "---\nname: competitor-intelligence-brief\ndescription: Turn Linkeddit competitor monitors, briefs, switching signals, and page snapshots into an evidence-backed competitive update or battlecard when users ask about competitor moves or market changes.\n---\n\n# Competitor intelligence brief\n\nUse `list_competitor_monitors` to resolve the competitors and monitor IDs available to this account. A tracked competitor is not access to that company's private account. Use the current connected tool schemas and avoid inventing missing IDs or records.\n\nFor one competitor, retrieve `get_competitor_brief`. For a weekly overview, start with `get_weekly_brief`, using the requested week if supplied. Add `get_switching_signals` or `get_competitor_changes` only when they help answer the request. Respect the actual returned window, generation date, limits, and missing data; a latest brief may be older than the requested period.\n\nDistinguish competitor announcements, buyer complaints, observed changes, and your interpretation. For page comparisons, compare snapshots of the same URL at different timestamps. A changed hash establishes a page changed; it does not prove a specific price or feature changed. Summary snippets may be truncated; request the tool's raw mode where available before making precise comparisons.\n\nDeduplicate repeated reports of the same event. A single complaint or switching signal is evidence of that instance, not a market-wide trend or confirmed purchase. Report conflicting evidence and the number and independence of sources where known.\n\nProduce the requested brief or battlecard with dated evidence links, implications for the user's product, and suggested responses. Separate verified product facts from positioning ideas. If no current brief exists, say so rather than inventing one. Do not create monitors, contact prospects, or publish comparisons as a side effect of producing a brief.\n"
}SHA-256 of public snapshot: 60f04c529e7331fb9ad2fdaa55f091fb288aa27d78374ae45b29bba8151ddffa