CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deduplicate

Detect duplicate entities, duplicate groups, and relationship duplicates in Semantica using fuzzy matching, schema heuristics, and graph similarity.

Quality

75%

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

Quality

Content

80%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 an exemplar of token efficiency: terse, well-structured, and code-first with no filler. Its one substantive weakness is the missing validation/feedback loop for a batch merge operation — candidates are detected but nothing tells Claude how to review or safely apply merges.

Suggestions

Add a validation checkpoint before applying merges, e.g., "Review candidate groups and confirm before merging; re-run detection after cleanup to verify no duplicates remain."

Show where `entities`, `relation_list`, and threshold values come from (e.g., loading from the Semantica graph or a concrete default threshold) to make the code copy-paste ready.

Clarify whether the skill should apply merge recommendations or only report them, since the current output description stops at recommendations.

DimensionReasoningScore

Conciseness

The ~35-line body is lean with zero padding: a one-line purpose ("Remove duplicates from the knowledge graph"), usage syntax, and two terse strategy sections each going straight to code. Every token earns its place and no concepts Claude already knows are explained.

5 / 5

Actionability

Concrete, near-executable code is provided for both strategies (e.g., "finder.detect_duplicates(entities, threshold=threshold)"), but key variables like `entities`, `threshold`, `relation_list`, and `similarity` are never bound to concrete values or shown being loaded from the graph — minor gaps keep it from copy-paste ready.

4 / 5

Workflow Clarity

Deduplication producing "representative merge recommendations" is a batch operation that modifies the graph, yet no validation or verification step exists (no review-before-merge, no post-merge check). Per the rubric, batch operations without validation are capped at 3 even though the per-strategy sequence itself is clear.

3 / 5

Progressive Disclosure

The skill is under 50 lines and needs no external references; content is well organized into two clearly signaled strategy sections with consistent structure, which merits a 5 under the simple-skill exception.

5 / 5

Total

17

/

20

Passed

Description

58%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 concise and specific about what the skill does within the Semantica domain, with concrete actions and methods named. Its main weaknesses are the complete absence of "when to use" trigger guidance and missing natural synonyms like "dedupe" or "merge", which limit both completeness and trigger discoverability.

Suggestions

Add a trigger clause such as "Use when the user mentions duplicates, deduping, or merging entities/relations in the knowledge graph" to answer the 'when' half of completeness.

Include natural synonyms users would actually say (dedupe, dedup, merge, redundant) to improve trigger term coverage.

Mention the outcome of detection (e.g., merge recommendations or cleanup) so the capability coverage is comprehensive rather than stopping at detection.

DimensionReasoningScore

Specificity

Lists several concrete actions ("Detect duplicate entities, duplicate groups, and relationship duplicates") and three named methods ("fuzzy matching, schema heuristics, and graph similarity"), but coverage has minor gaps — nothing about merging or resolving the detected duplicates.

4 / 5

Completeness

The "what" is clear (detect entity, group, and relationship duplicates), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Relevant keywords like "duplicate", "Semantica", and "fuzzy matching" are present, but common natural variations users would say — "dedupe", "dedup", "merge entities", "redundant" — are missing.

3 / 5

Distinctiveness Conflict Risk

Scoped to the Semantica domain with specific methods, giving it a mostly distinct niche; however, generic terms like "duplicates" without explicit trigger phrases leave minor overlap risk with related graph-cleanup skills.

4 / 5

Total

14

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

semantica-agi/semantica

Path

plugins/skills/deduplicate/SKILL.md

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.