
Proactive Intelligence
Teach your coding agent to fetch fresh web data, re-pull APIs, and run freshness checks on its own when context looks stale or incomplete.
Overview
Proactive Intelligence is a journey-wide agent skill that autonomously seeks external information—web search, API re-pulls, and freshness checks—whenever a solo builder’s agent detects stale or incomplete context during
Install
npx skills add https://github.com/itallstartedwithaidea/agent-skills --skill proactive-intelligenceWhat is this skill?
- Detects insufficient, stale, or contradictory context and acts without waiting for an explicit user prompt
- Supports autonomous web search, API re-pulls, and data freshness checks mid-analysis
- Modeled on Buddy™-style proactive search_web for benchmarks, policies, and competitor context
- Shifts agents from passive processors to active investigators for richer answers
Adoption & trust: 1 installs on skills.sh; 18 GitHub stars; 1/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
Your agent answers from whatever you pasted in, even when live benchmarks, policies, or API state would change the recommendation.
Who is it for?
Tool-enabled agents in domains where facts change quickly (ads, APIs, compliance, market data) and you want autonomous gap-filling during deep analysis.
Skip if: Fully offline or air-gapped workflows, or when you require every external call to be explicitly approved before it runs.
When should I use this skill?
The agent is analyzing a problem and may need fresher or external context than the current prompt and repo provide.
What do I get? / Deliverables
The agent independently fills knowledge gaps during analysis so results stay current, better grounded, and more complete without you micromanaging every lookup.
- Proactive lookup behavior wired into analysis flows
- More current, externally grounded agent conclusions
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Agent re-pulls a partner API when cached campaign metrics look inconsistent with the dashboard.
Before signing off a launch checklist, the agent searches for recent platform policy changes that affect the feature.
When conversion rates diverge from norms, the agent fetches industry benchmark ranges for comparison.
During an incident thread, the agent looks up known outage or deprecation notices instead of guessing root cause.
While sizing an opportunity, the agent proactively gathers competitor positioning you did not paste in.
How it compares
Use as procedural agent behavior atop your existing search/MCP tools—not a replacement for defining those tools or for manual research-only chat.
Common Questions / FAQ
Who is proactive-intelligence for?
Solo and indie builders running Claude Code, Cursor, Codex, or similar agents who need analysis that stays aligned with live external data, not just repository context.
When should I use proactive-intelligence?
During Build when designing agent tools, during Ship when validating assumptions before release, during Grow when interpreting metrics against benchmarks, and during Operate when investigating anomalies—whenever analysis should trigger its own lookups.
Is proactive-intelligence safe to install?
It implies network and possibly browser/API access when the agent acts proactively; review the Security Audits panel on this page and your agent permission settings before enabling autonomous fetches.
SKILL.md
READMESKILL.md - Proactive Intelligence
# Proactive Intelligence Part of [Agent Skills™](https://github.com/itallstartedwithaidea/agent-skills) by [googleadsagent.ai™](https://googleadsagent.ai) ## Description Proactive Intelligence enables agents to autonomously seek out external information — web searches, API re-pulls, data freshness checks — during analysis without waiting for explicit user requests. Traditional reactive agents only work with the data provided to them. Proactive agents recognize when their current context is insufficient, stale, or contradictory, and take independent action to fill knowledge gaps. This transforms the agent from a passive processor into an active investigator that delivers more accurate, more current, and more comprehensive results. This skill is modeled on the `search_web` tool integration in the Buddy™ agent at [googleadsagent.ai™](https://googleadsagent.ai), where the agent autonomously searches for competitor data, industry benchmarks, recent Google Ads policy changes, and platform updates when it detects that such information would improve its analysis. When Buddy™ encounters a campaign strategy it hasn't seen before, or metrics that deviate significantly from expected ranges, it proactively searches for context rather than speculating. This behavior is triggered by explicit conditions, not random curiosity, ensuring the additional latency and cost are justified. The proactive intelligence framework operates on a trigger-search-integrate cycle: the agent evaluates trigger conditions during analysis, dispatches targeted searches when conditions are met, scores the relevance and freshness of results, and integrates verified findings into its ongoing reasoning. Confidence scoring ensures the agent distinguishes between well-supported conclusions and speculative ones. ## Use When - The agent analyzes data that may be affected by recent external changes (policy updates, market shifts) - Competitive intelligence is needed alongside internal data analysis - The agent encounters unexpected patterns that need external context to explain - Data freshness is critical and the provided data may be outdated - Industry benchmarks or best practices are needed to contextualize performance - The agent must fact-check its own assumptions against current sources ## How It Works ```mermaid graph TD A[Agent Analysis] --> B[Trigger Evaluator] B -->|No Trigger| C[Continue Analysis] B -->|Trigger Fired| D[Search Strategy Selector] D --> E{Search Type} E -->|Web Search| F[search_web Tool] E -->|API Re-pull| G[Data Refresh] E -->|Benchmark Lookup| H[Industry Database] F --> I[Result Scorer] G --> I H --> I I --> J{Relevance Score} J -->|High| K[Integrate into Analysis] J -->|Low| L[Discard + Note] K --> M[Update Confidence Score] L --> M M --> C ``` The trigger evaluator runs continuously during analysis, checking predefined conditions: data anomalies (metrics outside expected ranges), knowledge gaps (encountering unfamiliar strategies or terms), staleness indicators (data older than a threshold), and explicit search cues (user mentions competitors or asks "is this normal"). When a trigger fires, the search strategy selector determines the most efficient information-gathering approach. Results are scored for relevance and freshness before integration, and the agent's confidence score is updated to reflect whether the proactive search strengthened or weakened its conclusions. ## Implementation **Trigger Condition Engine:** ```python class TriggerEngine: def __init__(self): self.triggers = [ AnomalyTrigger(), StalenessTrigger(max_age_days=7), KnowledgeGapTrigger(), Compe