Competitor Monitoring Flow
Marketing Official v1.1.27Ongoing competitor marketing surveillance, messaging analysis, and response planning
by skrptiq
Sign in to import this skrpt into your workspace.
Sign inWhat's included 15 nodes
Competitor Monitoring Flow
Ongoing competitor marketing surveillance, messaging analysis, and response planning
Market Signal Detection
Identifies and interprets significant competitive signals from market activity, announcements, and behavioral changes
Messaging Analysis
Deconstructs competitor messaging to identify positioning strategies, value propositions, and messaging patterns
Messaging Comparison Matrix
Building a side-by-side comparison of messaging, positioning, and value propositions across all tracked competitors
Monitoring Report Writer
Compiling a periodic competitive monitoring report from the messaging matrix, threat assessment, and market signals
Threat Assessment
Assessing competitive threats by severity and urgency and recommending prioritised defensive and offensive responses
Campaign Tracker
Analyzes a competitor's recent campaigns and extracts marketing tactics, messaging, and strategic intent
Competitor Audit Prompt
Produces a thorough audit of a competitor's marketing presence across all channels
Messaging Comparison Matrix
Compares messaging, positioning, and value propositions across competitors in a structured matrix
Monitoring Report Writer
Compiles a periodic competitive monitoring report from audit data, signal analysis, and threat assessments
Threat Assessment Prompt
Assesses competitive threats and recommends defensive and offensive marketing responses
Competitive Marketing Framework
Structured framework for systematic competitive marketing analysis and monitoring
Competitor Monitoring Playbook
Step-by-step guide to establishing and running an ongoing competitor monitoring program
Competitor Audit Template
Structured template for documenting a thorough competitor marketing audit
Monitoring Report Template
Structured template for periodic competitive monitoring reports
Requirements 1 service, 1 permission, 3 data types
- LLM Service
- network:web-search
- pii
- competitor information
- market data
Security Passed
Detected
- Services: llm-service
- Permissions:
- Data Handling:
Version history 17 releases
GH#863 Wave 1 — fix the K-045 intent/output mismatch: the bundle shipped the `messaging-comparison-matrix`, `threat-assessment-prompt`, and `monitoring-report-writer` prompts (the monitoring report being the real deliverable) and the docs said to run them, but the `execution:` block never invoked any of them — so the periodic report was never produced. Restored the intended bound graph: added **Messaging Comparison Matrix**, **Threat Assessment**, and **Monitoring Report Writer** execution steps (each with a backing skill so it is `from_step`-addressable), ordered `messaging-analysis → messaging-comparison → market-signal-detection → threat-assessment → audience-segmentation → monitoring-report`, and rewired every cross-step input to an explicit `from_step` binding (`{{step.context.*}}`) instead of positional `{{steps.previous.output}}` / `{{steps.<Title>.output}}` refs. The monitoring report is now the last content step and receives the messaging matrix, threat assessment, and market signals. Also repinned `polish-language` 1.0.1→1.0.6 (the version exposing the bindable `source` slot) and bound `language-polish`'s `source` ← the Monitoring Report Writer output, so the `output_step` polishes the actual report rather than its positional previous. No new required inputs.
GH#845 — republish with American English (en-US) content, completing the source-only GH#805 flip that never reached the Hub. Copy only — no functional or behaviour change.
GH#745 — declare per-step `output: {name, type}` on every execution step (messaging_analysis/text, market_signals/text, audience_segments/list, polished_report/text). Lights up the #744 rich flow-map. Content-only; no bindings or logic changes.
GH#645 Row 3b — migrate to K-037 dep-referenced schema. Strip 6 inline shared-content files and declare 6 hub-shared deps (UUID id + slug name + version + checksum from `gen-dep-checksums.mjs`). Closes pre-Step-3 inline-vendoring for this bundle.
Wave 2: re-signed with canonical engine signing pipeline.
Signature fix — RELEASE_NOTES.md now included in integrity checksum.
Initial catalogue release with full structural and content-quality validation. All scanner checks pass.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
Release notes unavailable for this version.
More from Marketing
View all →Campaign Launch Pipeline
End-to-end campaign creation: brief, audience segmentation, copy, and launch plan
Product Launch Marketing Flow
Go-to-market marketing plans for product launches — messaging, channels, timeline, and measurement
Social Media Analytics Flow
Social media performance analysis, content strategy optimization, and audience insight extraction