skills/cali-product-workflow/skills-strategic-analysis/cali-product-multi-method-market-analysis/SKILL.md
Conduct deep, structured market analysis using multiple methodologies (PESTLE, Foresight, Delphi, Wardley Maps). Use this skill whenever the user asks for market analysis, competitive intelligence, industry research, market trends, weekly intelligence reports, or strategic market insights. Also trigger when the user mentions PESTLE, Wardley Maps, Foresight signals, or wants to understand a market, niche, or industry in depth — even if they don't explicitly ask for "market analysis".
npx skillsauth add renatocaliari/agent-sync-public-skills cali-multi-method-market-analysisInstall 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.
A skill for producing rigorous, structured market analysis using multiple complementary methodologies. Two prompt variants are available depending on the user's goal.
IMPORTANT: When the user needs to choose between predefined options, ALWAYS use the question tool (if available) with enumerated format:
label and descriptionWhen question tool is not available, use enumerated text in chat (A/B/C/D or 1/2/3).
Use this when the user wants a comprehensive, methodologically rigorous study of a topic across time.
Study Topic: [FILL IN]
Focus on: [Enter 'Global' or the specific country/region name here]
Goal: Conduct a DEEP market analysis of the study topic.
Cover [Focus on] insights in English.
Methodologies: Use the following methodologies with in-depth details:
- PESTLE
- Foresight (Weak and Strong Signals)
- Delphi
- Wardley Maps
Organize the analysis into:
- Recent Past (1 year ago)
- Current Trends (Today to 1 year)
- Future Predictions (Next 5 years)
Ask the user for their inputs (if not already provided):
question tool to confirm:
Apply all four methodologies to each time horizon.
Synthesize findings into a coherent narrative, not just isolated frameworks.
Use this for a structured 7-day competitive intelligence report. Best suited for users who want to track a specific niche or business context on a recurring basis.
question tool to gather:
{my business}: The user's company or product{my job to be done or niche}: The market/niche to analyze**Context:**
{my business}: [fill it here]
{my job to be done or niche}: [fill it here]
You are an industry analyst specializing in {my job to be done or niche}.
### 🎯 Task
For the past 7 days, collect and analyze all relevant:
- 📰 Announcements, product releases, and feature updates
- 🤝 Partnerships, M&A, funding rounds
- ⚖️ Regulatory or policy changes
- 🔍 Strategic signals and foresight indicators
### 🌐 Data Sources
Search across:
- Company blogs, press releases, GitHub changelogs
- News sites relevant to the niche
- LinkedIn, X (Twitter), Reddit (practitioner communities)
- Traditional forums where relevant
### 🧮 Analytical Lenses
Apply multi-method market analysis:
- 🎯 Identify indirect and hidden competitors (tools, services, AI agents, startups addressing similar jobs)
- 🏛 PESTLE: Political, Economic, Social, Technological, Legal, Environmental
- 🔮 Foresight: Weak & strong signals + strategic implications
- 🗣 Delphi Method: Expert consensus from practitioner sentiment
- 🗺 Wardley Mapping (ASCII): Visualize capability evolution
### 🧾 OUTPUT FORMAT: EXECUTIVE CANVAS (Markdown)
#### 📊 Weekly Intelligence Canvas
**Period:** Last 7 Days
**Focus:** {my job to be done or niche}
---
#### 🎯 1. Executive Summary (3 bullets max)
> • One-sentence market shift
> • Top 2 leaders and their moves
> • Emerging threat or disruption
---
#### 🚀 2. Top Announcements (Grid)
| 🏢 Company | 🧩 Type | 📰 Summary | 🔗 Link |
|------------|---------|------------|---------|
---
#### 💡 3. Key Insights (Mermaid Flow + Bullets)
```mermaid
graph TD
A[Core Trend] --> B[Impact]
C[Signal] --> D[Outcome]
style A fill:#e3f2fd,stroke:#1976d2
style C fill:#fff3e0,stroke:#f9a825
| Platform | Move | Impact | Position | |----------|------|--------|----------|
| 🕵️ Entity | Category | Job Solved | Displacement Risk | 🔗 Main Link | 📚 Sources | |-----------|----------|-----------|-------------------|--------------|------------|
1 concise paragraph on how these shift buyer perception, pricing, or adoption.
| 🔎 Signal | Strength | Implication | |-----------|----------|-------------|
Users
↓
[Custom]
↓
[Product]
↓
[Commodity]
↓
[Genesis]
Brief Explanation (2 bullets max):
### Style Rules for the Canvas
- Use emojis consistently (🏢 🚀 💡 🧭 🔮 🗺 ✅ 📎)
- Keep all text scannable (< 2 pages)
- Use **bold** for emphasis, not italics
- Include a Mermaid flow in section 3 and an ASCII Wardley Map in section 6
- Cite sources with real clickable links — no inline citations
---
## Methodology Reference
| Methodology | Purpose |
|-------------|---------|
| **PESTLE** | Macro-environment scan across 6 dimensions |
| **Foresight** | Identify weak and strong signals for future shifts |
| **Delphi** | Synthesize expert/practitioner consensus |
| **Wardley Maps** | Visualize the evolution of capabilities in a value chain |
---
## Output Format
- Variant 1: Structured markdown report organized by time horizon and methodology
- Variant 2: Executive Canvas in markdown, ready for Notion, Miro, or Canva
tools
Auto-initialize structured documentation for any project using lat.md (knowledge graph of markdown files with [[wiki links]], // @lat: code refs, and semantic search). Detects cali-product-workflow artifacts (spec-product.md, spec-tech.md, critiques) and uses them as seed material. Falls back to extracting business rules, architecture, and design decisions directly from the codebase. Use when a project lacks structured documentation or when lat.md/ is missing. After seeding, lat.md extension hooks keep documentation alive automatically.
testing
[Cali] Server security audit and hardening for private servers behind Tailscale. Use when: auditing server security, hardening SSH/firewall/Docker, checking for vulnerabilities, setting up fail2ban, reviewing port exposure, or responding to security alerts. Covers 6 layers: CloudFlare, UFW, Tailscale, SSH, Docker, Application. Triggers: "server security", "security audit", "harden server", "SSH hardening", "firewall rules", "UFW config", "fail2ban", "port security", "Docker security", "vulnerability check", "security review".
tools
Run supply chain security scans before installing packages or before releases. Triggers when: user installs a package (npm, pip, go get, brew), user asks to 'scan dependencies', 'check vulnerabilities', 'supply chain', 'security audit', 'run trivy', 'run socket', or before any release/deployment. Also triggers on mentions of: socket.dev, trivy, OSV-scanner, dotenvx, CVE, dependency audit. Covers all four tools with concrete commands.
tools
Create GitHub releases following project conventions. Triggers when: user says 'release', 'create release', 'push release', 'deploy to main', 'merge to main', user merges a PR to main, or when git push to main is detected. Also triggers on mentions of: gh release, semver, version bump, changelog, release-please. Covers: config-driven (read .release.yml and execute) and fallback (gh CLI) release flows, versioning rules, tag management, and the mandatory release-on-merge convention.