CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nexa

GeneXus expert system for object modeling and knowledge base management

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./nexa/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 a dense, well-structured instruction set with concrete MCP tool invocations, a clearly sequenced workflow with validation checkpoints, and a genuinely useful reference index backed by a real bundle. Its main weaknesses are cross-section redundancy (GUIDELINE/Responsibilities, CHECKLIST/BEST PRACTICES) and an implicit rather than explicit error-recovery loop.

Suggestions

Merge or remove the redundant GUIDELINE section and de-duplicate QUALITY CHECKLIST items that restate BEST PRACTICES and CONSTRAINTS rules to tighten token usage.

Add an explicit validation feedback loop after "Run `validate_kb_text_files` tool after each dump/write": instruct to read errors, fix the dumped files, and re-validate until clean before proceeding to import/build.

Specify how to "Search candidate objects systematically" (which tool, filters, or file patterns) so that step is as actionable as the rest of the workflow.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows, but contains redundant structure: the GUIDELINE section ("Interprets user needs, validates Knowledge Base objects existence, analyzes cross-references, creates execution plans") restates Responsibilities and Workflow, and QUALITY CHECKLIST items ("Reuses existing artifacts first; creates new ones only when justified") duplicate BEST PRACTICES. Mostly efficient but several sections could be tightened or merged, matching anchor 3.

3 / 5

Actionability

Concrete, executable guidance throughout: named MCP tools with arguments ("Run `validate_kb_text_files` tool after each dump/write", "Set `environment` argument; values: `.NET`, `Java`"), defaults ("Default `localhost:8001/mcp`"), and paths ("Add `/src` for AI-generated files"). Not 5 because some steps stay high-level, e.g. "Search candidate objects systematically" gives no method or tool.

4 / 5

Workflow Clarity

The WORKFLOW is clearly sequenced with an approval gate ("After approval, execute"), validation checkpoints ("validate_kb_text_files" after each write, then "build_one"/"build_all"), and a fallback branch when the MCP server is unavailable. Not 5 because there is no explicit error-recovery feedback loop (what to do when validation or build fails) — validation is commanded but the fix-and-retry cycle is left implicit.

4 / 5

Progressive Disclosure

The body is a well-organized index: every object type gets purpose, use-when, and a verified link (e.g. "Reference: [Folder object](references/object-folder.md)", all 24 referenced paths exist), plus an explicit six-step "Resource selection protocol". Not 5 because references chain two levels deep — object-*.md files link onward to common-*.md, properties-*.md, and global-*.md files — which exceeds the one-level-deep ideal, though the protocol and clear signaling keep navigation manageable.

4 / 5

Total

15

/

20

Passed

Description

48%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 identifies a distinctive niche (GeneXus) but reads as a domain label rather than a capability statement: no concrete actions, no trigger terms beyond the platform name, and no 'use when' guidance. It would benefit most from an explicit use-when clause and a list of concrete operations.

Suggestions

Add an explicit 'Use when...' clause listing trigger moments, e.g. 'Use when the user mentions GeneXus, Knowledge Base operations, or asks to create or review GeneXus objects.'

Replace 'expert system' with 2-3 concrete actions, e.g. 'Create, validate, and export GeneXus Knowledge Base objects (Transactions, Transactions, Procedures, SDTs, Panels) and manage modules.'

Include the object-type names users actually say (Transaction, Procedure, SDT, Data Provider, Panel) as trigger terms to improve keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain ("GeneXus") and two broad activity areas ("object modeling and knowledge base management") but "expert system" is fluffy and no concrete actions (create, validate, build, export) are listed, matching the anchor 'names the domain but actions are minimal or generic'. It is not 3 because no genuinely concrete, countable action verb is given.

2 / 5

Completeness

It provides a reasonably clear 'what' ("object modeling and knowledge base management") but contains no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2 because the 'what' is not vague.

3 / 5

Trigger Term Quality

"GeneXus" and "knowledge base" are natural terms a user would say, but common variations and object-type triggers users actually mention (Transaction, Procedure, SDT, Panel, WorkWith) are absent, fitting 'some relevant keywords but missing common variations or synonyms'. Not 4 because coverage beyond the platform name is thin.

3 / 5

Distinctiveness Conflict Risk

"GeneXus" is a distinctive proprietary platform giving a clear niche with minimal conflict risk, though the generic "knowledge base management" tail could overlap with generic data-modeling or documentation skills. Not 5 because the anchor-5 example includes explicit trigger phrases, which this description lacks.

4 / 5

Total

12

/

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

cinthamo/genexus-skills

Path

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