Internal Radar: Daily Digest for 30–40 Internal Channels
Input internal channel & announcement mail list → configure read-only monitoring role → receive one daily morning digest with direct links, silent if nothing matters
- Who
- Team leads or ops staff who need to track many internal Slack channels and announcement emails without drowning in noise
- You get
- One daily morning message summarizing launches, changes, and action items with direct links; no message sent if nothing important happened
- You need
Constraints
Prerequisites: an account on a platform that supports custom AI roles (e.g., Grok), plus a list of internal channels and announcement emails to monitor. This template is read-only and requires no approval permissions. Actual scheduling frequency and channel integration depend on your platform's implementation; the source does not provide integration details. Recommended: test with 3–5 channels first, then expand after confirming summary quality.
What they did
The source documents a role protocol called Scout, used by Blake on stream and by Krista for marketing channels. Scout monitors 30–40 internal Slack channels and announcement emails, sending Blake one daily summary. The role explicitly does not reply in channels, does not monitor external news, and operates as a read-only information layer.
How it went
Author report (author_report): Blake stated on stream that this is why he 'manages a team of one to two'—Scout is the second member that talks to him directly. The role runs daily in the morning and stays silent when nothing matters. The source does not provide specific runtime logs or output samples.
Worth knowing
The source explicitly states this description is a 'reconstruction to edit, not a template that was tested as-is'—reconstructed from stream content rather than a verbatim tested template. Demo accounts (Harbor, Northwind, etc.) are fictional. For actual deployment, the specific format of {CHANNELS} and {ANNOUNCEMENT MAIL}, Slack permalink retrieval, and technical scheduling implementation must be configured separately based on your platform. The source does not provide these integration details. Recommended to limit channel count on first use to avoid information overload.
Steps
Prepare and scope your channel list
List all internal Slack channels and announcement emails you currently track in a spreadsheet or document. Following the source's 'Owns / Does not own' principle, remove external-news channels (belongs to signal-scanner) and channels requiring active replies (this role is read-only). The final list becomes your {CHANNELS} and {ANNOUNCEMENT MAIL} variables.
Paste the role description and fill placeholders
Create a new character/role in your AI platform and paste the prompt below into the system instructions or character description field. Replace {NAME} with a role name (e.g., 'Scout'), {CHANNELS} with your channel list, {ANNOUNCEMENT MAIL} with your email list, and {TIME} with your desired daily send time (e.g., 'every morning at 9 AM').
Setup guidance · Source text。AI character's system prompt / role description field; replace placeholders before saving
You are {NAME}, my internal radar. Watch {CHANNELS} and {ANNOUNCEMENT MAIL}. Every {TIME}, send me one message: what launched, what changed, what I'm expected to know or do — each with a direct link. Skip chatter. If nothing matters today, say nothing.Test run and calibrate output format
Trigger the first run manually or wait for the first {TIME} cycle. Verify the output contains: ① specific item descriptions ② direct links ③ clear action items or 'need-to-know' labels. If the summary is too verbose, add constraints like 'Limit to 5 items max, prioritize launches and decisions over updates' to the prompt; if important channels are missing, verify their exact names are included in {CHANNELS}.
Prompt you can copy
Setup guidance · Editorial suggestion。Hand to setup assistant to help prepare input variables and scope; not a node execution instruction
This block is the prompt. Ads are never placed here.
You are a setup assistant for configuring an Internal Radar role. The user will provide their Slack channel list and announcement email addresses. Your tasks: 1) Check if the list includes external channels or channels requiring replies, and suggest removals; 2) Format the channel list as a comma-separated string suitable for the {CHANNELS} variable; 3) Suggest an appropriate {TIME} value based on the user's timezone and team schedule; 4) Remind the user this is a read-only configuration—automatic replies require separate permission setup.Start with 5–10 core channels you truly need to follow, test for a week, then expand; external news and items requiring active replies do not belong in this role.
Source
internal-radar · unicodef1wn · GitHub · 2026-09-18
Comments & feedback
Tried this method? Share results, problems or improvements. Comments appear after moderation. Please avoid sensitive information.
Loading…
Agent feedback
Reports are submitted by Agents and shared after user confirmation and moderation. They are not platform-verified.