agent-pulse

name	agent-pulse
description	Operate and extend barretlee/agent-pulse, the evidence-backed AI industry intelligence system: inspect source catalog and lifecycle, collect and normalize signals, bind evidence, cluster Events, evaluate system health, generate Scout hypotheses, export the privacy-safe public site, and verify release gates. Use when the user asks to run, configure, debug, extend, or explain Agent Pulse, its collectors, Control Room, narratives, Scout, or GitHub Pages output. Triggers on: agent-pulse, Agent Pulse, evidence-backed intelligence, source catalog, signal collection, Event clustering, source audit, Scout opportunity, public export, weekly brief, or AI industry intelligence pipeline.
allowed-tools	Bash Read Write Edit Glob Grep WebFetch
compatibility	Requires the Agent Pulse repository, Node.js 22+, npm, and its documented local environment. SQLite is the zero-configuration default.
license	MIT
metadata	{"tags":"agent-pulse, ai-intelligence, evidence, source-catalog, collectors, event-clustering, scout, github-pages","version":"1.0","source":"https://github.com/barretlee/agent-pulse"}

Agent Pulse

Operate Agent Pulse as an evidence-backed intelligence system, not as a news aggregator. Keep facts, evidence, context, impact, judgment, and next signals distinct; make every public claim traceable to allowed source evidence.

When to use this skill

• The user wants to run Agent Pulse locally, refresh its repository snapshot, or inspect the Control Room and public site.
• The user needs to add, classify, test, activate, degrade, quarantine, or retire a data source.
• The user asks to collect signals, deduplicate or cluster Events, audit source health, or evaluate system capability.
• The user wants a narrative, weekly brief, Scout opportunity, or privacy-safe static export.
• The user is changing collectors, schemas, ranking, publication gates, source lifecycle, or public DTOs.
• The task is about Agent Pulse itself rather than generic web scraping or general research.

Instructions

Step 1: Capture the work packet

Record the requested outcome, affected plane, evidence boundary, and verification target:

• Outcome: operate, investigate, change code/schema, refresh data, publish, or research.
• Plane: server-only Control Room/database, collection pipeline, or public static export.
• Object: Source, SourceRun, Signal, Event, Track, Actor, Resource, View, Job, or Scout opportunity.
• Evidence: primary URL or paper, source tier, provenance, freshness, and uncertainty.
• Scope: one source, eligible batch, all sources, a narrative, or a release.
• Proof: focused test, npm run check, export validation, privacy scan, or browser smoke.

If the request is ambiguous, do not manufacture a publication decision. Ask for the missing target or leave the item in review/draft with its blocking reason.

Step 2: Read the project contract before editing

From the Agent Pulse repository root, read AGENTS.md and the relevant docs/specs first. At minimum, consult docs/ARCHITECTURE.md, docs/SOURCES.md, and docs/LEGAL.md for collection/publication work. Use the existing module boundary rather than inventing a source-specific exception:

• src/collectors/ owns SourceAdapter contracts, fetch safety, and adapters.
• src/domain/ owns pure URL, clustering, and scoring rules.
• src/db/ owns Kysely schema, migrations, repositories, and seed catalog.