CtrlK
BlogDocsLog inGet started
Tessl Logo

extract

Run the full Semantica semantic extraction pipeline on a file or selected text — NER, relations, events, coreference resolution, triplets, and validation. Clears result cache before each run. Returns Markdown tables with entity/relation/event/triplet results and inline validator warnings.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

87%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.

Highly actionable and concise content with a clear sequenced workflow, but the batch-extraction process lacks an explicit validation feedback loop, capping workflow clarity.

Suggestions

Add an explicit validation checkpoint with a feedback loop: if ExtractionValidator reports blocking issues, retry the relevant extraction step before returning results.

Specify what to do on validator errors (e.g., suppress low-confidence rows, or surface them as a separate 'Review needed' table) so the validation step is a true gate.

DimensionReasoningScore

Conciseness

The body is lean and direct — numbered steps plus executable code with brief inline labels — assuming Claude's competence and avoiding concept re-explanation, fitting the 'every token earns its place' anchor.

5 / 5

Actionability

It provides copy-paste-ready imports and class usage, concrete table templates, and an exact summary-line format, fully executable and covering the common pipeline case.

5 / 5

Workflow Clarity

Six steps are clearly sequenced and include cache clearing plus a validator, but for a batch extraction operation there is no explicit validate→fix→retry feedback loop or checkpoint, which caps workflow clarity at 3 per the rubric guidance.

3 / 5

Progressive Disclosure

This is a self-contained, well-sectioned single-file skill under 50 lines with no external references, qualifying for the simple-skill exception that allows a 5.

5 / 5

Total

18

/

20

Passed

Description

75%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.

A specific, distinct description that lists concrete capabilities, but it omits an explicit 'Use when...' trigger clause, which caps its completeness.

Suggestions

Add an explicit 'Use when ...' clause naming trigger phrases (e.g., 'Use when extracting entities, relations, events, or triplets from text').

Include natural synonyms or file/extension cues users might say to lift trigger-term coverage toward 5.

DimensionReasoningScore

Specificity

The description enumerates many concrete actions — 'NER, relations, events, coreference resolution, triplets, and validation', 'Clears result cache', 'Returns Markdown tables ... and inline validator warnings' — matching the comprehensive-coverage anchor.

5 / 5

Completeness

It gives a clear 'what' but no explicit 'Use when...' trigger clause, and the judging guideline caps completeness at 3 when such trigger guidance is missing.

3 / 5

Trigger Term Quality

It surfaces natural domain terms a user would say ('semantic extraction', 'NER', 'relations', 'events', 'coreference', 'triplets') but lacks synonyms or file-extension variants, fitting the 'good coverage, a few natural terms missing' anchor just below 5.

4 / 5

Distinctiveness Conflict Risk

The Semantica pipeline with its named components carves a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

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.