CtrlK
BlogDocsLog inGet started
Tessl Logo

ontology

Manage ontology schemas, concepts, relationships, and alignments for Semantica knowledge graphs.

61

Quality

71%

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/ontology/SKILL.md
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.

The content is concise and well-organized into two clear single-step tasks with appropriate code snippets. Its main weakness is actionability: the code examples are fragmentary rather than fully executable, with unbound variables preventing copy-paste use.

Suggestions

Make code examples executable end-to-end by binding inputs (e.g., show how concept_name, graph, and schema_file are obtained) so snippets are copy-paste ready.

Show the return-value shape of get_concept and validate_graph with a short example output so Claude knows what to expect and how to act on it.

DimensionReasoningScore

Conciseness

The body is lean with short headers, minimal prose, and code snippets, with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

It provides concrete code (OntologyManager, get_concept, validate_graph) but the snippets are fragmentary with unbound variables (concept_name, graph, schema_file) and are not copy-paste executable end-to-end, fitting 'some concrete guidance but incomplete; missing key details'.

2 / 3

Workflow Clarity

Each task (describe, validate) is a single unambiguous action clearly sequenced; per the simple-skills note, single-action skills can score 3, and validate even surfaces errors and correction suggestions.

3 / 3

Progressive Disclosure

The skill is under 50 lines, single-purpose, and needs no external references; its two well-organized sections satisfy the guideline allowing under-50-line skills to score 3 on organization alone.

3 / 3

Total

11

/

12

Passed

Description

57%

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 identifies its domain and is well-scoped to Semantica knowledge graphs, but it lacks explicit use-when trigger guidance and leans on the generic verb 'Manage' rather than listing concrete actions. Adding a 'Use when...' clause and named operations would raise it.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when managing ontology schemas, defining concepts, or aligning knowledge graphs in Semantica') to satisfy the 'when' half of completeness.

Replace the generic verb 'Manage' with specific actions like 'Create, edit, and validate ontology schemas, concepts, and relationships' to strengthen specificity.

Include more natural trigger phrasings users would say (e.g., 'ontology', 'knowledge graph', 'concept hierarchy', 'schema alignment') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

It names concrete domain objects ('ontology schemas, concepts, relationships, and alignments') but relies on the generic verb 'Manage' rather than enumerating distinct actions, matching the 'names domain and some actions, but not comprehensive' anchor.

2 / 3

Completeness

It clearly states what the skill does but omits any 'Use when...' trigger guidance, so per the guidelines completeness is capped at 2 ('has what, but when is missing or only implied').

2 / 3

Trigger Term Quality

It includes relevant domain keywords ('ontology', 'schemas', 'concepts', 'relationships', 'alignments', 'Semantica knowledge graphs') but lacks broader natural-language variations a user would say, fitting 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The scoping phrase 'for Semantica knowledge graphs' gives it a clear niche unlikely to conflict with unrelated skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

9

/

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.