CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

programming

Applies strict, modern language practice (typed errors, exhaustive match, tests that can fail) for Python, Rust, TypeScript, JavaScript, and Go. Use for work on .py, .rs, .ts, .js, or .go files, and whenever a test or spec file is written, reshaped, reviewed, or deleted: the four-question test authoring gate and the junk-test classes live here.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-sequenced index skill: executable measurement commands, explicit validation checkpoints, and a verified one-level-deep reference bundle with clear jump tables. Its main cost is token weight — the ~330-line body duplicates content across the gate table, jump tables, smells section, and review loop, and pins time-sensitive 2026 version data inline.

Suggestions

Collapse the duplication between the PHASE 0 language-gate table, the per-language jump tables, and the review-loop questions that restate Smells 2-4 — state each rule once and link to its reference file.

Move the time-sensitive 2026 version and library-pin tables (e.g. "golangci-lint v2", "bubbletea v2 RC", "~48%" market share) into the per-language references or a dedicated section, keeping only the decision rule in the body.

Trim the body toward a true index: keep the shared axioms, smells summary, and post-write loop, but delegate the per-language ecosystem/toolchain columns to the already-existing references/<lang>/libraries.md files.

DimensionReasoningScore

Conciseness

The body is directive rather than explanatory (it does not re-teach concepts Claude knows), but it is noticeably redundant: the PHASE 0 language-gate table restates the per-language jump tables, review-loop questions 8-10 restate Smells 2-4, the companion-skills table restates Step 4, and time-sensitive version pins ("2026", "golangci-lint v2", "bubbletea v2 RC", "~48%") are inlined rather than isolated, matching anchor 3 rather than anchor 4's "minor instances".

3 / 5

Actionability

Guidance is fully executable: copy-paste ready LOC measurement (awk command), exact script invocations ("uv run scripts/python/check-no-excuse-rules.py <changed paths>"), per-language CI gate commands, concrete linter flag lists, and a specific four-question test authoring gate, matching anchor 5.

5 / 5

Workflow Clarity

The workflow is clearly sequenced (language gate before any code, shared philosophy, test discipline, then a mandatory post-write loop) with explicit validation checkpoints (the LOC verdict table and the 11-question architectural checklist) and feedback loops (the "test your test" break-restore protocol, validation before commit), matching anchor 5.

5 / 5

Progressive Disclosure

Verified against the actual bundle: every referenced path under references/ exists, references are one level deep, and the "Need → Load" jump tables make navigation easy; however the body inlines sizable cross-language tables despite calling itself an index and duplicates the jump-table content in the PHASE 0 gate table, fitting anchor 4 rather than anchor 5.

4 / 5

Total

17

/

20

Passed

Description

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

A strong description: it explicitly states what the skill does and when to use it, with concrete trigger terms covering file extensions, language names, and test/spec authoring verbs. Its main weakness is that the broad "work on .py/.rs/.ts/.js/.go files" trigger creates some overlap risk with other code-related skills, and a few natural trigger phrases are absent.

DimensionReasoningScore

Specificity

Names several concrete practices — "typed errors, exhaustive match, tests that can fail", "the four-question test authoring gate", "the junk-test classes" — but the umbrella phrasing "Applies strict, modern language practice" leaves coverage gaps (code smells, logging, toolchain rules the skill also governs), matching anchor 4 rather than the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both parts: the "what" is stated up front ("Applies strict, modern language practice (typed errors, exhaustive match, tests that can fail)...") and the "when" carries concrete trigger phrases ("Use for work on .py, .rs, .ts, .js, or .go files, and whenever a test or spec file is written, reshaped, reviewed, or deleted"), matching anchor 5.

5 / 5

Trigger Term Quality

Includes file extensions (".py, .rs, .ts, .js, or .go files"), all five language names, and natural test-related verbs ("written, reshaped, reviewed, or deleted"), but misses common natural phrases like "coding", "refactor", or "fix a bug" and secondary extensions (.pyi, .tsx), so it fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clearly carved (strict modern language practice plus the distinctive "four-question test authoring gate" and "junk-test classes" that "live here"), though the broad trigger "work on .py... files" overlaps with any other development-oriented skill, keeping it at anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 62 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

code-yeongyu/lazycodex

Path

plugins/omo/skills/programming/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.