CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gentleman-bubbletea

Bubbletea TUI patterns for Gentleman.Dots installer. Trigger: When editing Go files in installer/internal/tui/, working on TUI screens, or adding new UI features.

Quality

77%

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 ./skills/gentleman-bubbletea/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.

The body is a tight, actionable pattern library: every critical pattern is shown in concrete Go, the decision tree sequences common changes, and verification commands are included. Only mild redundancy and the absence of an explicit validate/fix loop keep it from the top anchors.

DimensionReasoningScore

Conciseness

Lean and pattern-focused with no concept over-explanation (no "what Bubbletea is" padding). Minor redundancy — Pattern 4's key handler and Example 3's scrollable handler overlap — keeps it below the 'every token earns its place' 5 anchor.

4 / 5

Actionability

Concrete, idiomatic Go code for every pattern plus exact build/test commands with paths. Placeholder names (SomeType, NewFeatureData, "// ...") leave minor gaps versus fully copy-paste-ready code, matching the 4 anchor over 5.

4 / 5

Workflow Clarity

The Decision Tree sequences 'adding a new screen' end-to-end (constant → state → handler → view → title) and the Commands section provides go build/go test verification, but validation is presented as commands rather than explicit validate-then-fix checkpoints. Fits anchor 4, not the feedback-loop 5.

4 / 5

Progressive Disclosure

Well-organized sections with clear headers, and a Resources section pointing to the repo's model/update/view/styles files for depth. The ~200 lines of patterns/examples could partially move to a reference file, so structure is good but not the cleanly split 5.

4 / 5

Total

16

/

20

Passed

Description

68%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 has an explicit, specific trigger clause and is highly distinctive, but the capability statement is thin — it names the domain without enumerating concrete actions. Adding 2-3 verbs describing what the skill provides would lift it into the top tier.

Suggestions

Replace "Bubbletea TUI patterns" with concrete actions, e.g., "Add TUI screens, handle keyboard input and navigation, and manage state and scrolling in the Gentleman.Dots Bubbletea installer."

Include common synonyms users would say — "terminal UI", "keybindings", "Lipgloss styling" — alongside the existing trigger phrases.

State the what explicitly before the trigger: one sentence naming the deliverables (screen constants, Model struct fields, key handlers, view cases) the skill guides.

DimensionReasoningScore

Specificity

Names the domain ("Bubbletea TUI patterns for Gentleman.Dots installer") but states no concrete actions — what the skill actually provides (e.g., adding screens, handling key input, managing state) is only implied by the word "patterns". Closest to the 'names the domain but actions are minimal or generic' anchor, below the 3 anchor which requires 1-2 explicit actions.

2 / 5

Completeness

Both parts present: an explicit "Trigger:" clause answers *when* clearly and specifically, while "Bubbletea TUI patterns for Gentleman.Dots installer" answers *what*, though thinly. Fits the 'both present, one could be more explicit' anchor rather than 5, whose what-clause enumerates concrete capabilities.

4 / 5

Trigger Term Quality

Natural phrases with concrete path triggers — "editing Go files in installer/internal/tui/", "working on TUI screens", "adding new UI features" — that a contributor to this repo would say. A few natural terms are missing (terminal UI, keybindings/navigation, Lipgloss), so not the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche: named project (Gentleman.Dots), named library (Bubbletea), and a specific directory path (installer/internal/tui/). Minimal conflict risk with any other skill; matches the 'clear niche with distinct triggers' anchor.

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Gentleman-Programming/engram

Path

skills/gentleman-bubbletea/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.