query

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

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/skills/query/SKILL.md

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 content is a tight, well-structured command skill with executable examples and clear output expectations per mode. The main gap is light actionability detail around argument binding and query-error handling rather than any structural problem.

Suggestions

Clarify how `$ARGUMENTS` maps to `<mode>` and the query/filter string so routing is unambiguous.

Bind or annotate the placeholder variables (`query`, `keywords`, `filter_type`) so the code snippets are fully copy-paste ready.

Add a brief note on handling invalid or empty query results to improve workflow clarity for edge cases.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient: each mode gets a one-line description, minimal executable code, and a return-format note, with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Concrete Python code is provided per mode, but variables like `query`, `keywords`, and `filter_type` are unbound placeholders, leaving minor gaps for fully copy-paste-ready execution.	4 / 5
Workflow Clarity	Each query mode is an unambiguous single action with a stated output format, but how `$ARGUMENTS` routes into `<mode>` and args is not spelled out, and there is no guidance for handling invalid queries.	4 / 5
Progressive Disclosure	At ~45 lines with no bundle files and no need for external references, the three clearly-headed mode sections satisfy the simple-skill exception for well-organized progressive disclosure.	5 / 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 clearly communicates the skill's domain and concrete query capabilities with strong distinctiveness, but omits any explicit 'when to use' trigger guidance, which caps completeness. Adding a 'Use when...' clause would raise the overall quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to query the Semantica knowledge graph, run SPARQL or Cypher queries, or search graph entities by keyword.'

Expand trigger-term coverage with synonyms users may say, such as 'triple store', 'semantic search', or 'graph database'.

Tighten the generic 'structured graph query patterns' phrasing into a more specific capability to push specificity toward 5.

Dimension	Reasoning	Score
Specificity	Lists several concrete query actions (SPARQL, Cypher, keyword search), but the trailing 'structured graph query patterns' is a generic catch-all leaving minor coverage gaps.	4 / 5
Completeness	The 'what' is clear ('Query the Semantica knowledge graph using SPARQL, Cypher, keyword search...') but there is no 'Use when...' trigger clause, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural domain terms users would say (SPARQL, Cypher, keyword search, knowledge graph) but misses common synonyms like 'triple store', 'semantic search', or 'graph database'.	4 / 5
Distinctiveness Conflict Risk	The product-specific 'Semantica knowledge graph' combined with distinctive query languages (SPARQL, Cypher) carves a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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/query/SKILL.md
Commit: 2a303cf

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.