CtrlK
BlogDocsLog inGet started
Tessl Logo

programming

MUST USE for ANY work on .py .pyi .rs .ts .tsx .mts .cts .go files. One philosophy: strict types, modern stacks (Pydantic v2 / serde+thiserror / Zod / gin+sqlc+pgx+slog), modern toolchains (uv+basedpyright+ruff / cargo+clippy+miri / Bun+Biome+tsc / gofumpt+golangci-lint v2+nilaway+go-race), parse-don't-validate, exhaustive match, typed errors, no any/unwrap/panic, 250 LOC ceiling, TDD, consumer-routed logging. Routes to references/{python,rust,typescript,rust-ub,go}/ + references/logging.md. Triggers: write/edit Python/Rust/TypeScript/Go code, new project, gin server, bubbletea TUI, CJK IME, connect-go RPC, sqlc pgx, branded ids, exhaustive match, unsafe Rust, miri, oversized file, refactor, TDD, e2e test, logging, log levels, structured logging, observability, arena, allocator, bumpalo, const fn, const generics, comptime, zero-alloc, bitfield, repr, scopeguard, errdefer, Zig-like, zerocopy, packed struct.

71

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.

A well-architected index skill: strongly actionable, with clearly sequenced workflows and validation checkpoints, and excellent progressive disclosure through a real, well-organized reference bundle. Its one weak spot is conciseness — the body carries lengthy sermons on TDD and prompt-testing philosophy that Claude already knows and that sit oddly in a self-declared index.

Suggestions

Move the generic TDD discipline (red/green/refactor, Given/When/Then, mock-priority ladder) and the 'prompt tests: NEVER assert prose' sermon into a dedicated reference file (e.g. references/testing.md), keeping only the cross-language test-pyramid sizing table and the routing pointer inline.

Trim the seven-rung 'best code is the code never written' ladder and the 'lazy senior engineer' framing to a one-line axiom; the detailed ladder reads as conceptual padding Claude does not need.

Re-read the body against its own 250-LOC ceiling ethos — at ~394 lines it exceeds the limit it enforces; splitting the TDD and code-smells exposition into references would bring the index closer to its stated size discipline.

DimensionReasoningScore

Conciseness

Dense and table-heavy where it counts (ecosystem/toolchain/iron-list tables are token-efficient and project-specific), but the ~394-line body over-explains concepts Claude already knows — the seven-rung 'best code is the code never written' ladder, the full TDD/Given-When-Then/mock-hierarchy sermon, and the long 'prompt tests: NEVER assert prose' section — which is padding for a file that declares itself 'an index'; matches 'mostly efficient but includes some unnecessary explanation'.

2 / 3

Actionability

Highly concrete and copy-paste ready: the awk LOC one-liner, per-language check-script invocations ('uv run scripts/python/check-no-excuse-rules.py', 'cargo +nightly miri test'), exact CI-gate commands, named libraries with versions, and Need→Load routing tables giving exact reference paths; matches the 'fully executable code/commands; copy-paste ready' anchor.

3 / 3

Workflow Clarity

Multi-step processes are clearly sequenced with validation checkpoints: PHASE 0 gate (identify → STOP and read references → apply philosophy), red→green→refactor TDD with 'confirm it fails for the right reason', and a four-step post-write loop whose Step 2 LOC verdict table and Step 3 11-item self-review checklist act as explicit validation with a 'fix before declaring done' feedback loop.

3 / 3

Progressive Disclosure

Genuinely an index: SKILL.md routes via per-language jump tables to references/{python,rust,typescript,go,rust-ub}/README.md plus on-demand files, with code-smells.md and logging.md as cross-cutting refs — all referenced paths verified to exist and clearly signaled one level deep; inline shared-overview content (philosophy, ecosystem tables) is appropriate for the index rather than mis-placed detail.

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.

A dense, highly specific description that clearly states both capability and an explicit trigger list with strong natural-keyword coverage and a distinct niche. Its only real weakness is voice: it leads with an imperative 'MUST USE' directive rather than third-person phrasing, which costs it on specificity.

Suggestions

Rewrite the opening in third-person declarative voice (e.g. 'Applies strict-typed, modern-stack discipline to Python/Rust/TypeScript/Go code') instead of the imperative 'MUST USE for ANY work on ...' to satisfy the third-person requirement.

Lead with two or three concrete actions the skill performs (e.g. 'writes and edits type-strict code, scaffolds new projects, and routes to per-language references') so the capability reads as actions rather than a constraint list.

DimensionReasoningScore

Specificity

Packed with concrete specifics (file extensions, named stacks like 'Pydantic v2 / serde+thiserror / Zod / gin+sqlc+pgx+slog', the '250 LOC ceiling'), but the actual enumerated actions are thin ('write/edit ... code', 'new project', 'Routes to references') and it is not a clean third-person action list; base 3 docked to 2 because 'MUST USE for ANY work on ...' is imperative/second-person voice, which the rubric penalizes by reducing specificity by 1.

2 / 3

Completeness

Explicitly answers what ('One philosophy: strict types, modern stacks ... Routes to references/{...}') and when via a dedicated 'Triggers:' clause plus 'MUST USE for ANY work on [extensions]', satisfying the anchor requiring both what AND when with explicit triggers.

3 / 3

Trigger Term Quality

The explicit 'Triggers:' list gives broad coverage of natural terms a user would say — 'write/edit Python/Rust/TypeScript/Go code', 'new project', 'refactor', 'TDD', 'e2e test', 'logging', 'structured logging', 'observability', 'oversized file' — alongside file-extension routing; matches the 'good coverage of natural terms' anchor.

3 / 3

Distinctiveness Conflict Risk

Clear niche — strict-typed 2026-modern-stack programming across four named languages — with distinctive file-extension and stack-specific triggers (gin server, bubbletea TUI, CJK IME, connect-go RPC, sqlc pgx, unsafe Rust, miri) unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

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

Warning

Total

15

/

16

Passed

Repository
code-yeongyu/lazycodex
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.