CtrlK
BlogDocsLog inGet started
Tessl Logo

interactive-viz

Multi-modal interactive data presentation for agentsociety-analysis — EDA bundle (PyGWalker, Plotly, sortable tables, eda_hub), plotly/altair claim charts, HTML tab surfaces. Use in explore, refine, and produce stages.

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./extension/skills/agentsociety-analysis/v1.0.0/support/interactive-viz/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-organized with concrete commands, but actionability is weakened by unexplained placeholders and a thin Python example, the workflow lacks validation checkpoints, and the referenced files are missing from the bundle.

Suggestions

Add a short usage example for the chart_export imports (e.g., export_plotly_html(df, path)) so the Python section is actionable, and clarify the CLI placeholders (DB, DIR, WS, HID).

Add a verification step after run-eda (e.g., confirm data/eda_hub.html exists and opens) to close the batch workflow loop.

Either include the referenced files under references/ (eda.md, charts.md, reports.md) or remove the dangling 'Read order' references so disclosure is honest about what exists.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with no padding or explanation of concepts Claude already knows; every line (triggers, commands, read order, import, report) earns its place.

3 / 3

Actionability

Concrete CLI commands with real syntax are provided, but they use unexplained placeholders (DB, DIR, WS, HID) and the Python section shows only an import with no usage example, leaving the guidance incomplete rather than copy-paste ready.

2 / 3

Workflow Clarity

Steps are sequenced (Read order 1-3, Commands, Report), but run-eda is a batch generation step with no validation or verification of outputs, so the workflow lacks the checkpoints that would raise it to a 3.

2 / 3

Progressive Disclosure

The overview is well-signaled with one-level-deep references ('references/eda.md', 'charts.md', 'reports.md'), but those bundle files do not exist in the skill directory, so the navigation is dangling rather than functional.

2 / 3

Total

9

/

12

Passed

Description

57%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinctive, clearly targeting a narrow niche, but its trigger guidance relies on internal stage names and jargon rather than natural user language, weakening when-to-use clarity.

Suggestions

Rewrite the 'Use in explore, refine, and produce stages' clause as natural user triggers (e.g., 'Use when the user wants interactive data exploration, sortable tables, or embedded EDA dashboards').

Lead with concrete verbs/actions (e.g., 'Generate, embed, and export interactive visualizations') instead of leading with the tool list.

Reduce internal jargon ('agentsociety-analysis', 'eda_hub', '§数据') in favor of terms a user would actually say.

DimensionReasoningScore

Specificity

Names a concrete domain and several specific tools ('PyGWalker, Plotly, sortable tables, eda_hub', 'plotly/altair claim charts, HTML tab surfaces'), but the actions are tool lists under one verb ('data presentation') rather than multiple distinct concrete actions like 'extract, fill, merge'.

2 / 3

Completeness

It states what the skill does and includes a 'Use in explore, refine, and produce stages' clause, but the 'when' is tied to internal pipeline stages rather than user-recognizable triggers, so it sits between the 'when implied' and 'explicit natural triggers' anchors.

2 / 3

Trigger Term Quality

Some relevant keywords appear ('interactive data presentation', 'EDA', 'claim charts'), but they are mixed with internal jargon ('agentsociety-analysis', 'eda_hub', '§数据') and stage-based triggers a user would not naturally say, missing common natural variations.

2 / 3

Distinctiveness Conflict Risk

It carves a clear niche (interactive EDA visualization for agentsociety-analysis) with distinct, specific triggers that are unlikely to fire for unrelated skills.

3 / 3

Total

9

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository
tsinghua-fib-lab/AgentSociety
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.