A workflow for answering data questions, from a single metric to a full investigation or stakeholder report. It can use natural-language questions and data from a connected warehouse or other provided sources.

Use it to look up metrics, investigate trends or changes, compare groups over time, or prepare a formal data report.

It gives a structured way to move from a business question to the relevant data, calculations, findings, and presentation format.

analyze — Skill for Claude Code by nota-america

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add nota-america/forgecat-agent-profiles --skill analyze

Clone the repo

git clone --depth 1 https://github.com/nota-america/forgecat-agent-profiles

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/analyze/github.svg)](https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/analyze)

Your own site

<a href="https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/analyze"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/analyze/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/analyze"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/analyze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 978 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 98% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00045	$0.00978
Opus 5	$0.00023	$0.00489
Sonnet 5	$0.00009	$0.00196
Haiku 4.5	$0.00005	$0.00098

Measured 8d ago against content hash 2d9d1731a199, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

analyze scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

98% identical to analyze — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

profiles/anthropics/knowledge-work-plugins/anthropics_knowledge-work-plugins_data/for-claude/.claude/skills/analyze/SKILL.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/analyze - Answer Data Questions

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md (.forgecat/profiles/@forgecat/anthropics_knowledge-work-plugins_data/CONNECTORS.md).

Answer a data question, from a quick lookup to a full analysis to a formal report.

Usage

/analyze <natural language question>

Workflow

1. Understand the Question

Parse the user's question and determine:

Complexity level:
- Quick answer: Single metric, simple filter, factual lookup (e.g., "How many users signed up last week?")
- Full analysis: Multi-dimensional exploration, trend analysis, comparison (e.g., "What's driving the drop in conversion rate?")
- Formal report: Comprehensive investigation with methodology, caveats, and recommendations (e.g., "Prepare a quarterly business review of our subscription metrics")
Data requirements: Which tables, metrics, dimensions, and time ranges are needed
Output format: Number, table, chart, narrative, or combination

2. Gather Data

If a data warehouse MCP server is connected:

Explore the schema to find relevant tables and columns
Write SQL query(ies) to extract the needed data
Execute the query and retrieve results
If the query fails, debug and retry (check column names, table references, syntax for the specific dialect)
If results look unexpected, run sanity checks before proceeding

If no data warehouse is connected:

Ask the user to provide data in one of these ways:
- Paste query results directly
- Upload a CSV or Excel file
- Describe the schema so you can write queries for them to run
If writing queries for manual execution, use the sql-queries skill for dialect-specific best practices
Once data is provided, proceed with analysis

3. Analyze

Calculate relevant metrics, aggregations, and comparisons
Identify patterns, trends, outliers, and anomalies
Compare across dimensions (time periods, segments, categories)
For complex analyses, break the problem into sub-questions and address each

Read the full file on GitHub · 123 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

8d ago First seen · 123 lines · 45 tokens per session scan A 2d9d1731a199

Subscribe to this mod's changes

analyze is a skill published in the GitHub repository nota-america/forgecat-agent-profiles (66 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session and 978 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to analyze, differing in 9 lines, and is treated as a copy.

Analytics and metrics Claude Code agent-md-file agent-profiles ai-agent ai-agent-marketplace ai-agents

aoa-agents-skills

Form, transfer, continue, or receive an independent AoA responsibility with a role-bearing actor. Use when an obligation needs its own holder, mandate, or continuity across incarnations. Ordinary tasks and native Codex helpers do not need this skill.

8Dionysus/aoa-agents · 56 tokens

aoa-session-progression-lift

Turn closed, reviewed session evidence into a bounded multi-axis progression candidate with baseline and attribution limits for aoa-agents review. Do not use on live impressions, without a baseline, to assign one universal score, mutate a role, grant authority, or set routing policy.

8Dionysus/aoa-agents · 62 tokens

aoa-summon

Decide or execute a complete summon-request-v4 for an independent external AoA actor and return a validated summon-result-v4. Use as the aoa-agents-skills execution leaf or to inspect an explicit legacy summon packet. Ordinary native Codex helpers do not use this leaf.

8Dionysus/aoa-agents · 63 tokens

analyze