Skip to content
Back to skills

Analyze

ASecurity

Structured analysis for any input. Data, code, text, decisions, visuals. Prioritize, question, conclude.

  • 17 stars
  • 0 votes
  • 1 copy
  • 4 views
  • Added May 27, 2026
data-ai

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned May 27, 2026

npx -y skills add clawic/skills --skill analyze --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Analyze?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Analyze
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/clawic-analyze/badge)](https://www.skillsdirectory.com/skills/clawic-analyze)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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.*

Files in this skill

  • SKILL.md2.1 KB
  • _meta.json166 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.