Semiotic is a React library for building data visualizations such as charts, network graphs, streaming displays, and coordinated dashboards. It is used by developers who need to render data-driven interfaces, including with AI coding assistants. Its schemas and MCP server support the catalogue's add-ons for generating chart code.
Borrowing it
Nothing to install: this file belongs to nteract/semiotic. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nteract/semiotic/main/.agents/skills/blog-post/SKILL.mdgit clone --depth 1 https://github.com/nteract/semioticWrote 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.
[](https://agentmods.dev/skills/nteract/semiotic/blog-post)<a href="https://agentmods.dev/skills/nteract/semiotic/blog-post"><img src="https://agentmods.dev/badge/skills/nteract/semiotic/blog-post/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.
<a href="https://agentmods.dev/skills/nteract/semiotic/blog-post"><img src="https://agentmods.dev/badge/skills/nteract/semiotic/blog-post.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 76 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00044 | $0.03355 |
| Opus 5.5 | $0.00018 | $0.01342 |
| Sonnet 5.5 | $0.00009 | $0.00671 |
| Haiku 4.5 | $0.00004 | $0.00335 |
Grade A, and why
blog-post 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing a Semiotic blog post
This skill writes one entry for the Semiotic blog. The blog lives at
/blog/; entries live at /blog/<slug>/. Three story shapes are
supported — pick the one that matches what's being written:
- Chart explainer — single chart, "what / why / when / wiring".
- Release summary — what's new in a version, ordered by impact.
- Narrative / case study — comparative posts ("X vs Y"), walkthroughs, recreations of historical visualizations.
Every entry follows the same structure regardless of shape. The why-care section is non-negotiable: the post has to give the reader a reason to read it that lands even if they're not currently using Semiotic. The blog isn't reference docs; it's a publication that happens to be hosted on the docs site.
Before writing anything
Ask the user for the author byline unless they've already given one. Don't assume "Elijah Meeks" by default — many entries will be co-authored or attributed to "Semiotic Team" for releases. One short question, then proceed.
File structure
For a new entry with slug <slug>:
- Body component —
docs/src/blog/entries/<slug>.jsx. Default export is{ slug, title, subtitle, author, date, tags, excerpt, component, ogChart? }. Thecomponentis a React function returning JSX (the entry's body — no header, no chrome, theBlogEntryViewwraps it). - Register in registry —
docs/src/blog/entries.jsimports the new file and adds it toblogEntries. - Register in metadata mirror —
docs/src/blog/entries-meta.jsgets the same metadata object (withoutcomponent, without the React imports). This mirror is read by the OG-card generator and the prerender script, both of which run under plain Node and can't load JSX.
Both registry files must stay in sync. The OG-card generator and
prerender script read entries-meta.js; the React app reads
entries.js.
Required fields
{
slug: "kebab-case-route",
title: "Title-Case Headline",
subtitle: "One or two sentences orienting the reader.",
author: "Author Name", // ASK THE USER if unspecified
date: "YYYY-MM-DD", // ISO; controls sort order
tags: ["release"] | ["chart-explainer", "xy"] | ...,
excerpt: "2–3 sentence preview shown on the index card.",
component: Body, // function returning JSX
ogChart: { component: "DifferenceChart" }, // optional, see OG step
}
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 335 lines · 44 tokens per session scan A c5f054b7c16f
blog-post is a skill published in the GitHub repository nteract/semiotic (2,717 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 3,355 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
data-viz-2025
State-of-the-art data visualization for React/Next.js/TypeScript with Tailwind CSS. Creates compelling, tested, and accessible visualizations following Tufte principles and NYT Graphics standards. Activate on "data viz", "chart", "graph", "visualization", "dashboard", "plot", "Recharts", "Nivo", "D3". NOT for static…
example
Create new example charts for Recharts documentation website.
commit
Create git commits in the Unovis repo that pass its commitlint rules. Unovis uses a CUSTOM commit format (Type | Scope | Subscope: Sentence-case subject), NOT Conventional Commits, so feat:/fix: will be rejected by the commit-msg hook. Use this whenever staging and committing changes, writing or rewriting a commit…
add-component
Add a new visualization component to Unovis end to end — the TypeScript core, the shared registry, the generated framework wrappers, a dev example, a gallery example, and docs. Use when asked to add/create a new component, chart type, plot, or diagram to the library, or to wire an existing core component through to…
add-gallery-example
Add an example to the Unovis gallery — a per-framework example directory under packages/shared/examples, registered in examples-list.tsx, with light/dark previews. Use when asked to add a gallery example, showcase a chart in the gallery, or create the gallery entry that accompanies a new component.
open-pr
Open a pull request for the Unovis repo with the project's conventions — correct branch off main, the standard commit grouping, and the checklist-style PR body used by the maintainers. Use when asked to open/create/submit a pull request, prepare a branch for review, or write a PR description in this repository.