CtrlK
BlogDocsLog inGet started
Tessl Logo

tpscloud/charmedimsure

Source-verified skills for the Charm terminal stack: Bubble Tea v2, Bubbles v2, Lip Gloss v2, Huh v2, Log v2, Glamour v2, plus the gum and vhs CLIs.

100

1.02x
Quality

100%

Does it follow best practices?

Impact

100%

1.02x

Average score across 9 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

100%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 a dense, example-driven reference that trusts the reader: no concept padding, measured behaviors instead of vague claims, a sequenced workflow with an explicit verify-and-fix loop, and a clean split between core styling (inline) and specialized subpackages (references). The explicit flagging of excerpt blocks and the "Mistakes that cost time" section show deliberate, high-quality skill construction.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence throughout: it never explains what Go, ANSI codes, or TUIs are, and every section carries non-obvious, measured facts ("Width(10).Padding(0, 1).Border(NormalBorder()) renders exactly 10 cells wide; adding Margin(0, 1) makes it 12"). The version pin ("Pinned and verified against v2.0.6") is a scope statement rather than time-sensitive branching guidance, and v1 material is delegated to a dedicated "Migrating from v1" section, so the time-sensitivity penalty does not apply. Every token earns its place, matching anchor 5.

5 / 5

Actionability

Guidance is concrete and copy-paste-ready: real signatures like HasDarkBackground(os.Stdin, os.Stdout), colorprofile.Detect(os.Stdout, os.Environ()), and Blend1D(len(runes), ...) with complete usage snippets covering the common cases (basics, colors, gradients, adaptive, layout). The two sketch blocks are explicitly flagged and justified up front ("// excerpt blocks are API sketches"), which is the rubric's permitted exception; the anchor-5 standard of executable examples covering common cases is met.

5 / 5

Workflow Clarity

The Workflow section gives a clear 6-step sequence culminating in explicit validation with a feedback loop: "Check in a real terminal and compare lipgloss.Size with the width you expected... Fix and rerun", including cause-to-symptom diagnostics ("Wrong colors usually mean output went through fmt"). The "Mistakes that cost time" section adds an error-recovery checklist. This is not a destructive or batch operation, so the validation cap does not apply; the content matches anchor 5's explicit validation and error-recovery structure.

5 / 5

Progressive Disclosure

The body is a well-organized overview and specialized material is split into four real, verified bundle files (references/overlays.md, tables.md, trees-and-lists.md, migration.md), each clearly signaled with a one-line summary of its contents (e.g., "Read [references/overlays.md]... for layers, the compositor, Z order, and mouse hit testing"). References are one level deep — the only cross-link (migration.md to overlays.md) points to a file directly reachable from SKILL.md, not to buried content. This matches anchor 5's clear overview with well-signaled one-level-deep references.

5 / 5

Total

20

/

20

Passed

Description

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

An exemplary description: it states a comprehensive set of concrete capabilities, provides explicit and natural trigger phrases for when to use it, pins the exact package and version, and draws clear boundaries against sibling skills in the same ecosystem. No vagueness, over-claims, or voice violations are present.

DimensionReasoningScore

Specificity

The description enumerates concrete capabilities comprehensively: "ANSI colors and terminal colors, borders and boxes, padding, alignment, joining and placing blocks, light or dark adaptation, gradients, static tables, trees, lists, and layered overlays", plus migration. This matches the anchor-5 pattern of multiple specific concrete actions with comprehensive coverage; there are no gaps that would drop it to 4.

5 / 5

Completeness

Both questions are answered explicitly: the "what" is the full capability list, and the "when" is a concrete trigger clause — "Use when rendering styled strings or pretty terminal output for a TUI or CLI, drawing a bordered box, building a layout from measured blocks, or migrating v1 lipgloss code". This mirrors the anchor-5 example structure exactly; the "when" is neither missing nor only weakly implied.

5 / 5

Trigger Term Quality

Natural user phrases are covered with synonyms: "rendering styled strings", "pretty terminal output", "TUI or CLI", "drawing a bordered box", "building a layout from measured blocks", "migrating v1 lipgloss code", alongside package identifiers ("charm.land/lipgloss/v2", "charmbracelet") that function like file extensions for trigger matching. Coverage is comprehensive rather than merely good, matching anchor 5.

5 / 5

Distinctiveness Conflict Risk

A clear niche is staked out with minimal conflict risk: the skill is pinned to "Lip Gloss v2 (charm.land/lipgloss/v2, charmbracelet)" and explicitly excludes sibling skills — "Not for the event loop (charmed-bubbletea) or interactive widgets (charmed-bubbles)". The explicit negative boundary exceeds the anchor-5 example, which relies on positive triggers alone.

5 / 5

Total

20

/

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.

Reviewed

Table of Contents