Get started
  1. Marketplace
  2. OpenChatly
  3. Use-case pack
Source
OpenChatly
Workspace
Use-case pack
Files
1
View source
Back

Brand mention monitor

Skill

Search, dedupe against the seen-mentions ledger, classify sentiment and notability, and post a digest with suggested response drafts — the daily brand-monitor runbook.

kortix marketplace install kortix-starter:brand-mention-monitor-skill
Proactive and schedule-driven; read-only against the public web, with a single Slack channel as the only output. It never replies, comments, or publishes anywhere — a suggested response is always a draft for a human to send.

Step 0 — Orient and resume

bash
cat memory/brand-monitor-log.md 2>/dev/null || echo "(no ledger yet — first run)"
Read every mention already reported before searching. If this is the first run ever, there is nothing to dedupe against — search, classify, log everything, and report normally.

Step 1 — Load the brand terms

{{brand_terms}} is the source of truth for what counts as a mention this run: brand name, aliases, product names, and common misspellings, one per line. Search for exactly these terms — no more, no less.

Step 2 — Search the web

Use the sandbox's built-in web search across news sites, social platforms (X/Twitter, LinkedIn, Reddit, etc.), and forums (Reddit threads, Hacker News, industry forums). Run one search per term in {{brand_terms}}, plus a news-specific pass. No login, no connector credential — public search only.

Step 3 — Fetch and normalize each candidate

Fetch the full text (or a substantial excerpt) of anything that looks like a genuine mention rather than an unrelated result. Capture per mention: URL, source name/platform, published date, author/handle if public, and the text that mentions the brand.

Step 4 — Dedupe against the ledger

Compute a stable fingerprint per mention (the URL, or a hash of URL plus the first few hundred characters). Compare against memory/brand-monitor-log.md. Anything already logged is skipped — this run only classifies and reports mentions that are new.

Step 5 — Classify sentiment and notability

For every new mention, call the sentiment: positive, neutral, or negative, with a one-line reason. Flag as notable anything that is:
  • Negative in sentiment.
  • High reach (large follower count, high upvotes/comments/shares).
  • From an influential source (press outlet, verified or large account).
  • Factually wrong about the brand in a way that could spread.
Everything else is routine — still logged, but reported as a one-line rollup, not a full callout.

Step 6 — Draft a suggested response for flagged mentions

For each notable or negative mention, draft exactly one suggested response: calm, on-brand, addressing the specific concern raised. Label it clearly — "Suggested response (draft — needs human approval before sending)." Never post it, reply with it, or publish it anywhere. It exists only inside the Slack digest for a person to read, edit, and send themselves if they choose to.

Step 7 — Compose and post the digest

One message to {{slack_channel}} per run:
  • A count of new mentions found and the sentiment breakdown.
  • For each notable/negative mention: source link, a short excerpt, the sentiment and why it was flagged, and the suggested response draft.
  • Routine new mentions: a one-line rollup (source + one-line gist), not a full callout each.
  • A quiet run (no new mentions): a brief note, not a wall of "nothing found."

Step 8 — Update the ledger

Append today's mentions to memory/brand-monitor-log.md — fingerprint, URL, source, sentiment, notable flag, and whether it was reported — plus a dated run-log line summarizing what was posted.

Related skills

Access policy

The role-to-grant policy, extra-scrutiny cases, the approval handshake, and how an applied grant gets logged.

account-research

Get a complete picture of any company or person before outreach. This skill always works with web search, and gets significantly better with enrichment and CRM data.

Ad performance review

Daily runbook for budget pacing, CPA/ROAS drift, underperformer detection, and anomaly flags across Google Ads and Meta Ads, plus how to rank and word optimization recommendations.

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

AP invoice matching

Extract-and-match runbook for incoming vendor invoices: line-item extraction, PO/prior-invoice matching, duplicate + overcharge detection, and the ledger + approval hand-off.

Call recap

Runbook for turning a finished call's transcript into a HubSpot deal update (or a flagged handoff when no deal matches), filed Linear tasks, and a drafted recap email.

Own your AI.Start today, in our cloud.

Start for free

OpenChatly is the AI workspace for everything. One person directing, agents executing, from goal to finished work.

©2026 OpenChatly AI.沪ICP备2025124785号-5

Resource guide

  • Product overview
  • Skills marketplace

Terms of service

  • User agreement
  • Privacy policy

Contact us