Agent Intelligence System

Your agent tracks the market so you don't have to. This skill turns any agent into an intelligence analyst — it monitors the sources that matter for your business, synthesizes signals into structured briefings, and surfaces trends before they become obvious.

Three modules. Use them independently or stack them.

Price: $79 one-time

---

What's included

Market Radar

Watches a defined set of sources and flags anything worth your attention. You configure the sources and topics once; the agent checks them on a schedule and delivers a filtered signal report — only the things that would change a decision, not everything that moved.

What it monitors (you configure):

• Hacker News: new submissions + Show HN + comments on relevant threads
• Reddit: specific subreddits, keyword alerts, top posts of the week
• Product Hunt: daily launches in your category
• GitHub: new repositories, trending, release notes for tools you use
• Competitor web: landing page changes, pricing page changes, new blog posts
• Job boards: who your competitors are hiring (leading indicator for product direction)

Outputs a structured signal report:

## Market Radar — [date]

### Signals worth acting on (>7/10 relevance)
- [Signal 1]: what happened, why it matters, recommended action
- [Signal 2]: ...

### Signals worth knowing (4-7/10 relevance)
- ...

### Low signal (FYI only)
- ...

Sources checked: [list]
Next run: [scheduled time]

---

CEO Briefing

Generates a morning intelligence brief. Format is fixed — short, scannable, decision-oriented. No filler. You wake up, read it in 90 seconds, and know what to act on.

Default briefing format:

## Morning Brief — [weekday, date]

### Revenue & metrics
[Current MRR / ARR, yesterday's sales, conversion rates if available]

### Top 3 priorities for today
1. [Priority] — [why, what done looks like]
2. [Priority] — ...
3. [Priority] — ...

### What's blocked
[Open blockers, who needs to act]

### Market signal (1 thing)
[One thing from yesterday's market radar worth knowing]

### Open loops
[Tasks assigned but not closed in >48h]

Customizing the brief:

• Edit the template to match your context (B2B vs consumer, team size, metrics you care about)
• Connect to your task tracker (Paperclip, Linear, Notion) to pull live blockers and priorities
• Connect to Stripe/PaddleHQ/LemonSqueezy to pull revenue numbers automatically

---

Trend Watcher

Runs weekly. Looks back at a rolling 30-day window of market signals and identifies patterns — what's accelerating, what's fading, what just emerged. This is the strategic layer on top of the daily radar.

Weekly trend report format:

## Trend Report — Week of [date]

### Accelerating (signal increasing over 4 weeks)
- [Trend]: evidence, relevant sources, what it means for you

### Emerging (appeared in last 2 weeks)
- [Trend]: ...

### Fading (signal decreasing)
- [Trend]: ...

### What this means for [your company/project]
[2-3 sentence synthesis: what you should adjust based on what you're seeing]

---

Installation

Step 1 — Configure your intelligence scope

Create a file at ~/.intelligence/scope.yaml:

company: "Your Company Name"
domain: "what you do / what market you're in"

sources:
  hacker_news:
    keywords: ["your keyword", "competitor name", "technology you use"]
    min_points: 50

  reddit:
    subreddits: ["r/YourNiche", "r/MachineLearning"]
    keywords: ["relevant term", "another term"]

  product_hunt:
    categories: ["AI", "Developer Tools"]

  github:
    topics: ["your-tech-stack"]
    watch_repos: ["competitor/repo", "tool/you-use"]

  competitors:
    - name: "Competitor A"
      url: "https://competitora.com"
      watch: ["pricing", "blog", "jobs"]

briefing:
  time: "08:00"
  timezone: "America/Los_Angeles"
  metrics_source: "manual"  # or: stripe, notion, paperclip

trend_watch:
  day: "monday"
  lookback_days: 30

Step 2 — Set up the Market Radar system prompt

Add this to your agent's instructions or use it as a system prompt for a dedicated intelligence sub-agent:

You are a market intelligence analyst. Your job is to monitor the sources in ~/.intelligence/scope.yaml, filter for signals relevant to [company name], and produce structured signal reports.

When running Market Radar:
1. Read ~/.intelligence/scope.yaml to understand scope and sources
2. Check each source for new activity since the last run
3. Score each signal for relevance (1-10):
   - 8-10: directly affects a decision the company might make this week
   - 4-7: good context, worth tracking
   - 1-3: noise, skip
4. Write the signal report to ~/.intelligence/radar-[date].md
5. Append a one-line summary to ~/.intelligence/radar-log.md

Do not include signals you scored below 4. Do not editorialize. State what happened, why it might matter, and what action (if any) makes sense.

Step 3 — Set up the CEO Briefing system prompt

You are a morning briefing assistant. Your job is to compile a CEO-level morning brief from available data and deliver it before 9 AM.

When generating the morning brief:
1. Read ~/.intelligence/scope.yaml for company context
2. Check ~/.intelligence/radar-[yesterday].md for yesterday's market signals (use the top signal only)
3. Read the task tracker for open blockers and today's priorities (adapt to your tracker)
4. If Stripe/revenue data is configured, pull last 24h revenue and compare to 7-day average
5. Identify any tasks open >48h without a status update
6. Write the brief to ~/.intelligence/brief-[date].md
7. Send it via Telegram or print to stdout

The brief should take under 90 seconds to read. If it would take longer, cut it. Priorities, blockers, one market signal, open loops. Nothing else.

Step 4 — Set up the Trend Watcher system prompt

You are a trend analyst. Every Monday, you review the last 30 days of market radar reports and identify patterns.

When running the trend watch:
1. Read all ~/.intelligence/radar-*.md files from the past 30 days
2. Cluster signals by topic/theme
3. Count signal frequency per theme per week
4. Identify: what's appeared more in recent weeks vs. earlier weeks (accelerating), what's new in the last 2 weeks (emerging), what appeared early but less recently (fading)
5. Write a trend report to ~/.intelligence/trends-[week].md
6. In the final section, write 2-3 sentences: given these trends, what should [company name] adjust or pay attention to?

Be concrete. "AI agents are getting more autonomous" is not a trend finding — "5 of 8 top HN posts about agents this month focused on multi-agent coordination vs. 1 of 6 last month" is.

---

Running on a schedule

With OpenClaw cron:

# Daily Market Radar at 7:30 AM
openclaw cron add \
  --name "market-radar" \
  --schedule "30 7 * * *" \
  --prompt "Read ~/.intelligence/scope.yaml. Run Market Radar. Check all configured sources for new signals since yesterday. Score and filter. Write report to ~/.intelligence/radar-$(date +%Y-%m-%d).md" \
  --channel telegram \
  --to "YOUR_TELEGRAM_CHAT_ID"

# CEO Brief at 8:00 AM weekdays
openclaw cron add \
  --name "ceo-brief" \
  --schedule "0 8 * * 1-5" \
  --prompt "Read ~/.intelligence/scope.yaml and yesterday's radar report. Generate morning brief. Send to Telegram." \
  --channel telegram \
  --to "YOUR_TELEGRAM_CHAT_ID"

# Weekly Trend Watch every Monday at 9:00 AM
openclaw cron add \
  --name "trend-watch" \
  --schedule "0 9 * * 1" \
  --prompt "Read the last 30 days of radar reports in ~/.intelligence/. Identify accelerating, emerging, and fading trends. Write trend report and send to Telegram." \
  --channel telegram \
  --to "YOUR_TELEGRAM_CHAT_ID"

---

Example: First run

Tell your agent:

"Run the initial Market Radar. Read scope.yaml, check Hacker News for anything about [your keywords] from the last 7 days, check r/[your subreddit] for posts with 50+ upvotes this week. Score and filter. Write the report."

After the first report, you'll know what to tune — keywords that are too broad, sources that are too noisy, categories you missed.

---

What this doesn't do

• Doesn't replace reading yourself — it filters, you decide
• Doesn't have real-time access to paywalled sources
• Doesn't track social media that requires authentication (Twitter/LinkedIn) without extra setup
• Trend detection requires at least 3-4 weeks of radar data to be useful

---

By ClawGear. More intelligence tools at clawgear.io