CtrlK
BlogDocsLog inGet started
Tessl Logo

bencium-code-conventions

Bence's code style, tech stack, and workflow conventions

55

Quality

61%

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 ./bencium-code-conventions/skills/bencium-code-conventions/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 a tight, well-structured conventions reference that names specific technologies and patterns with clear directives and a sequenced workflow including validation checkpoints. It is highly token-efficient and actionable, with only minor room to add executable examples or split detail into reference files.

DimensionReasoningScore

Conciseness

The body is a lean bullet list of directives with no padding or explanations of concepts Claude already knows; every line states a concrete convention.

5 / 5

Actionability

Guidance is concrete and specific with named tools (Zustand, Zod, sonner, @phosphor-icons/react) and inline examples ("const toggle = () =>", "isLoading"), though it stops short of full executable code blocks.

4 / 5

Workflow Clarity

The Development Workflow lays out a clear Explore → Plan → Code → Commit sequence with checkpoints (typecheck after changes, run tests before commit) and the TDD loop iterates until the suite passes.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections with no need for external references, but the body exceeds 50 lines and offers no progressive split, so it sits just below the top anchor.

4 / 5

Total

17

/

20

Passed

Description

41%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 concise and third-person but only states the topic domains without concrete actions or an inline trigger clause, leaving the "when" to a separate frontmatter field. It is distinct thanks to the personal naming yet generic in its wording.

Suggestions

Fold the trigger into the description, e.g. "Applies Bence's code style, tech stack, and workflow conventions. Use when writing code or setting up projects for Bence."

Replace topic nouns with concrete verbs (e.g. "Formats code, selects the tech stack, and enforces workflow steps per Bence's conventions") to lift specificity.

Add natural synonyms a user would say ("Bence's preferences", "coding standards for Bence") to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domains ("code style, tech stack, and workflow conventions") but lists no concrete actions, matching the anchor that names the domain with minimal or generic actions.

2 / 5

Completeness

It gives a clear "what" (Bence's conventions) but no "when" clause in the description field, so per the rubric a missing Use-when clause caps completeness at 3.

3 / 5

Trigger Term Quality

Only generic keywords ("code style", "tech stack", "workflow conventions") appear; the natural trigger phrase a user would say ("writing code for Bence") lives in when_to_use, not the description.

2 / 5

Distinctiveness Conflict Risk

Binding the skill to a named person ("Bence") gives it a clear niche with only minor overlap risk against general coding-convention skills; it is not a 5 because no concrete triggers are stated.

4 / 5

Total

11

/

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
bencium/bencium-marketplace
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.