CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vibers-code-review

Human review workflow for AI-generated GitHub projects with spec-based feedback, security review, and follow-up PRs from the Vibers service.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/vibers-code-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 tightly written, safety-gated instruction skill that is efficient with tokens and well structured, with a genuinely useful concrete example of synthetic test notes. Its weaknesses are the high-level (non-executable) guidance for the authorized evaluation path, an implicit rather than explicit workflow with no validation checkpoints, and a sole external reference that cannot be verified to exist.

Suggestions

Turn the evaluation-preparation path into a numbered checklist with explicit checkpoints (e.g., '1. Confirm the named service, repository, and data in the request; 2. Draft minimum permission list; 3. Pin and verify the workflow ref; 4. Owner approves before any grant').

Specify what 'minimum proposed permissions' and 'verified dependency' mean concretely (e.g., which GitHub permissions, how to pin and audit the action ref) so the guidance is executable.

Fix or inline the broken reference to ../code-review-excellence/SKILL.md — either make the path resolve in the bundle or state the local-review instructions directly.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no concepts are over-explained, and the example fixture block is compact and load-bearing. It does not reach 5 because the authorization caveat is repeated across sections ('does not authorize the Vibers integration', 'These have not been approved here', 'does not itself authorize access grants or publication') and could be consolidated into one statement. It is clearly above anchor 3, which expects noticeably more unnecessary explanation.

4 / 5

Actionability

There is concrete guidance in places — a copy-paste-ready synthetic test-notes example, explicit prohibitions, and a pointer to a local review skill — but the proposed activation path stays high-level ('prepare the minimum proposed permissions', 'verify the current service contract and dependency provenance') without the specific steps or artifacts needed to execute it. This matches anchor 3's 'concrete guidance but incomplete; missing key details' better than anchor 4's 'mostly executable guidance'.

3 / 5

Workflow Clarity

A sequence is present but implicit and spread across prose: confirm the explicit request and its scope, prepare a proposal with minimum permissions and a pinned workflow, verify contract and provenance, test with synthetic fixtures, record what ran. There are no explicit checkpoints or validation steps for the evaluation workflow (e.g., what counts as a verified dependency), fitting anchor 3's 'sequence present but checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

The 34-line body is well organized into clear sections (status, when to consider it, synthetic test instructions) with a clearly signaled one-level reference to a sibling skill for local review. It misses anchor 5 because that single reference ('../code-review-excellence/SKILL.md') points outside the bundle and does not resolve in the provided files, leaving navigation to the main alternative path unverified.

4 / 5

Total

14

/

20

Passed

Description

55%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 communicates a clear, fairly specific capability set tied to a named external service, written in third person without fluff. Its main weaknesses are the complete absence of any 'when to use' trigger guidance (capping completeness at 3) and missing natural trigger synonyms such as 'pull request' or 'code review' as literal phrases.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user explicitly requests Vibers external review for an AI-generated GitHub project, or mentions Vibers by name.'

Include natural trigger synonyms users would actually say — 'code review', 'pull request', 'review AI-generated code' — so the skill matches real phrasings.

Clarify what the skill does relative to local review (e.g. 'Escalates to paid human reviewers...') to reduce overlap with generic code-review skills.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "spec-based feedback, security review, and follow-up PRs" — grounded in a named domain ("AI-generated GitHub projects"), with only minor gaps such as what the review deliverable looks like. It falls short of the comprehensive anchor 5 because coverage of the workflow's actions is not complete (e.g., collaborator access, spec publication, and review-time purchase from the body are absent).

4 / 5

Completeness

The 'what' is clearly stated (human review workflow with spec-based feedback, security review, follow-up PRs from Vibers), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It does not fit anchor 2 because the 'what' is concrete rather than vague, and cannot reach 4 without any 'when' element.

3 / 5

Trigger Term Quality

It contains some natural keywords users would say ("code review" implied via "Human review workflow", "security review", "PRs", "GitHub"), but misses common variations and synonyms like "pull request", "review my code", or "AI-generated code". It is above anchor 2 (which expects only one or two generic keywords) but below anchor 4 because several natural phrasings are missing.

3 / 5

Distinctiveness Conflict Risk

Naming the "Vibers service" and the niche of "AI-generated GitHub projects" gives it a distinguishable identity, but the action terms ("review", "security review", "PRs") overlap heavily with generic code-review skills, and without trigger guidance it could fire on ordinary review requests. It is more specific than anchor 2 ('very broad; high overlap risk with many similar skills') but does not reach anchor 4's 'minor overlap risk with closely related skills'.

3 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/vibers-code-review/SKILL.md

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.