CtrlK
BlogDocsLog inGet started
Tessl Logo

export

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

63

Quality

74%

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

82%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 a concise, well-structured reference with executable code for each export format and minimal padding. It is strong on token efficiency and actionability, with only minor gaps in output/error handling guidance and no progressive-disclosure references.

DimensionReasoningScore

Conciseness

Lean and efficient: each format section is a one-line description plus an executable code block and a brief output note, with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Provides concrete, copy-paste-ready code with imports and parameters for every format, but variables like graph_data and output are undefined placeholders, leaving a minor gap versus fully self-contained examples.

4 / 5

Workflow Clarity

The per-format sections make the single export action unambiguous and well sequenced, but there is no guidance on output handling for large graphs or error cases, a minor validation gap.

4 / 5

Progressive Disclosure

Content is well-organized into clear per-format sections and is self-contained with no nested references, though the body slightly exceeds the 50-line simple-skill threshold and offers no advanced-detail pointers.

4 / 5

Total

17

/

20

Passed

Description

66%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 clearly states what the skill does and names concrete output formats, but it omits any explicit 'Use when' trigger guidance, which limits completeness. It is distinctive thanks to the Semantica qualifier but could add natural trigger phrases.

Suggestions

Add an explicit 'Use when ...' clause naming trigger situations, e.g. 'Use when exporting Semantica knowledge graphs or when the user asks to save graph data as JSON, RDF, Parquet, CSV, or GraphML.'

Include common synonyms and file extensions (e.g. .json, .ttl, .parquet, .csv, .graphml) to broaden natural trigger coverage.

Mention provenance/results export as a distinct action verb alongside 'Export graphs' to strengthen specificity.

DimensionReasoningScore

Specificity

Names the Semantica domain and lists several concrete export targets (JSON, RDF, Parquet, CSV, GraphML), but the action is a single verb (export) repeated across formats rather than multiple distinct actions, leaving minor coverage gaps.

4 / 5

Completeness

Has a clear 'what' (export Semantica graphs/results/provenance to listed formats) but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes natural format keywords users would say (JSON, RDF, Parquet, CSV, GraphML) with good coverage, but misses common synonyms and phrases like 'knowledge graph', 'save as', or file extensions.

4 / 5

Distinctiveness Conflict Risk

Tied to the Semantica niche with named graph formats, making it mostly distinct with only minor overlap risk against generic export utilities.

4 / 5

Total

15

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
semantica-agi/semantica
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.