competitive-intel

Detect competitor changes and generate actionable intelligence for MCP-powered projects.

3|2|Updated Mar 6, 2026

Search Tags:#automation #monitoring #discovery #scoring #bootstrap #competitive-intelligence #watchlist

Ready to run

npx skills add https://github.com/cloga/optimus-code --skill competitive-intel-cloga

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: competitive-intel
Source: https://github.com/cloga/optimus-code/tree/main/optimus-plugin/skills/competitive-intel
Command: npx skills add https://github.com/cloga/optimus-code --skill competitive-intel-cloga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Autonomous competitive intelligence protocol detects meaningful competitor changes and translates them into actionable intelligence for MCP-powered projects.

Core Features & Use Cases

Bootstrap (auto-generate watchlist from project context), Discovery (weekly competitor search), and Monitor (daily lightweight check) execution modes to cover the lifecycle of competitive intelligence.
Conservative reporting discipline with structured scoring, bounded search, and strict watchlist mutation rules to minimize noise.
Use when triggered by Meta-Cron for competitive monitoring to inform product strategy and roadmap decisions.

Quick Start

Trigger a Meta-Cron cycle to run competitive-intel monitoring for your MCP-enabled project.

Frequently Asked Questions about competitive-intel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate competitor monitoring for an MCP-powered project?▼

Automate competitor monitoring for an MCP-powered project by triggering a Meta-Cron cycle to run the competitive-intel protocol, which detects meaningful competitor changes and translates them into actionable intelligence. It uses Bootstrap, Discovery, and Monitor modes to cover the competitive intelligence lifecycle.

What is the best way to bootstrap a competitor watchlist from project context?▼

The best way to bootstrap a competitor watchlist from project context is to use the Bootstrap execution mode. This mode automatically generates a watchlist based on your project context, establishing a baseline for subsequent weekly discovery and daily lightweight monitoring.

How does competitive intelligence scoring minimize noise during daily monitoring?▼

Competitive intelligence scoring minimizes noise during daily monitoring by applying conservative reporting discipline. It uses structured scoring, bounded search, and strict watchlist mutation rules to ensure only meaningful competitor changes are reported, maintaining clear provenance for every fact.

Can I schedule weekly competitor discovery and daily monitoring separately?▼

Yes, you can schedule competitor discovery and monitoring separately because the protocol operates across distinct execution modes. It performs weekly competitor search in Discovery mode and daily lightweight checks in Monitor mode to inform product strategy and roadmap decisions.

Do I need to manually curate the competitor watchlist during automated discovery?▼

You do not need to manually curate the competitor watchlist during automated discovery because the protocol enforces strict watchlist mutation rules. It automatically manages the watchlist through bounded search and structured scoring with clear provenance for every fact.