Structured analysis for any input. Data, code, text, decisions, visuals. Prioritize, question, conclude.
Scanned 5/27/2026
Install via CLI
openskills install clawic/skills---
name: "Analyze"
description: "Structured analysis for any input. Data, code, text, decisions, visuals. Prioritize, question, conclude."
---
## Pattern
```
Purpose → Structure → Analyze → Prioritize → Conclude
```
Before analyzing: State what decision this serves. Pick a framework. Note first impression to challenge later.
## Before
- **Purpose in one line**: "This analysis helps decide ___"
- **What's missing**: 3+ unknowns that would change conclusions
- **First impression**: Write it — then seek counter-evidence
## During
- **Prioritize always**: 🔴 Critical (1-2 max) · 🟡 Important (2-3) · ⚪ Minor
- **Mark sources**: Every claim gets `[from input]` or `[inferred]`
- **Seek disconfirmation**: Dedicate space to "why I might be wrong"
- **Distinguish**: Facts vs opinions. Correlation vs causation.
## After
- **One-line summary**: Force analysis into one sentence
- **So what?**: End with action, not summary
- **Obviousness test**: Would someone say this without reading? → Deeper
## Traps
- **Superficial**: Paraphrasing ≠ analysis
- **Equal weight**: Everything yellow = nothing prioritized
- **Confirmation bias**: First impression became conclusion
- **Missing denominator**: "500 cancellations" of 600 or 50,000?
- **Invented data**: Stats without source = hallucination
## By Domain
| Domain | Focus | Watch |
|--------|-------|-------|
| Data | Grain, missing, outliers | Centinels, mixed types |
| Code | Production breaks, dead code | Style ≠ bugs |
| Text | Thesis, evidence strength | Unsourced claims |
| Decisions | Unlisted options, reversibility | Status quo bias |
| Visual | Dominance, consistency | Platform conventions |
## Frameworks
Pick one before starting:
- **MECE**: Mutually exclusive, collectively exhaustive
- **Pros/Cons+**: Add reversibility + cost of inaction
- **Pre-mortem**: Assume failure — why?
- **Steel man**: Best opposing argument
## Output
```
🎯 PURPOSE: Decide [X]
🔴 CRITICAL: [Finding + source]
🟡 IMPORTANT: [Findings]
⚠️ COUNTER: [Contradictions]
➡️ ACTION: [Recommendation]
```
---
*Channels, not teaches. Ensures prioritization, questioning, and conclusions.*
No comments yet. Be the first to comment!
End-to-end marketing campaign planning and execution. Covers audience research, positioning, campaign angle definition, landing page copy, email sequences, social posts, ad copy, short-form video scripts, and content calendars. Use as the orchestration layer for multi-channel product launches.
Orchestrate multi-phase deep research with web search, memory retrieval, pattern matching, and synthesis into structured findings
Persistent memory systems for LLM conversations including short-term, long-term, and entity-based memory Use when: conversation memory, remember, memory persistence, long-term memory, chat history.
CodeTour `.tour`ファイルを作成 — ペルソナターゲット、ステップバイステップウォークスルー(実際のファイルとラインアンカー付き)。オンボーディングツアー、アーキテクチャウォークスルー、PRツアー、RCAツアー、構造化「これがどのように機能するかを説明」リクエストに使用。
showコマンド、コンフィグ階層、ワイルドカードマスク、ACL配置、インターフェースハイジーン、安全な変更ウィンドウ検証のためのCisco IOSおよびIOS-XEレビューパターン。