skills/strategic-scan/SKILL.md
Mandatory strategic pattern recognition process. Use when analyzing research, client work, or competitor tools to identify cross-client opportunities, build-vs-buy decisions, and ecosystem plays.
npx skillsauth add roviq-ai/agency-ops-center strategic-scanInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Don't just report findings. Connect the dots.
When research, client work, or competitor analysis reveals a tool, technique, platform, or advantage:
After every research phase completes, ask:
When you spot a cross-client opportunity:
❌ WRONG: "SERPCOM has a programmatic SEO platform called Prometheus. Here's what it does." (just reporting) ✅ RIGHT: "SERPCOM has Prometheus driving $250K/mo for a competitor. We should build our own version — Delivered, CH, and AC all need this. I'm spawning a research agent to evaluate build vs. buy." (connecting dots + taking action) ✅ ALSO RIGHT: "CCC data shows only 27 delivery operators in MA and exclusivity locked until 2029. That's not just good for Delivered — Roviq should position as THE cannabis delivery marketing agency in MA. There are 26 other operators who need what we're building for Delivered. That's a $50K+/year revenue opportunity per operator." (connecting client work → Roviq growth)
The COO doesn't just relay information. The COO sees the play — for the client AND for Roviq.
On 2026-02-10, the Prometheus platform was identified in SERPCOM research but only reported as a finding. Randy had to ask "should we make a better version?" The COO should have proposed this immediately upon seeing that a competitor's tool was driving $250K/mo and applied to multiple Roviq clients. This rule exists because strategic initiative > task completion.
tools
Fetches current top trending topics on X (Twitter) for any country using public aggregators.
development
Use when: user needs UX flows, information architecture, design critique, or design-system tokens. Don't use when: building a full static site (use frontend-design-ultimate) or redesigning an existing app (use human-optimized-frontend). Routing tree: "Building new site from scratch?" → frontend-design-ultimate; "Need UX critique or design tokens?" → ui-ux-pro-max; "Redesigning existing frontend with quantified eval?" → human-optimized-frontend; "Need design workflow (wireframe → theme → code)?" → frontend-design (superdesign); "Extracting design from existing codebase?" → frontend-design-extractor
development
Use when: generating a design system from brand colors. Don't use when: need full site build (use frontend-design-ultimate).
development
Use when: building new UI from scratch and need design workflow (layout → theme → animation → code). Don't use when: extracting design from existing code (use frontend-design-extractor) or need full production site (use frontend-design-ultimate). Routing tree: "Building new site from scratch?" → frontend-design-ultimate; "Need UX critique or design tokens?" → ui-ux-pro-max; "Redesigning existing frontend with quantified eval?" → human-optimized-frontend; "Need design workflow (wireframe → theme → code)?" → frontend-design (superdesign); "Extracting design from existing codebase?" → frontend-design-extractor