Skip to main content
Use this workflow when an operator asks an agent to find LinkShot videos, return view-proof screenshots, or add dated links for future view checks. The in-app control surface is /tools/linkshot/settings.

​
Core Rule

Read existing DealDash proof before browsing. If the operator says: 
/linkshot views may 22 LAMBA300 send screenshots and links if already there
DealDash should parse the date, expand it by the configured fallback window, query LinkShot View Logs, and return the normal completed-copy payload when proof already exists.

​
Tool Hierarchy

RankTool pathPurpose
1Slash parser and date normalizerRuns in code, not agent reasoning.
2deals.view_logs / /api/deals/view-logsFinds existing proof and copy-ready screenshot/source links.
3deals.due_views and screenshots.list_latestNarrows candidate search before browsing.
4linkshot_evidenceRanks candidates and creates proof-capture jobs without writes.
5Browser or local LinkShot extensionUsed only when platform/session data is needed.
6Screenshot capture and verifierConfirms highlight, view count, URL, date, duplicates, and notes.
7deals.bulk_add_view_checks or approved write pathPersistent writes after verifier acceptance.

​
Slash Commands

Aliases:
  • /linkshot
  • /ls
  • /dealdash-linkshot
Date formats:
  • may 22
  • may 21-23
  • 22 may
  • 22/05/2026
  • 22/05/26
  • 2026-05-22
  • today, yesterday, tomorrow
Examples:
CommandBehavior
/linkshot views may 22 LAMBA300Return existing proof if present.
/ls proof 22/05/26 lordlambaLookup by creator/account text.
/linkshot logs may 21-23 mrcuteSearch a date range.
/linkshot status may 22 LAMBA300Read due/completed state.
/linkshot capture may 22 @lordlambaPlan proof capture; no auto-write.
/linkshot bulk import 2026-05-22 <links>Prepare the LinkShot bulk import endpoint.
Instruction words such as send, screenshots, links, usual, and already there are stripped from the search query so promo codes and creator names stay clean.

​
Settings Page

/tools/linkshot/settings stores local defaults:
  • Include shared view logs.
  • Use local extension capability when cloud browsing lacks a session.
  • Prefer English platform pages where available.
  • Require verifier before writes.
  • Expand date lookup by fallback days, default 1.
  • Set the highlight color for local capture plans.
The page calls /api/deals/view-logs with normalized from, to, q, scope, and limit=50. It also builds the matching View Logs deep link, for example: 
/screenshots?tab=logs&from=2026-05-21&to=2026-05-23&q=LAMBA300
When rows exist, copyText uses linkshot-extension-completed-copy-v1, the same format used by the LinkShot extension completed-copy action and the website View Logs copy buttons.

​
Workflow Diagram

​
Evidence States

​
Verifier Checklist

  • Platform page is in English when supported.
  • Screenshot shows the relevant video/post page, not only a feed or generic account page.
  • Highlight is visible and does not cover the view count or proof text.
  • Source video URL, screenshot link, checked date, and views stay together.
  • One day before and one day after are checked when fallback is 1.
  • Duplicates are checked by canonical URL, video id, promo code, deal, and checked date.
  • Uncertain rows are returned with notes instead of written silently.
  • Include observedPromoAtSeconds when it is visible or cheaply available.

​
Local Tokens

Cloud agents should use DealDash reads first. Local LinkShot/browser tokens are optional and should stay on the user’s machine. When Nox or another local agent uses the LinkShot extension, it may collect page data from dd_auth and the browser profile, but the cloud handoff should include only sanitized URLs, dates, screenshot links, view counts, and notes. Never paste tokens, cookies, service secrets, database URLs, or raw browser storage into chat.

​
Local QA

For browser smoke tests, start the app with background jobs disabled: 
DISABLE_BACKGROUND_JOBS=true pnpm dev:full
Plain pnpm dev:full starts Sheets sync and reminder processors. Do not use it for read-only UI smoke tests against shared or production-like data.

​
Write Policy

Existing proof lookup is read-only. Adding dated post/video links for future view checks should use deals.bulk_add_view_checks or POST /api/agent/deals/bulk-import/process. Do not use generic deal create/update for LinkShot view-check imports. Persistent proof/view-log writes require verifier acceptance and the active DealDash approval policy.