Name: verbolia
Rating: 50.4 (1 reviews)
Author: membranedev

verbolia

Verbolia integration. Manage data, records, and automate workflows. Use when the user wants to interact with Verbolia data.

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/verbolia/SKILL.md

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 content is a solid, command-heavy integration guide with executable examples and a reasonable connection workflow, but it lacks validation checkpoints around action execution and carries some minor redundancy and filler. It is actionable and well-structured without being exhaustive.

Suggestions

Add explicit validation/verification steps before running actions and after proxy requests (e.g., confirm the returned state/output before proceeding) to support the destructive/batch feedback-loop requirement.

Fix the broken step references: the body mentions 'Step 2' but no Step 1/Step 2 headers exist; renumber the connect-and-wait flow consistently.

Trim filler lines ('Use action names and parameters as needed.', the auth-plumbing aside) and merge the overlapping 'Searching for actions' and 'Popular actions' sections.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and lean, but includes some unnecessary explanation such as 'so you can focus on the integration logic rather than auth plumbing', an unexplained hierarchy listing, and filler like 'Use action names and parameters as needed.' This matches the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides concrete, executable commands for install, login, connection, action search/run, and proxy requests plus a flag table. Guidance is mostly copy-paste ready with only minor gaps (placeholder substitution), matching the 4-anchor; it is short of the fully-covered 5-anchor.	4 / 5
Workflow Clarity	The connect-poll-run sequence is present with a connection-state feedback loop, but there are no validation/verification checkpoints before or after running actions or proxy requests, and 'Step 2' is referenced without a matching 'Step 1/Step 2' structure. Per the rubric, missing validation for potentially destructive action execution caps this at 3.	3 / 5
Progressive Disclosure	With no bundle files, all content lives in one well-sectioned SKILL.md (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices), which is appropriate for a sub-150-line skill. Minor organization gaps (the 'Popular actions' section near-duplicates 'Searching for actions') keep it at the 4-anchor rather than 5.	4 / 5
	Total	14 / 20 Passed

Description

50%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 correctly pairs a 'what' with a 'Use when' trigger and leverages a distinct brand name, but its capability list is generic and its trigger vocabulary is thin. It is functional but not comprehensive or sharply specific.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Verbolia capabilities (e.g., manage SEO content projects, languages, translations, and automate publishing workflows).

Expand the 'Use when' clause with natural trigger phrases and synonyms a user would say, not just 'interact with Verbolia data'.

Add specific nouns users mention (e.g., Verbolia projects, translations, SEO content) to strengthen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the Verbolia domain but its actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete API capabilities. It fits the 'names the domain but actions are minimal or generic' anchor and falls below the 3-anchor where 1-2 concrete actions appear.	2 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Verbolia data'). The 'when' is present and explicit but generic, matching the 4-anchor; it is not the concrete multi-trigger phrasing of the 5-anchor.	4 / 5
Trigger Term Quality	Only the brand 'Verbolia' and 'data' appear as trigger terms, with no synonyms, file extensions, or common user phrasings. This matches the 'one or two generic keywords; missing the natural phrases users say' anchor better than the 3-anchor which expects relevant keyword variations.	2 / 5
Distinctiveness Conflict Risk	The Verbolia brand gives it a clear niche with minimal conflict risk, but the surrounding generic actions ('manage data, records, automate workflows') keep it from the fully distinct 5-anchor. It sits at 'mostly distinct; minor overlap risk with closely related skills'.	4 / 5
	Total	12 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/verbolia/SKILL.md
Commit: f484c82

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