CtrlK
BlogDocsLog inGet started
Tessl Logo

capturing-tui-visual-proof

Captures reviewable before-and-after visual proof from the real Letta Code Ink TUI. Use when a Letta Code PR changes interactive CLI rendering or behavior and needs terminal screenshots or GIFs in its PR body.

72

Quality

88%

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

88%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 highly actionable, well-sequenced procedure with strong validation feedback loops and copy-paste-ready artifacts. Its only weakness is minor conciseness trim potential and the absence of any progressive-disclosure file split, which is largely appropriate for this self-contained workflow.

DimensionReasoningScore

Conciseness

The body is largely lean and direct with code blocks and minimal concept re-explanation, but contains some interspersed rationale prose (e.g. the symlinked node_modules and --model warnings) that could be trimmed slightly.

4 / 5

Actionability

It provides fully executable, copy-paste-ready bash commands, a complete VHS tape template, ffmpeg frame extraction, and a markdown embed table, with placeholders explicitly flagged for replacement.

5 / 5

Workflow Clarity

The process is clearly sequenced across named sections with explicit validation checkpoints: dry-run before recording, "vhs validate", an "Inspect Every Recording" verification checklist, and confirming embedded URLs resolve after publishing.

5 / 5

Progressive Disclosure

No bundle files exist and the single-file workflow is well-organized with clear section headers; content is appropriately inline since there is no large reference material to split, though it lacks the one-level-deep reference structure the top anchor rewards.

4 / 5

Total

18

/

20

Passed

Description

87%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 is strong: third-person, concrete, and explicit about both what it does and when to use it, with a clearly distinct niche. Minor keyword synonym coverage keeps trigger_term_quality and specificity at 4 rather than 5.

DimensionReasoningScore

Specificity

"Captures reviewable before-and-after visual proof from the real Letta Code Ink TUI" and "terminal screenshots or GIFs" name the domain plus several concrete actions, with only minor coverage gaps versus a fully comprehensive list.

4 / 5

Completeness

It explicitly states what ("Captures reviewable before-and-after visual proof from the real Letta Code Ink TUI") and when ("Use when a Letta Code PR changes interactive CLI rendering or behavior...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"Use when a Letta Code PR changes interactive CLI rendering or behavior and needs terminal screenshots or GIFs" provides good natural keyword coverage (PR, CLI rendering, terminal screenshots, GIFs), missing only a few synonyms or common variations.

4 / 5

Distinctiveness Conflict Risk

The niche is highly specific (Letta Code Ink TUI visual proof for PRs) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
letta-ai/letta-code
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.