CtrlK
BlogDocsLog inGet started
Tessl Logo

vectera

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

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/vectera/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 delivers highly actionable, executable CLI guidance with a well-sequenced connection workflow that includes genuine validation feedback loops. It is slightly held back by minor editorial verbosity and light section redundancy in an otherwise well-structured single file.

DimensionReasoningScore

Conciseness

The body is mostly efficient commands and tables with a few editorial asides ("so you can focus on the integration logic rather than auth plumbing") that could be trimmed, fitting the efficient-with-minor-over-explanation anchor.

4 / 5

Actionability

Copy-paste-ready commands populate every workflow (login, connection ensure, action list/run, request proxy) plus a flag table, fully covering the common cases the user would hit.

5 / 5

Workflow Clarity

The connection flow is a clear sequence with an explicit poll -> state-check -> handle clientAction -> re-poll feedback loop, including error states (CONFIGURATION_ERROR, SETUP_FAILED), matching the anchor for clear sequencing with validation and error recovery.

5 / 5

Progressive Disclosure

The single-file skill is well organized into clear sections with no nested references, but at ~140 lines it exceeds the simple-skill threshold and has minor redundancy between "Searching for actions" and "Popular actions", fitting the good-structure-with-minor-gaps anchor.

4 / 5

Total

18

/

20

Passed

Description

66%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 includes both a capability statement and an explicit use-trigger tied to a distinct vendor, which is strong on distinctiveness and completeness. It is held back by generic action verbs and limited natural-term coverage.

Suggestions

Replace generic verbs ("manage data, records, and automate workflows") with concrete Vectera capabilities such as scheduling meetings, managing contacts, and handling subscriptions.

Add natural trigger synonyms a user might say, e.g. "Use when the user mentions Vectera meetings, video calls, or client scheduling."

Tighten the "what" so it lists specific record types the integration acts on rather than the abstract word "data".

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Vectera domain and a few actions, but the actions are generic rather than concrete, matching the anchor for naming the domain with limited specific actions.

3 / 5

Completeness

Both a "what" (manage data, records, automate workflows) and an explicit "when" (Use when the user wants to interact with Vectera data) are present, though the "what" is somewhat vague, fitting the both-present-but-could-be-sharper anchor.

4 / 5

Trigger Term Quality

"Vectera" and the "Use when the user wants to interact with Vectera data" clause provide a relevant natural term, but synonyms and common variations are missing, so coverage is partial rather than comprehensive.

3 / 5

Distinctiveness Conflict Risk

Naming a specific vendor (Vectera) creates a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

15

/

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.

Validation15 / 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
membranedev/application-skills
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.