CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

export

Export Semantica graphs, results, and provenance to JSON, RDF, Parquet, CSV, GraphML, and other formats.

Quality

78%

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 ./plugins/skills/export/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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

The body is an lean, well-organized reference of per-format export snippets that respects Claude's competence and stays fully actionable at the template level. Its only weaknesses are minor execution gaps: placeholder variables, an undemonstrated --filter option, and ambiguity about file-versus-inline output.

DimensionReasoningScore

Conciseness

Each format section is a one-line description plus a minimal 3–5 line snippet (e.g. "Export graph data as JSON." followed by an import and a single call), with no explanation of concepts Claude already knows and no padding — every token earns its place.

5 / 5

Actionability

The snippets give concrete import paths and function signatures ("from semantica.export.methods import export_json", "export_json(data=graph_data, file_path=output, ...)") but rely on undefined placeholders (graph_data, output) and never demonstrate the advertised --filter option, so they are mostly rather than fully executable.

4 / 5

Workflow Clarity

As a simple single-action skill the per-format sections are unambiguous (import → call), but there are gaps: no guidance on where graph_data comes from, what a --filter query looks like, or when the output is a file versus an inline payload ("JSON file or inline JSON payload" is stated without saying which applies), so it falls short of the fully-unambiguous bar for a 5.

4 / 5

Progressive Disclosure

This is a compact (~1.4KB) simple skill with clear per-format sections and no content that belongs in separate files — no bundle files exist and none are needed, so well-organized sections satisfy the progressive-disclosure bar for small skills.

5 / 5

Total

18

/

20

Passed

Description

58%Weight 40%Scale 1-5

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 concise and specific about what it does, listing a concrete set of export formats tied to the Semantica domain. Its main weaknesses are the complete absence of any 'when to use' trigger guidance and limited natural-language keyword coverage beyond format names.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to export or save Semantica graph data, results, or provenance to a file or another format."

Include natural synonyms and file extensions users would actually say (e.g. "save", "download", "convert", ".json", ".csv", "Turtle") to broaden trigger-term coverage.

Consider naming one or two concrete actions beyond the single verb "export" (e.g. "serialize", "convert") to sharpen capability coverage.

DimensionReasoningScore

Specificity

"Export Semantica graphs, results, and provenance to JSON, RDF, Parquet, CSV, GraphML" names the domain and several concrete output formats, but all actions collapse into a single verb ("export"), leaving minor gaps in coverage rather than the comprehensive multi-action list of a 5.

4 / 5

Completeness

The description clearly answers 'what' (exports graphs, results, and provenance to enumerated formats) but contains no 'when'/Use-when clause at all, which per the judging guidelines caps completeness at 3; it is not a 2 because the 'what' is concrete rather than vague.

3 / 5

Trigger Term Quality

The keywords are mostly format names ("JSON, RDF, Parquet, CSV, GraphML") plus "export" and "provenance" — relevant, but common natural variations users would say ("save", "download", "convert", extensions like .json/.csv) are missing, matching the 'some relevant keywords but missing variations' anchor rather than the near-complete coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

"Semantica graphs" and "provenance" scope the skill to a specific tool, creating a mostly distinct niche with only minor overlap risk from generic words like "export" and "CSV" that could collide with other export skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

semantica-agi/semantica

Path

plugins/skills/export/SKILL.md

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.