CtrlK
BlogDocsLog inGet started
Tessl Logo

explain

Explain Semantica reasoning, decision logic, and graph results with traceability, causal context, and human-readable rationale.

59

Quality

67%

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

Quality

Content

78%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 concise, actionable, and well-structured for a simple single-purpose skill, with real executable code examples and clear sectioning, limited only by minor unspecified variables and absent error-recovery guidance.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: a usage line plus two short subcommand sections each with a compact code block and a one-line output statement, with only minor over-explanation in the inline comments.

4 / 5

Actionability

Provides mostly executable guidance with real imports and concrete method calls (ExplanationGenerator, ctx.trace_decision_explainability, ctx.get_causal_chain), with minor gaps where some variables (reasoning_result, depth) are referenced but not shown bound.

4 / 5

Workflow Clarity

Two clearly-separated entry points each with explicit inputs and stated outputs; the task is non-destructive so the validation cap does not apply, but no error-recovery guidance for missing IDs keeps it just below a 5.

4 / 5

Progressive Disclosure

At under 50 lines with no need for external bundle files, the well-organized section headers (decision, graph) satisfy the simple-skill exception allowing a 5 from clear organization alone.

5 / 5

Total

17

/

20

Passed

Description

56%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 well-scoped to a specific platform and names concrete explanation targets, but omits an explicit 'Use when' trigger clause, which caps completeness and limits trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when the user asks why a Semantica decision was reached or wants graph relationships explained').

Include common synonyms and natural variations users might say (e.g., 'justify', 'trace', 'why did it decide') to broaden trigger-term coverage.

Consider naming concrete output artifacts (decision factors, rule traces, causal chains) in the description to lift specificity toward a 5.

DimensionReasoningScore

Specificity

Names the Semantica explanation domain and lists three concrete action targets ('reasoning', 'decision logic', 'graph results') with modifiers (traceability, causal context), placing it between the 3-anchor (1-2 actions) and 4-anchor (several specific actions, minor gaps).

3.5 / 5

Completeness

Provides a clear 'what' (explain Semantica reasoning, decisions, and graph results) but no explicit 'when'/'Use when...' clause; per rubric guidance, a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes some relevant natural terms ('reasoning', 'decision logic', 'graph results', 'explain') a user might say, but lacks common synonyms, file extensions, or explicit 'Use when' trigger phrasing, fitting the 3-anchor (some relevant keywords, missing variations).

3 / 5

Distinctiveness Conflict Risk

Tightly scoped to the Semantica platform with domain-specific triggers (reasoning, decision logic, graph results), giving a clear niche with minimal conflict risk, with only minor possible overlap with generic 'explain' skills.

4 / 5

Total

13.5

/

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.