vibe

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

Quality

56%

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

77%

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

The body is operationally strong: concrete command/JSON templates, an explicit state machine, and rigorous validation and re-entry feedback loops. Its weaknesses are verbosity from repetitive governance prohibitions and progressive-disclosure references that do not resolve in the actual bundle.

Suggestions

Consolidate the many repetitive 'Do not...' prohibitions into a compact negative-rules list to reduce token weight while preserving the constraints.

Ensure the referenced protocols/*.md and core/skill-contracts/v1/vibe.json files actually exist in the bundle, or repoint the Protocol Map to the real reference paths.

Move the detailed stage/cleanup governance currently inline into protocols/runtime.md so the host-facing SOP stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The ~245-line body is heavily padded with repetitive 'Do not...' / 'must not...' governance prose, though it avoids basic-concept filler; it could be tightened substantially without losing operational content.	2 / 3
Actionability	It provides concrete PowerShell and bash canonical-entry command shapes plus complete host-decision and revision JSON templates that are copy-paste ready, despite using appropriate placeholders.	3 / 3
Workflow Clarity	A fixed 6-stage state machine, three progressive stops, explicit proof-artifact validation gates, and rejection feedback ('correct the same module-execution.json and reuse the same return command') give a clearly sequenced workflow with checkpoints.	3 / 3
Progressive Disclosure	A 'Protocol Map' signals one-level-deep references to protocols/*.md, but those referenced files (and core/skill-contracts/v1/vibe.json) are absent from the provided bundle, and the body is still long and inline-heavy rather than truly split out.	2 / 3
	Total	10 / 12 Passed

Description

35%

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 conveys a clear niche and several named actions but is written in internal jargon with no natural trigger terms and no 'when to use' guidance. It reads more like an internal contract label than a user-invocable skill description.

Suggestions

Add a 'Use when...' clause stating the natural situations in which a host or user would invoke this skill (e.g., complex multi-phase tasks needing governed requirement/plan/execution closure).

Reword governance jargon ('governed runtime entry', 'phase cleanup') into terms a user would actually say, or pair them with plain-language equivalents.

Lead with the concrete outcome the skill produces before the abstract governance verbs so the 'what' is concrete rather than abstract.

Dimension	Reasoning	Score
Specificity	It names a domain ('governed runtime entry') and several actions ('freezes requirements, bounds execution, and enforces verification and phase cleanup'), but these are abstract governance verbs rather than concrete user-facing actions like 'extract text' or 'fill forms'.	2 / 3
Completeness	It answers 'what' but provides no 'Use when...' or equivalent trigger guidance for 'when', so per the judging guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	No natural user-facing keywords appear; the description is pure jargon ('governed runtime entry', 'phase cleanup'), paralleling 'Handles document object model manipulation'.	1 / 3
Distinctiveness Conflict Risk	It occupies a niche (VCO governed runtime) but lacks distinct trigger terms and leans on jargon, so it could still overlap with adjacent workflow skills.	2 / 3
	Total	7 / 12 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: f627ab5

Reviewed: 2 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.