Name: follow-up-boss
Rating: 64.8 (1 reviews)
Author: membranedev

follow-up-boss

Follow Up Boss integration. Manage Persons, Organizations, Leads, Deals, Pipelines, Activities and more. Use when the user wants to interact with Follow Up Boss data.

Quality

77%

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/follow-up-boss/SKILL.md

Quality

Content

76%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 highly actionable with copy-paste CLI commands and a well-structured connection state machine, but loses points for missing validation around destructive actions and minor verbosity. Progressive disclosure is solid for a single-file skill though slightly long.

Suggestions

Add an explicit validation/confirmation step before destructive actions (e.g. 'Before delete-*, confirm the ID with a get-* call and verify with the user') to lift the workflow-clarity cap.

Trim padding such as 'so you can focus on the integration logic rather than auth plumbing' and condense the introductory CRM-description paragraph.

Consider moving the 20-row popular-actions table into a references file and linking to it, keeping only a few key examples inline, to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and tables, but includes minor padding such as 'so you can focus on the integration logic rather than auth plumbing' and a slightly padded intro paragraph explaining what Follow Up Boss is.	4 / 5
Actionability	Fully executable, copy-paste-ready commands cover the full path: install (`npm install -g @membranehq/cli@latest`), login, `connection ensure`, `action list/run`, and `request` proxy, plus a populated popular-actions table and proxy flag table.	5 / 5
Workflow Clarity	The connection workflow has a clear sequence with explicit polling/state validation (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but the skill exposes destructive actions (delete-person, delete-deal, delete-task) with no validation or verification guidance, which caps workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and no bundle files to navigate; at ~165 lines the large popular-actions table is borderline inline-heavy but remains useful and appropriately placed, leaving minor organization gaps rather than a clean one-level-deep split.	4 / 5
	Total	16 / 20 Passed

Description

78%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 clearly identifies a specific product niche and lists concrete entities, with both a 'what' and a 'when' clause. It is held back from a perfect score by the generic 'Manage ... and more' verb and a slightly vague trigger clause.

Suggestions

Replace the generic 'Manage ... and more' with specific verbs (e.g. 'create, update, list, and delete Persons, Deals, Tasks') to sharpen the capability list.

Tighten the trigger clause to concrete situations, e.g. 'Use when the user wants to query or update Follow Up Boss leads, deals, people, or tasks.'

Dimension	Reasoning	Score
Specificity	Names the domain ('Follow Up Boss integration') and lists several concrete entities to manage ('Persons, Organizations, Leads, Deals, Pipelines, Activities'), though the verb 'Manage ... and more' is generic rather than enumerating distinct actions.	4 / 5
Completeness	Explicitly states both what ('Manage Persons, Organizations, Leads, Deals, Pipelines, Activities') and when ('Use when the user wants to interact with Follow Up Boss data'); the 'when' clause is present but fairly generic ('interact with ... data').	4 / 5
Trigger Term Quality	Includes the product name and a strong set of domain keywords (Persons, Organizations, Leads, Deals, Pipelines, Activities) users would naturally say, but offers no synonyms or file-extension-style variants.	4 / 5
Distinctiveness Conflict Risk	Tied to a single named product ('Follow Up Boss'), giving it a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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/follow-up-boss/SKILL.md
Commit: f484c82

Reviewed: ~21 hours 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.