Consulting Analysis

Indexed Reference Map

• @[SKILL.md#L1-L84] Frontmatter, scope, KB notes, trigger rules, SOP, error handling, output contract.
• @[references/INDEX.md#L1-L11] Reading order and document map.
• @[references/QUICK_REFERENCE.md#L1-L20] Use-vs-don't-use map and phase selection.
• @[references/CORE_API.md#L1-L49] Two-phase contract, source priority, evidence rules, and report constraints.
• @[references/PATTERNS.md#L1-L25] Framework design patterns, data handoff discipline, and narrative rules.
• @[references/EXAMPLES.md#L1-L16] Example asks and expected behavior.
• @[references/AI_WORKFLOW.md#L1-L14] Bounded orchestration flow.

Scope

• In-scope:
  • Phase 1: define an analysis framework for market, brand, industry, consumer, competitive, financial, or diligence-style work.
  • Phase 2: synthesize already-collected evidence into a consulting-grade Markdown report.
  • Coordinating downstream research/data tasks by specifying what evidence is required.
• Out-of-scope:
  • Acting as a generic always-on research skill.
  • Collecting evidence itself when a more specific skill should do it (deep-research, github-deep-research, data-analysis, context7-clean, firecrawl).
  • Fabricating numbers, charts, or citations when evidence is missing.

KB Mode Notes

• Reading order:
  1. references/INDEX.md
  2. references/QUICK_REFERENCE.md
  3. references/CORE_API.md
  4. references/PATTERNS.md
  5. references/EXAMPLES.md
  6. references/AI_WORKFLOW.md
• Coverage Matrix:
  • trigger boundary + phase choice -> QUICK_REFERENCE.md
  • phase contract + evidence/report rules -> CORE_API.md
  • framework/reporting methodology -> PATTERNS.md
  • representative tasks -> EXAMPLES.md
  • bounded orchestration order -> AI_WORKFLOW.md
• Portability note:
  • Local skill boundaries and tool handoff rules here are source-of-truth for OpenClaw-Module Android; re-check before porting to another orchestration environment.

Trigger Rules

• Positive:
  • User explicitly wants a consulting-grade report, analysis framework, diligence memo, market study, competitive landscape, consumer insights report, or structured executive narrative.
  • The task needs a deliberate two-phase workflow: framework first, evidence collection second, synthesis last.
• Negative:
  • The user only wants raw research/search results.
  • The user only wants tabular analysis or GitHub investigation without consulting-style synthesis.
  • The request is ordinary planning/brainstorming rather than professional analytical reporting.
• Escalation:
  • If evidence is not yet collected, stay in Phase 1 and hand off concrete data tasks.
  • If evidence is partial, report gaps explicitly instead of fabricating Phase 2 polish.

SOP

1. Resolve whether the task is Phase 1 (framework) or Phase 2 (final report).
2. Identify domain, scope, key questions, and decision audience.
3. For Phase 1, produce chapter skeleton, hypotheses, data requirements, and visualization plan.
4. Delegate evidence collection to the most specific downstream skill(s).
5. For Phase 2, validate evidence completeness before writing.
6. Write the report in consulting voice, tied only to provided evidence.
7. Flag missing P0 evidence, assumptions, and limits explicitly.

Error Handling

• Missing evidence:
  • stay in framework mode or produce a bounded partial report with explicit gaps.
• Weak scope definition:
  • narrow the business question, geography, period, or segment before designing a large framework.
• Overlap ambiguity:
  • hand off evidence collection to the more specific skill instead of bloating this one.
• Unsupported chart/citation expectation:
  • state the limitation and provide a textual alternative rather than inventing artifacts.

Output Contract

• Deliverables:
  • Phase 1: Markdown analysis framework.
  • Phase 2: Markdown final report.
• Validation:
  • no invented data
  • every major claim traceable to provided evidence
  • report structure and phase behavior stay consistent with this skill
• Compliance Verdict:
  • PASS when phase selection, evidence handling, and reporting discipline are correct.