Name: outreach
Rating: 55.2 (1 reviews)
Author: membranedev

outreach

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

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

67%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 strong, command-driven integration guide with a well-sequenced connection workflow and explicit state-handling checkpoints. Its main weaknesses are a large padded entity-name list and the absence of a worked write-operation example with real parameters.

Suggestions

Collapse the ~60-item bulleted entity list into a one-line pointer (e.g. 'Outreach exposes ~60 objects including prospects, accounts, opportunities, sequences, and templates — discover the rest via `membrane action list`') to reclaim tokens.

Add one fully worked write example with realistic JSON input, e.g. `membrane action run create-prospect --input '{"email":"...","firstName":"..."}'` plus how to read the resulting output.

Add a brief post-write verification note (e.g. re-run the corresponding list/get action to confirm the created or updated record) to close the validation loop on create/update operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands but includes substantial padding, notably a ~60-item bulleted list of entity names ('Account', 'Sequence', 'Mailbox', ...) and prose like 'so you can focus on the integration logic rather than auth plumbing', matching the score-3 anchor 'Mostly efficient but includes some unnecessary explanation or could be tightened'. It is not a 2 because the bulk is actionable command reference, and not a 4 because the entity list is large low-value token spend.	3 / 5
Actionability	It provides concrete, executable commands throughout — `membrane login`, `membrane connection ensure`, `membrane action list/run`, `membrane request` — plus a popular-actions table with names and keys, matching the score-4 anchor 'Mostly executable guidance; concrete code or commands with minor gaps'. It is not a 5 because common write operations lack a full worked input example showing real JSON parameters.	4 / 5
Workflow Clarity	The connection flow is a clearly sequenced multi-step process with explicit checkpoints and feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED, branch on CONFIGURATION_ERROR/SETUP_FAILED), matching the score-4 anchor 'Clear sequence with most checkpoints present'. It is not a 5 because create/update operations lean on Membrane's generic error handling without an explicit post-write verification step, and not a 3 because the connection workflow itself has strong validation.	4 / 5
Progressive Disclosure	The body is a single, well-sectioned SKILL.md with clear headers (Overview, Working with Outreach, Popular actions, Best practices) and one external link to official docs; no bundle files exist and there are no nested references, matching the score-4 anchor 'Good structure; most content is appropriately placed'. It is not a 5 because the large inline entity list is content that could live in a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

57%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 a competent, third-person trigger statement with an explicit 'Use when' clause, but it relies on the generic verb 'Manage' and broad nouns rather than concrete Outreach operations. It would score higher with specific verbs and natural user terms like prospects, sequences, and accounts.

Suggestions

Replace the generic 'Manage sales data, records, and workflows' with concrete verbs tied to Outreach entities, e.g. 'List and create prospects, accounts, opportunities, and sequences; run and track sales workflows.'

Add natural trigger terms users actually say, e.g. 'Use when the user mentions prospects, sequences, outreach cadences, or wants to query Outreach sales data.'

Keep the explicit third-person 'Use when' trigger but tighten it so it names the domain's primary objects rather than the abstract word 'interact'.

Dimension	Reasoning	Score
Specificity	The description names the Outreach domain but the actions are generic — 'Manage sales data, records, and workflows' uses the abstract verb 'Manage' with no concrete operations, matching the score-2 anchor 'Names the domain but actions are minimal or generic'. It is not a 1 because a domain and several action nouns are present, and not a 3 because no concrete verbs (e.g. list, create, update prospects) are stated.	2 / 5
Completeness	It states both a clear 'what' ('Outreach integration. Manage sales data, records, and workflows.') and an explicit 'when' ('Use when the user wants to interact with Outreach data.'), matching the score-4 anchor where 'when' could be more specific. It is not a 5 because the trigger phrase is generic rather than concrete, and not a 3 because an explicit 'Use when...' clause is present.	4 / 5
Trigger Term Quality	It includes some relevant keywords ('sales data, records, and workflows', 'interact with Outreach data') but misses the natural terms users would actually say (prospects, sequences, accounts, opportunities), matching the score-3 anchor 'Some relevant keywords but missing common variations or synonyms'. It is not a 4 because the keywords are generic rather than the specific Outreach nouns a user would naturally mention.	3 / 5
Distinctiveness Conflict Risk	'Outreach integration' with sales-data framing is a clear niche unlikely to fire for unrelated skills, matching the score-4 anchor 'Mostly distinct; minor overlap risk'. It is not a 5 because the generic trigger ('interact with Outreach data') could overlap with a broader CRM skill, and not a 3 because the Outreach brand and sales framing are specific.	4 / 5
	Total	13 / 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/outreach/SKILL.md
Commit: f484c82

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