CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

78%

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

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

A lean, highly actionable command-dispatch skill: every subcommand maps to concrete semantica APIs with explicit output formats. The main weaknesses are repeated boilerplate across sections, placeholder variables that prevent copy-paste execution, and no error-handling guidance.

Suggestions

State the shared setup (AgentContext import and construction with decision_tracking=True) once at the top and drop it from each section to cut repeated tokens.

Show how CLI arguments bind to the code placeholders (e.g., `scenario = args[0]` or argparse equivalents) so snippets become copy-paste executable.

Add brief handling for empty results (query/precedents/list returning nothing) so the workflow includes a validation checkpoint.

DimensionReasoningScore

Conciseness

Each subcommand section is a header, one-line description, code block, and output format with zero concept explanation. However, the boilerplate pair `from semantica.context import AgentContext` / `ctx = AgentContext(decision_tracking=True)` repeats in all eight sections and could be trimmed.

4 / 5

Actionability

Concrete, specific API calls with output table formats and argument handling (e.g., `end=datetime.fromisoformat(to_date or "2099-12-31")`), but the snippets reference undefined placeholders (`scenario`, `args`, `as_of_date`, `category`), so they are not fully copy-paste executable.

4 / 5

Workflow Clarity

Each of the eight subcommands is an unambiguous single action with a consistent structure (usage, code, output format), and `exception` sequences record-then-find-similar clearly. No destructive or batch operations require validation caps, though there is no error-recovery guidance for cases like empty query results.

4 / 5

Progressive Disclosure

No bundle files exist and the ~190-line body is well organized into scannable per-subcommand sections. The inline `DecisionQuery` method listing and the repeated AgentContext setup could be moved to a reference file, leaving minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

71%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, comprehensive what-description that accurately enumerates the skill's subcommands in third person. Its main gap is the complete absence of when-to-use guidance, and the class-name inventory at the end adds jargon without trigger value.

Suggestions

Append a "Use when..." clause with concrete triggers, e.g., "Use when recording, querying, or explaining decisions, finding precedents, or logging policy exceptions in Semantica."

Drop or shorten the trailing class-name list (AgentContext, ContextGraph, DecisionQuery, CausalChainAnalyzer, DecisionRecorder) — it is implementation detail, not capability description.

Add a natural synonym or two such as "decision log" or "audit trail" to improve trigger coverage.

DimensionReasoningScore

Specificity

The description lists eight concrete actions — "record, query, find precedents (hybrid/advanced), analyze influence, explain, insights dashboard, list, and record exceptions" — comprehensively covering the body's subcommands in third-person voice.

5 / 5

Completeness

The "what" is clear and detailed, but there is no "Use when..." clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Natural terms like "decision", "precedents", "influence", "explain", and "exception" are present, but common variations ("decision log", "past decisions", "audit") are missing and the trailing class names (AgentContext, ContextGraph, etc.) are jargon rather than user-facing triggers.

4 / 5

Distinctiveness Conflict Risk

"Full decision lifecycle in Semantica" carves out a clear niche with low conflict risk against generic skills, though within the Semantica ecosystem it could overlap with related context/decision-adjacent skills.

4 / 5

Total

16

/

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/decision/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.