vibe

Vibe Code Orchestrator (VCO) is a governed runtime entry that freezes requirements, bounds execution, and enforces verification and phase cleanup.

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./SKILL.md

Quality

Content

56%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 actionable and well-sequenced with concrete commands, JSON shapes, and validation checkpoints, but it is verbose and its progressive-disclosure references point to protocol files that are absent from the bundle.

Suggestions

Tighten the repeated "Do not..." prohibition lists and governance prose; consolidate duplicated rules to reduce the ~280-line footprint.

Fix the Protocol Map by either adding the referenced protocols/*.md files to the bundle or repointing the links to existing references/ files.

Move the inlined runtime/stage detail into the referenced protocol files so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The ~280-line body is noticeably verbose: dense governance prose, repeated "Do not..." prohibition lists, and restated rules that could be tightened, even though the embedded commands and JSON carry real content.	2 / 5
Actionability	Provides concrete executable canonical-entry commands (PowerShell and Bash) and a complete host-decision JSON shape with copy-paste-ready structure; only minor gaps from placeholders like <skill_root> and <current user task, verbatim>.	4 / 5
Workflow Clarity	A clear fixed state machine (skeleton_check through phase_cleanup) is sequenced with explicit validation (proof artifacts, verify-before-completion) and a feedback loop (one targeted repair then rerun); minor gaps come from checkpoints being buried in dense prose.	4 / 5
Progressive Disclosure	A well-signaled "Protocol Map" points one level deep to protocols/runtime.md, protocols/think.md, etc., but no protocols/ directory exists in the bundle, so the references are broken; additionally, much detail that belongs in those files is inlined here.	3 / 5
	Total	13 / 20 Passed

Description

51%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 names a clear niche and several concrete governance actions but leans on jargon and omits any explicit "when to use" trigger guidance. Adding a natural-language trigger clause would most improve it.

Suggestions

Add a "Use when..." clause naming natural user triggers (e.g., invoking $vibe or /vibe, or choosing governed requirement/plan/execution closure for a complex task).

Replace governance jargon ("governed runtime entry", "bounds execution") with at least one phrase a user would naturally say.

Include common invocation forms ($vibe, /vibe, the vibe skill) so the description surfaces natural trigger terms.

Dimension	Reasoning	Score
Specificity	Lists several specific actions — "freezes requirements, bounds execution, and enforces verification and phase cleanup" — which are concrete named operations for a governance runtime, with only minor coverage gaps.	4 / 5
Completeness	It clearly states what the skill does but has no "Use when..." clause or equivalent explicit trigger guidance, so the "when" is missing and completeness is capped at 3.	3 / 5
Trigger Term Quality	The recognizable name "Vibe Code Orchestrator (VCO)" is present, but the rest is governance jargon ("governed runtime entry", "bounds execution") with no natural trigger phrases a user would actually say.	2 / 5
Distinctiveness Conflict Risk	The governed-runtime-entry niche is fairly distinct from generic skills, with only minor overlap risk against other orchestration/planning skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: foryourhealth111-pixel/Vibe-Skills
Path: SKILL.md
Commit: ddcaa2a

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.