← 101CONTENT HISTORY
WHAT CHANGED
Update to 101
Snapshot Nov 9, 2026 · 00:21 UTC · version 2.0.5
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save 101 and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use when the primary 101 analytical workflow has allowed a standalone chart or composite report based on verified aggregates.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 43
},
{
"relative_path": "references/artifact-payload-example.json",
"size_in_bytes": 2676
},
{
"relative_path": "references/chart-design.md",
"size_in_bytes": 3326
},
{
"relative_path": "references/chart-payload-example.json",
"size_in_bytes": 1378
},
{
"relative_path": "references/chart-token-snapshot-1.0.154.json",
"size_in_bytes": 1815
}
],
"name": "analytics-visualization",
"skill_md_contents": "---\nname: analytics-visualization\ndescription: Use when the primary 101 analytical workflow has allowed a standalone chart or composite report based on verified aggregates.\nversion: \"2.2.0\"\nrole: helper\ninvocation: internal\nintents:\n - analytics.visualize\ndepends_on: []\nrequired_tools:\n - render_chart\n - validate_artifact\n - render_artifact\noptional_tools: []\nresources:\n - path: references/chart-design.md\n kind: semantic-guide\n required: true\n - path: references/chart-token-snapshot-1.0.154.json\n kind: token-snapshot\n required: true\n - path: references/chart-payload-example.json\n kind: payload-example\n required: true\n - path: references/artifact-payload-example.json\n kind: payload-example\n required: true\ncompletion:\n statuses:\n - готово\n - частично\n - заблокировано\n---\n\n# Analytics Presentation\n\nReceive the question, allowed format, verified aggregates, and sources from the primary analytical workflow. Do not read business data yourself. If a required tool is unavailable, return the limitation instead of promising a presentation.\n\n1. Read `references/chart-design.md`, the token snapshot, and canonical examples. Choose the simplest suitable type from the current schema; the question and data determine the chart count.\n2. Check units, signs, grain, period, and sources. `source`: `engine=101-mcp`, `language=mcp`, the actual allowed `tool` called, strict `executedAt`, and safe filters. Do not pass GUIDs, secrets, SQL, or temporary URLs.\n3. One chart: `render_chart({title,source,table,chart,display})`, without a `payload` wrapper. Up to 500 rows and 40 columns. Rows exactly match `table.columns`; `chart.fields` contains encoding objects such as `{\"field\":\"month\",\"type\":\"temporal\"}`.\n4. Composite artifact: `{surface,manifest,snapshot}`, `surface=report|dashboard`. Up to 4 charts, 8 tables, 8 metrics, 20 datasets of 500 rows each, 12 sources, and 50 blocks; these are limits, not target counts.\n5. In an audit, place a finding, meaning, and recommendation based on each chart's data after that chart. After all charts, add a separate overall conclusion and company actions.\n6. `snapshot.status=ready|partial|blocked|fixture`; `fixture` is only for test data, not for hiding a source failure. Incompleteness requires visible `accessIssues` with `lower_snake_case` identifiers and understandable messages.\n7. Run one `validate_artifact`, then, on success, one `render_artifact` with the same data. Validation itself displays nothing. Do not repeat a successful presentation; on `failed`, `INVALID_ARGUMENT`, or `invalid_analytics_payload`, return the error and do not claim success.\n\nPreserve accessible tooltips, legend, table, mobile presentation, and empty/incomplete data states. Formatting changes to loaded data run locally; new data requires returning to the primary workflow.\n"
}SHA-256 of public snapshot: 55652c8f6560e05dc5ad4dde892182a09e83ed6a8b6f21b927e2ea64f9940022