Load language-specific coding standards before editing Go, Rust, Python, or Tailwind CSS files
79
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 1.00xAgent success when using this skill
Validation for skill structure
Go language detection and standards application
Uses slog for logging
100%
100%
Structured slog calls
100%
100%
Error wrapping with %w
100%
100%
context.Context first param
100%
100%
Godoc on exported symbols
100%
100%
Lowercase error messages
100%
100%
No discarded errors
100%
100%
Standards noted in log
100%
100%
slog imported in metrics handler
100%
100%
Without context: $0.2862 · 1m 54s · 19 turns · 23 in / 4,570 out tokens
With context: $0.5221 · 2m 10s · 27 turns · 63 in / 7,269 out tokens
Python language detection and standards application
Type annotations present
100%
100%
f-strings used
100%
100%
No .format() usage
100%
100%
pathlib.Path for file ops
100%
100%
No os.path usage
100%
100%
argparse for CLI
100%
100%
argparse help strings
100%
100%
main guard present
100%
100%
Optional type used where needed
100%
100%
Without context: $0.3260 · 1m 16s · 20 turns · 27 in / 4,387 out tokens
With context: $0.3922 · 1m 24s · 21 turns · 26 in / 4,923 out tokens
Tailwind CSS detection and standards application in TSX
clsx for class composition
100%
100%
No manual class string building
100%
100%
gap-* for flex spacing
100%
100%
Responsive class prefixes present
100%
100%
focus-visible ring on dismiss button
100%
100%
Semantic button element
100%
100%
Mobile-first ordering
100%
100%
Without context: $0.3362 · 1m 29s · 21 turns · 27 in / 4,812 out tokens
With context: $0.4296 · 1m 29s · 26 turns · 32 in / 4,787 out tokens
Table of Contents
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.