This skill provides a workflow for transforming data into structured narrative text visualizations using T8 Syntax - a declarative Markdown-like language for creating data narratives with semantic entity annotations.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionnarrative-text-visualizationExecute the skills CLI command in your project's root directory to begin installation:
Fetches narrative-text-visualization from antvis/chart-visualization-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate narrative-text-visualization. Access via /narrative-text-visualization in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
50
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
50
stars
This skill provides a workflow for transforming data into structured narrative text visualizations using T8 Syntax - a declarative Markdown-like language for creating data narratives with semantic entity annotations.
T8 is a text visualization solution under the AntV technology stack designed specifically for insight-based narrative text display. Instead of manually constructing DOM elements, you write simple, human-readable syntax that describes your data narrative.
Key Features:
To generate narrative text visualizations, follow these steps:
Analyze the user's request to determine:
Create narrative text using T8 Syntax following the specification below. The content must include:
Create HTML, React, or Vue code to render the T8 content based on user's preferred framework.
Ensure:
T8 Syntax is a Markdown-like language for creating narrative text with semantic entity annotations. It makes data analysis reports more expressive and visually appealing.
Use standard Markdown heading syntax:
# Level 1 Heading (Main Title)
## Level 2 Heading (Section)
### Level 3 Heading (Subsection)
#### Level 4 Heading
##### Level 5 Heading
###### Level 6 Heading
Rules:
# symbolsRegular text paragraphs are separated by blank lines:
This is the first paragraph with some content.
This is the second paragraph, separated by a blank line.
Rules:
T8 Syntax supports both unordered and ordered lists.
Unordered Lists:
- First item
- Second item
- Third item
Ordered Lists:
1. First step
2. Second step
3. Third step
Rules:
-, *) or numberT8 Syntax supports inline text formatting using Markdown syntax:
Bold Text: This is **bold text** that stands out.
Italic Text: This is *italic text* for emphasis.
Underline Text: This is __underlined text__ for importance.
Links: Visit [our website](https://example.com) for more information.
Rules:
[text](URL) syntax where URL starts with http://, https://, or /The core feature of T8 Syntax is entity annotation - marking specific data points with semantic meaning and metadata.
[displayText](entityType)
displayText: The text shown to readersentityType: The semantic type of this entityExample:
The [sales revenue](metric_name) reached [¥1.5 million](metric_value) this quarter.
[displayText](entityType, key1=value1, key2=value2, key3="string value")
Metadata Rules:
origin=1500000, active=true)unit="元", region="Asia")Example:
Revenue grew by [15.3%](ratio_value, origin=0.153, assessment="positive") compared to last year.
Use these entity types to annotate different kinds of data:
| Entity Type | Description | When to Use | Examples |
|---|---|---|---|
metric_name |
Name of a metric or KPI | When mentioning what you're measuring | "revenue", "user count", "market share" |
metric_value |
Primary metric value | The main number/value being reported | "¥1.5 million", "50,000 users", "250 units" |
other_metric_value |
Secondary or supporting metric value | Additional metrics that provide context | "average order value: $120" |
delta_value |
Absolute change/difference | When showing numeric change between periods | "+1,200 units", "-$50K", "increased by 500" |
ratio_value |
Percentage change/rate | When showing percentage change | "+15.3%", "-5.2%", "grew 23%" |
contribute_ratio |
Contribution percentage | When showing what % something contributes | "accounts for 45%", "represents 30% of total" |
trend_desc |
Trend description | Describing direction/pattern of change | "steadily rising", "declining trend", "stable" |
dim_value |
Dimensional value/category | Geographic, categorical, or segmentation data | "North America", "Enterprise segment", "Q3" |
time_desc |
Time period or timestamp | When specifying when something occurred | "Q3 2024", "January-March", "fiscal year 2023" |
proportion |
Proportion or ratio | When expressing parts of a whole | "3 out of 5", "60% of customers" |
rank |
Ranking or position | When indicating order or position in a list | "ranked 1st", "top 3", "5th place" |
difference |
Comparative difference | When highlighting difference between two items | "difference of $50K", "gap of 200 units" |
anomaly |
Unusual or unexpected value | When pointing out outliers or anomalies | "unusual spike", "unexpected drop" |
association |
Relationship or correlation | When describing connections between metrics | "strongly correlated", "linked to", "related" |
distribution |
Data distribution pattern | When describing how data is spread | "evenly distributed", "concentrated in", "spread across" |
seasonality |
Seasonal pattern or trend | When describing recurring seasonal patterns | "seasonal peak", "holiday period", "Q4 surge" |
Add these optional fields to provide richer data context:
origin (number)The raw numerical value behind the displayed text.
Examples:
[¥1.5M](metric_value, origin=1500000)[23.7%](ratio_value, origin=0.237)[5.2K users](metric_value, origin=5200)[3 out of 4](proportion, origin=0.75)Why use it: Enables data visualization, sorting, and calculations
assessment (string)Evaluates whether a change is positive, negative, or neutral.
Valid values: "positive", "negative", "equal", "neutral"
Examples:
[increased 15%](ratio_value, assessment="positive")[dropped 8%](ratio_value, assessment="negative")[remained flat](trend_desc, assessment="equal")Why use it: Enables visual indicators (colors, icons) for good/bad trends
unit (string)The unit of measurement for the value.
Examples:
[¥1,500,000](metric_value, unit="元", origin=1500000)[150](metric_value, unit="units")detail (any)Additional context or breakdown data for chart rendering. Required for certain entity types.
Required for these entity types:
rank: Array of numbers representing ranking data
[top performer](rank, detail=[5, 8, 12, 15, 20])difference: Array of numbers showing comparative values
[gap narrowing](difference, detail=[100, 80, 60, 40])anomaly: Array of numbers highlighting outliers
[unusual spike](anomaly, detail=[10, 12, 11, 45, 13])association: Array of {x, y} objects for correlation data
[strong correlation](association, detail=[{"x":1,"y":2},{"x":2,"y":4},{"x":3,"y":6}])distribution: Array of numbers showing data spread
[uneven distribution](distribution, detail=[5, 15, 45, 25, 10])seasonality: Object with data array and optional range
[Q4 peak](seasonality, detail={"data":[10,12,15,30],"range":[0,40]})Optional for other types:
[steady growth](trend_desc, detail=[100, 120, 145, 180, 210])Critical: All data must be from publicly authentic sources:
# 2024 Smartphone Market Analysis
## Market Overview
Global [smartphone shipments](metric_name) reached [1.2 billion units](metric_value, origin=1200000000) in [2024](time_desc), showing a [modest decline of 2.1%](ratio_value, origin=-0.021, assessment="negative") year-over-year.
The **premium segment** (devices over $800) showed *remarkable* [resilience](trend_desc, assessment="positive"), growing by [5.8%](ratio_value, origin=0.058, assessment="positive"). [Average selling price](other_metric_value) was [$420](metric_value, origin=420, unit="USD").
## Key Findings
1. [Asia-Pacific](dim_value) remains the __largest market__
2. [Premium devices](dim_value) showed **strong growth**
3. Budget segment faced *headwinds*
## Regional Breakdown
### Asia-Pacific
[Asia-Pacific](dim_value) remains the largest market with [680 million units](metric_value, origin=680000000) shipped, though this represents a [decline of 180 million units](delta_value, origin=-180000000, assessment="negative") from the previous year.
Key markets:
- [China](dim_value): [320M units](metric_value, origin=320000000) - down [8.5%](ratio_value, origin=-0.085, assessment="negative"), [ranked 1st](rank, detail=[320, 180, 90, 65, 45]) globally, accounting for [47%](contribute_ratio, origin=0.47, assessment="positive") of regional sales
- [India](dim_value): [180M units](metric_value, origin=180000000) - up [12.3%](ratio_value, origin=0.123, assessment="positive"), [ranked 2nd](rank, detail=[320, 180, 90, 65, 45])
- [Southeast Asia](dim_value): [180M units](metric_value, origin=180000000) - [stable](trend_desc, assessment="equal")
For detailed methodology, visit [our research page](https://example.com/methodology).
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>T8 Narrative Text</title>
</head>
<body>
<div id="container"></div>
<!-- Import T8 from unpkg CDN -->
<script src="https://unpkg.com/@antv/t8/dist/t8.min.js"></script>
<script>
// T8 is available as a global variable
const { Text } = window.T8;
// Initialize T8 instance
const text = new Text(document.getElementById('container'));
// Render narrative text using T8 Syntax
const narrativeText = `
# Sales Report
This quarter, [bookings](metric_name) are higher than usual. They are [¥348k](metric_value, origin=348.12).
[Bookings](metric_name) are up [¥180.3k](delta_value, assessment="positive") relative to the same time last quarter.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Useful defaults in narrative-text-visualization — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added narrative-text-visualization from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend narrative-text-visualization for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
narrative-text-visualization is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: narrative-text-visualization is focused, and the summary matches what you get after install.
narrative-text-visualization is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
narrative-text-visualization fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in narrative-text-visualization — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for narrative-text-visualization matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend narrative-text-visualization for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 54