ysskrishna/ai-agent-skills / skills/analytical-thinking
analytical-thinking
VerifiedUse for analytical thinking, or when a question needs breaking down and evidence: "why did metric X drop?", "what drives this?", "break this down", "what data do we need?". Builds a tree, hypotheses and evidence, ends with an answer and key uncertainty. Skip for quick verdicts.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.5 KB |
| references/example.md | markdown | 1.6 KB |
references/example.md
View on GitHub# Example: Analytical Thinking (light path)
Illustrative case. All details are invented.
**User:** "Weekly signups from our pricing page dropped last month. What should we look at?"
**Analytical question:** which factor best explains the drop in weekly signups from the pricing page last month?
**Pass:** Frame, Decompose, Hypotheses, Evidence, Synthesis.
**Frame**
- Type: explain. Unit: weekly signups attributed to the pricing page. Baseline: the previous four weeks.
**Decompose**
- Signups = visitors x conversion rate.
- Visitors: traffic by channel (search, paid, referral); page load issues.
- Conversion: page changes, price changes, form errors, tracking changes.
**Hypotheses**
- H1: traffic fell (one channel). Expect visitors down with stable conversion. Falsified if visitors are flat.
- H2: conversion fell after a page or price change. Expect a step change on a known date. Falsified if conversion is flat.
- H3: tracking broke. Expect a drop in recorded events but not in billing signups. Falsified if billing signups fell too.
**Evidence**
- Not yet gathered. Thought experiment (no data): ask the user for visitors, conversion and billing signups by week for 8 weeks, and the deploy log.
- Reading guide: H1 shows in visitors by channel. H2 lines up with a deploy or price date. H3 shows when billing and analytics disagree.
**Synthesis**
1. Answer: not determinable without data; the three checks above separate the causes in under an hour.
2. Key uncertainty: whether billing signups also dropped (separates a real drop from a tracking fault).
3. Next step: pull 8 weeks of visitors, conversion and billing signups; compare against the deploy log.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |