CtrlK
BlogDocsLog inGet started
Tessl Logo

decision

Full decision lifecycle in Semantica — record, query, find precedents (hybrid/advanced), analyze influence, explain, insights dashboard, list, and record exceptions. Uses AgentContext, ContextGraph, DecisionQuery, CausalChainAnalyzer, DecisionRecorder.

58

Quality

66%

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

Quality

Content

68%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 action-dense and well-structured with executable code per sub-command, but treats each command as an isolated single-step with no validation checkpoints for the record/exception writes, and inlines some reference-style material.

Suggestions

Add a validation step after record/exception writes (e.g., query the recorded decision_id to confirm persistence) to lift workflow clarity above the destructive-operation cap.

Define or show how the template variables (category, scenario, entities, args) are derived from the CLI invocation so snippets are fully copy-paste-ready.

Consider moving the commented DecisionQuery method catalog into a references file linked from the query section to improve progressive disclosure.

DimensionReasoningScore

Conciseness

Each sub-command section is a lean one-line description plus an executable code block with no concept over-explanation; the only trimmable redundancy is the repeated AgentContext import/boilerplate across sections.

4 / 5

Actionability

Every sub-command ships concrete, import-bearing Python code with parameter-hinting comments, but snippets use undefined template variables (category, scenario, entities) and include commented-out DecisionQuery methods, leaving minor gaps from fully copy-paste-ready.

4 / 5

Workflow Clarity

The skill is a catalog of independent sub-commands rather than a sequenced workflow, and the write operations (record, exception) lack validation or verification checkpoints, capping workflow clarity at 3 per the destructive/batch guideline.

3 / 5

Progressive Disclosure

Content is well-organized into clearly headed per-command sections with no nested references and no bundle files, though the inlined DecisionQuery method catalog and ~190-line length suggest some API reference could be split out.

4 / 5

Total

15

/

20

Passed

Description

63%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 specific and comprehensive about capabilities but is missing explicit "when to use" trigger guidance, which caps completeness. Trigger terms are domain-relevant but somewhat jargon-heavy and lack natural synonyms.

Suggestions

Add a "Use when..." clause with concrete trigger phrases (e.g., "Use when recording, querying, or explaining Semantica decisions, or finding precedents for a scenario").

Soften technical jargon in the trigger portion by leading with natural verbs users would say before naming the underlying classes.

Include common synonyms (e.g., "find similar past decisions" alongside "find precedents") to broaden natural-term coverage.

DimensionReasoningScore

Specificity

Lists eight concrete actions — "record, query, find precedents (hybrid/advanced), analyze influence, explain, insights dashboard, list, and record exceptions" — giving comprehensive coverage of the decision lifecycle rather than just a few actions.

5 / 5

Completeness

It clearly states what the skill does (full decision lifecycle with enumerated sub-operations) but provides no "Use when..." clause or equivalent trigger guidance, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Domain terms like "record", "query", "precedents", "influence", and "explain" are reasonably natural, but the description leans on technical jargon (AgentContext, CausalChainAnalyzer, hybrid/advanced) and lacks synonyms or natural user phrasing variations.

3 / 5

Distinctiveness Conflict Risk

The Semantica-specific scope and named classes (DecisionQuery, DecisionRecorder) carve a clear niche with minimal conflict risk, though the trigger phrasing could overlap with a sibling Semantica analytics skill.

4 / 5

Total

15

/

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.