CtrlK
BlogDocsLog inGet started
Tessl Logo

vibe-coding

Transform an AI agent into a tasteful, disciplined development partner. Not just a code generator, but a collaborator with professional standards, transparent decision-making, and craftsmanship. Use for any development task: building features, fixing bugs, designing systems, refactoring. The human provides vision and decisions. The agent provides execution with taste and discipline.

53

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 ./packages/builtin-skills/skills/vibe-coding/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

47%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill has strong, well-sequenced workflows with explicit confirmation checkpoints and a decent reference index, but it is far too verbose and padded for a meta-instruction skill, re-teaching basics Claude already knows.

Suggestions

Cut the motivational mantras, the duplicated ASCII quick-reference box, and the re-explanation of basic practices (read-before-edit, follow conventions, test-before-refactor) to respect the token budget.

Move the large communication templates (Discovery, Design, Execution, RAPID, Code Review) into reference files and keep SKILL.md as a lean overview, then actually link the orphaned phases/ and assets/templates/ bundles.

Replace abstract mindset directives ('Write code you'd be proud to show') with concrete, checkable criteria where possible.

DimensionReasoningScore

Conciseness

The ~727-line body is heavily padded with motivational mantras ('Human provides the Vibe. Agent provides the Code.', 'Every interaction either builds or erodes trust. There is no neutral.') and re-explains basic engineering practices Claude already knows (read code before editing, follow conventions, never refactor without tests), with a duplicated ASCII quick-reference box.

1 / 3

Actionability

It provides concrete, copy-paste-ready communication templates (Discovery Questions, Design Proposal Format, RAPID method, Code Review table), but much of the guidance is abstract mindset ('Understand deeply before acting', 'Write code you'd be proud to show') and the templates are placeholder scaffolding rather than fully specified execution.

2 / 3

Workflow Clarity

Discovery -> Design -> Execution -> Debug modes are clearly sequenced with explicit validation checkpoints ('MUST get human confirmation before proceeding', 'Verify atomically', and the RAPID reproduce-to-deploy sequence with regression verification), matching the clear-sequence-with-checkpoints anchor.

3 / 3

Progressive Disclosure

References are well-organized into domains/patterns/scenarios with a one-level-deep index and 'MANDATORY LOAD' signals, but the SKILL.md body itself is a monolith with large inline templates and several bundle files (references/phases/*, assets/templates/*) are never linked from the body.

2 / 3

Total

8

/

12

Passed

Description

75%

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 has an explicit 'Use for' trigger with natural terms and clearly answers both what and when, but it is padded with marketing language and its 'any development task' scope makes it almost indistinguishable from other development skills.

Suggestions

Narrow the trigger scope or add a distinctive qualifier so it does not collide with every other development-related skill.

Trim the marketing phrasing ('tasteful, disciplined development partner', 'craftsmanship') in favor of concrete behaviors the skill enforces.

Lead with the concrete actions (features, bugs, design, refactoring) rather than the mindset-transformation framing.

DimensionReasoningScore

Specificity

It lists concrete task types ('building features, fixing bugs, designing systems, refactoring') but the dominant framing is abstract and mindset-oriented ('tasteful, disciplined development partner', 'craftsmanship', 'transparent decision-making'), so it names a domain and some actions without being comprehensive.

2 / 3

Completeness

It answers both what ('Transform an AI agent into a ... development partner') and when via an explicit 'Use for ...' trigger clause, satisfying the what-and-when requirement.

3 / 3

Trigger Term Quality

The 'Use for any development task: building features, fixing bugs, designing systems, refactoring' clause uses natural terms a user would actually say when they need this skill, with reasonable coverage.

3 / 3

Distinctiveness Conflict Risk

'Use for any development task' is maximally broad and would overlap with feature-specific, bug-fix, refactoring, and design skills, matching the 'very generic; would conflict with many skills' anchor.

1 / 3

Total

9

/

12

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (727 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

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

Warning

Total

14

/

16

Passed

Repository
shareAI-lab/Kode-CLI
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.