Index of every page on this site: llms.txt
All skills
anthropics avatar

/analyze

@b4c9a4e
Run it yourself

Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.

Use this Skill: https://skilld.dev/gh/anthropics/knowledge-work-plugins/analyze

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈59 tokens for metadata: the name and description. ≈1k when used: this file.

Description uses 2.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈236 characters, or 2.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

/analyze - Answer Data Questions

If you see unfamiliar placeholders or need to check which tools are connected, see 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:

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

If no data warehouse is connected:

  1. 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
  2. If writing queries for manual execution, use the sql-queries skill for dialect-specific best practices
  3. 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

4. Validate Before Presenting

Before sharing results, run through validation checks:

  • Row count sanity: Does the number of records make sense?
  • Null check: Are there unexpected nulls that could skew results?
  • Magnitude check: Are the numbers in a reasonable range?
  • Trend continuity: Do time series have unexpected gaps?
  • Aggregation logic: Do subtotals sum to totals correctly?

If any check raises concerns, investigate and note caveats.

5. Present Findings

For quick answers:

  • State the answer directly with relevant context
  • Include the query used (collapsed or in a code block) for reproducibility

For full analyses:

  • Lead with the key finding or insight
  • Support with data tables and/or visualizations
  • Note methodology and any caveats
  • Suggest follow-up questions

For formal reports:

  • Executive summary with key takeaways
  • Methodology section explaining approach and data sources
  • Detailed findings with supporting evidence
  • Caveats, limitations, and data quality notes
  • Recommendations and suggested next steps

6. Visualize Where Helpful

When a chart would communicate results more effectively than a table:

  • Use the data-visualization skill to select the right chart type
  • Generate a Python visualization or build it into an HTML dashboard
  • Follow visualization best practices for clarity and accuracy

Examples

Quick answer:

/analyze How many new users signed up in December?

Full analysis:

/analyze What's causing the increase in support ticket volume over the past 3 months? Break down by category and priority.

Formal report:

/analyze Prepare a data quality assessment of our customer table -- completeness, consistency, and any issues we should address.

Tips

  • Be specific about time ranges, segments, or metrics when possible
  • If you know the table names, mention them to speed up the process
  • For complex questions, Claude may break them into multiple queries
  • Results are always validated before presentation -- if something looks off, Claude will flag it

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill facilitates data analysis by exploring schemas, executing SQL queries, and generating visualizations. It follows a structured workflow for data validation and reporting. While it processes external data and utilizes dynamic code generation for visualizations, these are standard practices for its intended purpose.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    1 file scanned · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at b4c9a4e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 8 months ago
argument-hint
<question>

README badge

README badge for anthropics/knowledge-work-plugins/analyze