Skip to main content
skill CX Codex

analysis-authoring — Claude Code skill: what it does, how to install

analysis-authoring provides authoring standards for exploratory notebooks and dashboards, covering section flow, plot selection, and validation budgets.

CC-BY-4.0 ★ 1,627 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add microsoft/hve-core --skill analysis-authoring -a claude-code
Open on GitHub

What analysis-authoring does

This skill supplies editorial guidelines for data analysis deliverables. Instead of generic charting, it forces the assistant to select plots based on explicit analytical questions, truncate high-cardinality values, and attach written takeaways directly next to every figure. Visual channels must use palettes accessible to colorblind readers.

For analytical dashboards, the guidance checks caching separation between raw data and global state, multi-page interactions, and responsiveness budgets. The instructions are backed by two reference documents: eda-notebook-authoring.md and dashboard-authoring-and-validation.md.

Responsibilities remain strictly bounded: semantic profiling belongs to data-catalog, while file formats stay with dataops. If an analysis goal is missing, the skill halts execution immediately, because plotting choices cannot be made without a defined research question.

What it helps with

  • structure exploratory data analysis notebooks logically
  • pick charts matched to data scale and analytical targets
  • audit analytical dashboards against responsiveness budgets and cache rules
  • document data limitations alongside visual charts

Example prompts for the agent

  • Review this exploratory notebook against authoring conventions and check section order
  • Recommend visualization types for high-cardinality metrics following the skill guidelines
  • Validate this dashboard deliverable for state handling and responsiveness budgets

How to install analysis-authoring

1Skills CLI (Vercel)

npx skills add microsoft/hve-core --skill analysis-authoring -a claude-code

2Manually: put the files in place

~/.claude/skills/analysis-authoring/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/analysis-authoring/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about analysis-authoring

How to install analysis-authoring in Claude Code?

Run npx skills add microsoft/hve-core --skill analysis-authoring -a claude-code. The skill file will be placed in ~/.claude/skills/analysis-authoring/SKILL.md.

What does analysis-authoring do?

It guides Claude Code through composing and reviewing EDA notebooks and analytical dashboards, establishing layout sequences and chart criteria.

When does the skill trigger a stop rule?

It halts when the core analytical question is omitted, or when column definitions and business grain require delegation to data-catalog.

Source text

SKILL.md · CC-BY-4.0
---
name: analysis-authoring
description: "Authoring conventions for exploratory data analysis notebooks and analytical dashboards, covering section sequence, visualization selection, scale thresholds, caching and state, and dashboard validation budgets. Use when composing or reviewing an EDA notebook, an analytical dashboard, or a dashboard test pass."
license: CC-BY-4.0
user-invocable: false
metadata:
  authors: "Microsoft (planning synthesis)"
  spec_version: "1.0"
  last_updated: "2026-08-05"
---

# Analysis Authoring Conventions

## Goal

Produce exploratory notebooks and analytical dashboards whose structure, visualization choices, and scale handling are deliberate rather than incidental. This skill supplies the editorial judgment that generic file, notebook, terminal, and browser tooling does not carry.

## Flow

1. Confirm the analysis question, the datasets in scope, and the deliverable shape: notebook, dashboard, or both.
2. Read the available profile and objectives artifacts rather than re-deriving column semantics. `data-catalog` owns the profile contract and semantic roles.
3. Select the deliverable's section sequence from the matching reference, including only the conditional sections the data supports.
4. Choose each visualization from its analytical goal, applying the scale thresholds rather than plotting whole datasets by default.
5. Record interpretation next to each figure so a reader learns what the figure answers, not only what it shows.
6. Validate the deliverable against its completeness expectations, and for dashboards apply the responsiveness budgets as project-adjustable defaults.

## Inputs

* The analysis question and intended audience
* Dataset locations and, when available, an existing data profile and declared objectives
* The deliverable shape and its destination
* Any project-specific performance budget that overrides the defaults here

## Success criteria

* The deliverable follows the section sequence for its shape, and conditional sections appear only when the data supports them.
* Every figure is preceded by the question it answers and is followed by an interpretation placeholder or an actual reading.
* Visualization selection matches the analytical goal, and dense or high-cardinality data is sampled, binned, or truncated deliberately.
* Every meaningful distinction is encoded in a channel besides colour, and categorical and continuous scales use colourblind-safe palettes.
* Notebook code stays modular, with repeated transformation logic extracted rather than duplicated across cells.
* Dashboard caching distinguishes serializable data from global resources, and cross-page interaction state is explicit.
* Dashboard validation reports functional, data, and responsiveness findings against stated budgets.
* Uncertainty, data limitations, and open questions are written down rather than implied.

## Constraints

* Describe judgment, not tool mechanics. Notebook creation, cell execution, output inspection, browser navigation, and screenshots are native tool capabilities and are not narrated here.
* Reference profile and objectives artifacts instead of copying their contents into the deliverable.
* Keep persistence format and dataset versioning with `dataops`, which owns pipeline invariants and storage conventions.
* Keep entity semantics, relationships, and semantic roles with `data-catalog`.
* Treat the performance budgets as defaults. A project-stated budget supersedes them.
* Do not embed environment-specific absolute paths in a deliverable.

## Ownership boundaries

| Concern                                                                   | Owner                |
|---------------------------------------------------------------------------|----------------------|
| Column semantics, semantic roles, profile and objectives contracts        | `data-catalog`       |
| Persistence format, dataset versioning, pipeline and validation placement | `dataops`            |
| Accessibility conformance criteria and assistive-technology review        | `accessibility`      |
| Evaluation dataset design for AI systems                                  | `evaluation-design`  |
| Trained-model evaluation, tracking, and readiness                         | `ml-experimentation` |

## Stop rules

* Stop and ask when the analysis question is unstated, because section selection and visualization choice both depend on it.
* Stop and record a limitation rather than inventing an explanation for a pattern the data does not support.
* Stop and route to `data-catalog` when column meaning, grain, or relationships are ambiguous.
* Stop and route accessibility conformance work to the `accessibility` skill rather than restating criteria here.

## Package resources

| Resource                                                                                  | Use                                                                   |
|-------------------------------------------------------------------------------------------|-----------------------------------------------------------------------|
| [eda-notebook-authoring.md](references/eda-notebook-authoring.md)                         | Read when composing or reviewing an exploratory notebook              |
| [dashboard-authoring-and-validation.md](references/dashboard-authoring-and-validation.md) | Read when composing, reviewing, or validating an analytical dashboard |

## Attribution

This package is repository-original content licensed CC BY 4.0. The section sequences, selection thresholds, completeness expectations, and default budgets are HVE Core conventions rather than reproductions of an upstream specification.

© microsoft · CC-BY-4.0 · microsoft/hve-core

Similar skills

All skills for Data and databases →

From the same set148

The whole set →
RPI Reviewer RPI Reviewer reviews an assigned slice of RPI evidence and returns candidate findings with locations. Useful when a large comparison needs to be split up. CX Codex +1 ★ 1,627repo stars diff-computation The diff-computation rule sets the order for code review: build the diff before reading files. Findings stay on changed lines, and large patches are read in chunks. CX Codex +1 ★ 1,627repo stars rai-standards rai-standards is a Claude Code skill that organizes responsible AI references: NIST AI RMF 1.0, the AI STRIDE overlay, and EU AI Act requirements across development stages. CX Codex +1 ★ 1,627repo stars data-catalog Build a Markdown data catalog with declared entities and relationships. Use the skill to inventory engagement data or prepare a catalog for ERD rendering. CX Codex +1 ★ 1,627repo stars Supply Chain Skill Assessor Supply Chain Skill Assessor runs a supply-chain review against the supply-chain-security skill and returns a findings table: what passes, what is partial, where the gap sits. Handy before a release or a CI review. CX Codex +1 ★ 1,627repo stars privacy-standards privacy-standards is a Claude Code skill that provides privacy engineering references for data-flow analysis, DPIA thresholds, and open compliance standards. CX Codex +1 ★ 1,627repo stars copilot-tracking This rule organizes working files for RPI, HVE Builder, and related workflows under .copilot-tracking/. It sets paths and formatting conventions for research, plans, changes, and reviews. CX Codex +1 ★ 1,627repo stars demo-video Assembles demo videos from ordered frames or clips, WAV narration, and transitions via FFmpeg. Built for first-pass prototype walkthroughs and tutorials. CX Codex +1 ★ 1,627repo stars

Project sponsors

Companies that keep this analytics open