CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

programming

Write, debug, review and explain source code following object-oriented best practices, DDD principles, and comprehensive testing standards. Use when writing new code, refactoring, debugging, code review, or explaining programming concepts.

Quality

65%

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 ./dotfiles/shared/.config/claude/forgoty-marketplace/plugins/software-engineering/skills/programming/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%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 well-organized and brief but hollow: it defers all real content to a CODING-RULES.md file that is absent from the bundle, and the remaining sections largely restate the frontmatter description. Beyond 'read the rules file', it offers no concrete examples of rules or their application, and no validation checkpoints.

Suggestions

Ship the referenced CODING-RULES.md (or inline its essential rules) — the body's central reference is a dangling link, so the skill currently delivers none of its promised content.

Replace the directive filler ('STRICTLY follow this rules') with a concrete example of one rule in each severity level so the format and application are actionable before reading the full file.

Cut the redundant intro paragraph and 'When to Use' section, which duplicate the frontmatter description almost verbatim, and add a post-task validation step (e.g., re-check applied rules against severity ordering) to the Quick Start sequence.

DimensionReasoningScore

Conciseness

The intro paragraph ("Master programming principles to build high-quality, maintainable, testable and production-ready software...") and the "When to Use This Skill" section both restate the frontmatter description almost verbatim — redundant padding that could be tightened. Not 4 because two full sections are duplicative; not 2 because the body is short (~50 lines) and doesn't explain concepts Claude already knows.

3 / 5

Actionability

The only executable instruction is "Read [CODING-RULES.md](CODING-RULES.md)"; beyond that the body is exhortation ("STRICTLY follow this rules", "RESPECT rules by severity") with no example rule, format, or application guidance — minimal concrete guidance matching the score-2 anchor. Not 3 because the body contains no partially-executable content at all; not 1 because reading the rules file and the conflict-resolution decision procedure are concrete instructions.

2 / 5

Workflow Clarity

Quick Start lists a readable sequence (read rules → follow by severity → resolve conflicts by severity then existing patterns), but steps 2–3 are vague directives and no validation checkpoints verify rules were applied — the score-3 anchor 'sequence present but checkpoints missing or implicit'. Not 4 because the steps are exhortations rather than defined actions; not 2 because the sequence is coherent and a real conflict-resolution decision rule is specified.

3 / 5

Progressive Disclosure

Scored against the actual bundle structure: the body's single reference, CODING-RULES.md (invoked twice and carrying the skill's entire substance), does not exist in the bundle — no references/ directory and no such file. The clearly-signaled one-level-deep structure is undermined by a dangling reference that leaves the skill undeliverable. Not 3/4 because content cannot be 'appropriately placed' when the referenced payload is missing; not 1 because the body itself is well-sectioned rather than monolithic or nested.

2 / 5

Total

10

/

20

Passed

Description

76%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 well-formed: it names several concrete actions, has an explicit and enumerated 'Use when' clause answering both what and when, and uses natural trigger terms. Its main weakness is breadth — as an unscoped general-programming skill it risks triggering for tasks better served by narrower skills.

Suggestions

Narrow the scope (e.g., to a language, paradigm, or task type like 'object-oriented code review and DDD refactoring') to reduce overlap with dedicated code-review, testing, and language-specific skills.

Add a few natural trigger synonyms such as 'fixing bugs' or 'writing unit tests' to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

Lists four concrete actions ("Write, debug, review and explain source code") with minor coverage gaps, matching the score-4 anchor. Not 5 because the remaining coverage relies on jargon modifiers ("object-oriented best practices, DDD principles") rather than a comprehensive inventory of concrete capabilities.

4 / 5

Completeness

Explicitly answers both what ("Write, debug, review and explain source code following... testing standards") and when ("Use when writing new code, refactoring, debugging, code review, or explaining programming concepts") with five concrete trigger phrases. The 'when' is explicit and enumerated, so it meets the score-5 anchor rather than the score-4 'could be more specific' case.

5 / 5

Trigger Term Quality

"writing new code, refactoring, debugging, code review, explaining programming concepts" are natural phrases users would say — good keyword coverage with a few terms missing. Not 5 because no synonyms or variations (e.g., "fixing bugs", "writing tests", specific languages or file types) are included.

4 / 5

Distinctiveness Conflict Risk

An unscoped 'programming' skill claiming writing, debugging, code review, refactoring, and explanation is very broad with high overlap risk against dedicated code-review, testing, and language-specific skills — the score-2 anchor. Not 3 because no niche constraint (language, domain, or task type) narrows it at all.

2 / 5

Total

15

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

forgoty/dotfiles

Path

dotfiles/shared/.config/claude/forgoty-marketplace/plugins/software-engineering/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.