CtrlK
BlogDocsLog inGet started
Tessl Logo

engram-visual-language

Visual language rules for Engram surfaces. Trigger: Any dashboard styling, typography, spacing, or visual identity change.

72

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-organized into clear sections suited to a simple styling skill. The primary weakness is actionability: many rules are subjective principles rather than concrete, measurable guidance.

Suggestions

Make rules concrete and measurable, e.g. replace "clearer breathing room" with specific spacing guidance ("use 2x base spacing between major sections") or link to a defined token scale.

Add a short concrete example (before/after) or a reference palette of actual color tokens so "TUI-inspired palette" is unambiguous.

Define "feel like Engram" with 2-3 checkable criteria rather than leaving it as a subjective judgment.

DimensionReasoningScore

Conciseness

The body is lean with short imperative rules ("Metrics should read instantly.", "Important text must never touch borders") and no padding or explanation of concepts Claude already knows, matching the lean-and-efficient anchor.

3 / 3

Actionability

Rules name concrete targets (palette, typography, spacing, tables, borders) but stay subjective ("feel like Engram", "breathing room", "intentionally"), lacking specific measurable guidance an instruction-only skill should provide.

2 / 3

Workflow Clarity

As a simple single-purpose styling skill, the "When to Use" scope and clearly organized rule sections make the single task unambiguous; no destructive/batch operation requires validation checkpoints.

3 / 3

Progressive Disclosure

A simple skill under 50 lines with no need for external references, organized into three clear sections (When to Use, Visual Rules, Density Rules), satisfying the simple-skill allowance for well-organized sections.

3 / 3

Total

11

/

12

Passed

Description

90%

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 concise, scoped to a clear niche, and includes an explicit trigger clause covering natural user terms. Its main weakness is that it states abstract "rules" rather than concrete actions.

Suggestions

Replace the abstract "Visual language rules" framing with concrete actions, e.g. "Applies Engram's TUI-inspired palette, typography, and spacing rules to dashboard surfaces."

Add a couple more natural trigger variations (e.g. "theme", "colors", "layout") to broaden keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ("Visual language rules for Engram surfaces") but describes abstract "rules" rather than listing concrete actions, matching the anchor for naming domain with some actions but not comprehensive.

2 / 3

Completeness

Both "what" (visual language rules for Engram surfaces) and "when" (explicit "Trigger:" clause) are answered, matching the anchor that clearly answers both with explicit triggers.

3 / 3

Trigger Term Quality

"Trigger: Any dashboard styling, typography, spacing, or visual identity change" provides natural terms a user would actually say, giving good coverage of relevant variations.

3 / 3

Distinctiveness Conflict Risk

Scoped specifically to "Engram surfaces" with distinct styling triggers, making it unlikely to conflict with other skills.

3 / 3

Total

11

/

12

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
Gentleman-Programming/engram
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.