CtrlK
BlogDocsLog inGet started
Tessl Logo

pobuca-connect

Pobuca Connect integration. Manage Organizations, Leads, Deals, Projects, Pipelines, Users and more. Use when the user wants to interact with Pobuca Connect data.

63

Quality

75%

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/pobuca-connect/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, highly actionable CLI integration guide with executable commands and a clear state-machine workflow. Its main weakness is conciseness, due to removable marketing/explanatory prose, and minor workflow labeling gaps.

Suggestions

Trim the introductory marketing paragraph ('Pobuca Connect is a contact management platform designed for businesses...') and the 'so you can focus on the integration logic rather than auth plumbing' aside — Claude already understands integration/auth context.

Fix the dangling workflow labels: label 'Step 2' explicitly or remove 'skip to Step 2' references, and renumber '1b' under a consistent scheme so the connect→ready flow is unambiguous.

Consider moving the proxy flags table and Best practices section into a reference file to keep SKILL.md a lean overview, raising token efficiency.

DimensionReasoningScore

Conciseness

Mostly efficient with code blocks and a flag table, but it retains unnecessary exposition Claude could infer, such as the marketing-style Pobuca Connect paragraph and 'so you can focus on the integration logic rather than auth plumbing'.

3 / 5

Actionability

It provides fully executable, copy-paste-ready commands for the common cases (install, login, connection ensure, polling, action run, proxy) plus a concrete flags table.

5 / 5

Workflow Clarity

The connect→poll→search→run→proxy sequence has explicit state-machine checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and re-poll feedback, but 'skip to Step 2' references an unlabeled Step 2 and the '1b' numbering is unanchored.

4 / 5

Progressive Disclosure

No bundle files exist, but the single file is well-organized with clear section headers and no nested references; at ~140 lines some sections (proxy flags, best practices) could live in separate files but placement is reasonable.

4 / 5

Total

16

/

20

Passed

Description

75%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 is specific, third-person, and provides both a clear 'what' and an explicit 'when' trigger, fitting a solid Level 4 across dimensions. It stops short of Level 5 mainly due to the generic 'and more', a single trigger phrase, and the absence of richer synonym coverage.

DimensionReasoningScore

Specificity

It lists several concrete objects/actions ('Manage Organizations, Leads, Deals, Projects, Pipelines, Users') rather than vague language, though the trailing 'and more' leaves a minor coverage gap.

4 / 5

Completeness

It answers 'what' (manage the listed Pobuca Connect entities) and includes an explicit 'when' ('Use when the user wants to interact with Pobuca Connect data'), though the when-clause could name more concrete trigger phrases.

4 / 5

Trigger Term Quality

Good keyword coverage with concrete domain terms (Organizations, Leads, Deals, Pipelines) plus 'Pobuca Connect', but it relies on a single trigger phrase and lacks synonyms or file extensions.

4 / 5

Distinctiveness Conflict Risk

It targets a clearly named niche (Pobuca Connect) with distinct triggers, carrying only minor overlap risk against other generic CRM/contact skills.

4 / 5

Total

16

/

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.