CtrlK
BlogDocsLog inGet started
Tessl Logo

query

Query Semantica knowledge graphs — in-memory ContextGraph search, SPARQL over RDF triple stores, and Cypher over LPG backends.

66

Quality

79%

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/query/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 tight, code-driven reference that gives executable guidance for all three query backends alongside valuable non-obvious gotchas. It is well-structured for a simple skill, with only minor room to improve actionability placeholders and upfront routing framing.

DimensionReasoningScore

Conciseness

The body is lean: prose is limited to genuinely non-obvious gotchas ("load_from_file does not expand ~", "QueryEngine needs an object exposing execute_sparql()... not the TripletStore wrapper", "Not installed in this environment"), with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Each of the three modes has a real, import-bearing executable code block, but minor gaps remain (placeholder connection params `uri=..., user=..., password=...` and a `find_nodes(...)` method menu using ellipses), placing it just below fully copy-paste-ready.

4 / 5

Workflow Clarity

A single-purpose, read-only skill whose action is unambiguous per mode; the opening routing hint ("Which API you want depends on where the graph lives") frames the three-way choice, and no destructive/batch operations require validation checkpoints.

5 / 5

Progressive Disclosure

Well-organized into three clearly headed mode sections with no external bundle files needed and content appropriately kept inline; not a 5 because there is no explicit quick-start/overview section framing the routing decision up front beyond a one-line blockquote.

4 / 5

Total

18

/

20

Passed

Description

70%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 specific and highly distinctive, naming concrete query modes tied to a named product, but it omits any explicit 'when to use' trigger guidance, which caps completeness. Adding a Use-when clause would lift it into the top band.

Suggestions

Append an explicit trigger clause, e.g. 'Use when querying Semantica knowledge graphs, running SPARQL or Cypher, or searching an in-memory ContextGraph.'

Add a couple of natural synonyms users might say ('graph search', 'triple store query') to broaden trigger-term coverage beyond the technical protocol names.

DimensionReasoningScore

Specificity

Names the domain ("Query Semantica knowledge graphs") and lists three concrete query mechanisms ("in-memory ContextGraph search, SPARQL over RDF triple stores, and Cypher over LPG backends"), matching the 'lists several specific actions' anchor; not a 5 because coverage is not comprehensive (e.g. find/similarity lookups, decision queries are absent).

4 / 5

Completeness

Clearly states the 'what' (querying Semantica graphs via three modes) but provides no 'Use when...' or equivalent trigger guidance, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

Strong domain-natural keywords ("SPARQL", "Cypher", "knowledge graphs", "RDF", "LPG") that graph-database users would actually say; not a 5 because common synonyms/variations (e.g. 'graph search', 'triple store query') are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped to a specific product ("Semantica") with three distinct, specialized query modes, giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

16

/

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.