CtrlK
BlogDocsLog inGet started
Tessl Logo

query

Query the Semantica knowledge graph using SPARQL, Cypher, keyword search, and structured graph query patterns.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A concise, well-organized command skill that presents three query modes with real API calls and clear outputs. The main gap is actionability: the cypher/search snippets omit setup already shown for sparql and reference undefined argument variables, keeping those examples just short of copy-paste ready.

Suggestions

Repeat the QueryEngine setup in the cypher and search snippets, or state once that `engine` is constructed as in the sparql example, so every mode is independently executable.

Show how `$ARGUMENTS` maps to `query`, `keywords`, and `filter_type` (e.g., a one-line parse example) so the snippets reference defined variables.

DimensionReasoningScore

Conciseness

The body is lean with no concept explanation, each mode given as a short code snippet plus a one-line return description; every token earns its place. Not a 2 because there is no unnecessary explanation or padding.

3 / 3

Actionability

Code snippets show real API calls (engine.query_sparql, engine.search), but cypher/search omit the import/engine setup shown for sparql, and `query`, `keywords`, `filter_type` are referenced but never defined — missing key details, matching the level-2 anchor. Not a 3 because the examples are not fully copy-paste ready.

2 / 3

Workflow Clarity

Three modes are cleanly organized with usage, code, and output; as a simple read-only query skill the single actions are unambiguous, so workflow clarity can score 3. Not a 2 because the structure and per-mode sequence are explicit and no destructive/batch operation requires validation.

3 / 3

Progressive Disclosure

Under 50 lines with no external references needed (no references/scripts/assets present); sections are well-organized by mode, which per the simple-skills note earns a 3. Not a 2 because the content is appropriately structured with nothing that should be split out.

3 / 3

Total

11

/

12

Passed

Description

82%

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

A specific, third-person description naming four concrete query modes, with strong trigger-term coverage and low conflict risk. Its main weakness is the absence of an explicit "Use when..." trigger clause, which caps completeness at 2.

Suggestions

Append a "Use when..." clause (e.g., "Use when the user wants to query or search the Semantica knowledge graph, run SPARQL/Cypher queries, or find entities by keyword.") to lift completeness to 3.

DimensionReasoningScore

Specificity

"Query the Semantica knowledge graph using SPARQL, Cypher, keyword search, and structured graph query patterns" lists multiple concrete query actions (SPARQL, Cypher, keyword search, structured patterns), matching the level-3 anchor of several specific actions.

3 / 3

Completeness

It clearly answers "what" (query the Semantica graph via four modes) but has no "Use when..." clause or equivalent trigger guidance, so per the guidelines completeness is capped at 2. Not a 1 because the "what" is explicit and concrete.

2 / 3

Trigger Term Quality

"SPARQL, Cypher, keyword search, and structured graph query patterns" are natural terms a user would say when needing graph queries; coverage spans the common modes a user would name. Not a 2 because it covers multiple natural phrasings rather than a single jargon term.

3 / 3

Distinctiveness Conflict Risk

"Semantica knowledge graph" with SPARQL/Cypher modes carves a clear niche unlikely to trigger for unrelated skills. Not a 2 because the Semantica scope plus specific query languages make overlap with sibling skills unlikely.

3 / 3

Total

11

/

12

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.