CtrlK
BlogDocsLog inGet started
Tessl Logo

vibe-workflow

Select the appropriate planning, implementation, or debugging workflow for an app project.

61

Quality

72%

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 ./.claude/skills/vibe-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 content is a tight, well-structured router that assumes Claude's intelligence and gives concrete, branched guidance with verification emphasis. It earns top marks for conciseness and structure, with only minor gaps in executable specificity and explicit error-recovery loops.

DimensionReasoningScore

Conciseness

The body is lean and directive with no concept re-explanation or padding; every line carries a specific instruction (e.g. "Load only the context needed", "An existing file does not prove that a stage is complete"), assuming Claude's competence throughout.

5 / 5

Actionability

Guidance is concrete and mostly executable, naming specific skills and sequenced actions ("Use `vibe-agents` when creating project instructions, `vibe-build` for a new implementation", "reproduce, diagnose, fix, and verify the failure"), with a minor gap being its dependence on skills that may not be present in the target environment.

4 / 5

Workflow Clarity

Branching scenarios (New product / Existing product / Broken behavior / Handoff) give a clear sequence with verification checkpoints ("verify the failure", "distinguish actual results from unperformed checks"), but explicit error-recovery feedback loops and checklists for the riskier branches are not fully spelled out.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references and is well-organized into clearly signaled scenario sections, satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

18

/

20

Passed

Description

58%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 states a clear purpose and names concrete workflow categories, but lacks an explicit "Use when..." trigger clause and natural trigger synonyms, which caps completeness and trigger-term quality at the midpoint. It is reasonably distinct from other skills but would benefit from explicit usage triggers.

Suggestions

Add an explicit "Use when..." clause naming concrete trigger phrases, e.g. "Use when starting, changing, or fixing an app project and unsure which workflow to follow."

Include natural trigger synonyms and variations users would actually say (e.g. "new app", "add a feature", "fix a bug", "ship an app") to improve trigger-term coverage.

Tighten the 'when' by distinguishing the three branches explicitly (planning a new app vs. changing an existing app vs. debugging broken behavior) to lift completeness above 3.

DimensionReasoningScore

Specificity

Names the app-project domain and three concrete workflow types ("planning, implementation, or debugging workflow"), giving several specific action areas with only minor coverage gaps, but stops short of comprehensive enumeration.

4 / 5

Completeness

The "what" is clear (select the appropriate workflow), but the "when" is only weakly implied by "for an app project"; per rubric guidance the missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords like "app project", "planning", "implementation", and "debugging" are present, but common natural variations and synonyms are missing and no explicit "Use when..." trigger phrase is supplied.

3 / 5

Distinctiveness Conflict Risk

The workflow-routing niche for app projects is mostly distinct from generic build or debug skills, with only minor overlap risk against closely related planning/build skills.

4 / 5

Total

14

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
KhazP/vibe-coding-prompt-template
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.