Name: lob
Rating: 59.2 (1 reviews)
Author: membranedev

lob

Lob integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Lob data.

Quality

68%

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/lob/SKILL.md

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 strong, actionable CLI integration guide with executable commands, a well-sequenced connection lifecycle including state-based validation loops, and clean organization. Its main weaknesses are minor over-explanation, an inconsistent step numbering scheme, and a generic placeholder where a worked end-to-end example would help.

Suggestions

Fix the step numbering: the flow references 'Step 2' but no 'Step 2' heading exists and a '1b' subsection appears — relabel into a consistent Step 1 / Step 2 / Step 3 sequence.

Add one fully-worked end-to-end example (connect → search actions → run one) with a concrete CONNECTION_ID and a real intent so Claude can follow it without guesswork.

Trim inferable framing like 'so you can focus on the integration logic rather than auth plumbing' and reduce the proxy flags table to only the non-obvious flags to save tokens.

Dimension	Reasoning	Score
Conciseness	Mostly lean with copy-paste commands and minimal preamble, but includes some inferable framing ('so you can focus on the integration logic rather than auth plumbing') and a flags table that echoes CLI help, fitting anchor 4 with minor trim opportunities.	4 / 5
Actionability	Provides executable bash for install, login, connection ensure/get, action list/run, and proxy requests plus a flags table and input-schema explanation; minor gaps (generic CONNECTION_ID placeholder, no fully worked end-to-end example) keep it at anchor 4.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, but inconsistent step numbering ('1b', a referenced 'Step 2' with no matching heading) introduces minor gaps, fitting anchor 4.	4 / 5
Progressive Disclosure	No bundle files exist, so scored on structure: a single self-contained file with clear section headers and only a one-level external docs link, well-organized but longer than a pure overview, fitting anchor 4.	4 / 5
	Total	16 / 20 Passed

Description

62%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 solid: it names a distinct integration, lists concrete entities, and includes an explicit 'Use when' trigger. Weaknesses are the generic 'Manage'/'and more' phrasing and trigger terms that underuse the natural Lob domain vocabulary (direct mail, postcards, address verification).

Suggestions

Replace generic 'Manage' with specific verbs (e.g., 'Send postcards and letters, verify addresses, manage billing groups') so capabilities read as concrete actions.

Expand the 'when' clause with natural trigger phrases users actually say, e.g. 'Use when the user wants to send direct mail, verify addresses, or automate postcards/letters via Lob.'

Drop the open-ended 'and more' — list the actual covered resources (the body enumerates Addresses, Checks, Letters, Postcards, Templates, US/International Verifications) to sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the Lob domain and lists concrete entities ('Persons, Organizations, Deals, Leads, Projects, Activities'), but the verb 'Manage' is generic and 'and more' leaves coverage vague, matching anchor 3 rather than the comprehensive 4-5.	3 / 5
Completeness	Provides both a 'what' ('Manage Persons, Organizations...') and an explicit 'when' ('Use when the user wants to interact with Lob data'); the 'when' is present but generic, matching anchor 4 where the trigger could be more specific.	4 / 5
Trigger Term Quality	Includes the core term 'Lob' plus natural entity names ('Deals', 'Leads', 'Projects'), but omits the natural Lob-domain synonyms a user would say (direct mail, postcards, letters, address verification) that the body covers, fitting anchor 3.	3 / 5
Distinctiveness Conflict Risk	'Lob integration' is a clear, distinct niche, but the generic CRM-style entity list (Persons, Deals, Leads) creates minor overlap risk with other SaaS skills, fitting anchor 4.	4 / 5
	Total	14 / 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/lob/SKILL.md
Commit: f484c82

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