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

Blog Docs Log in Get started

followup

Followup integration. Manage Organizations, Users. Use when the user wants to interact with Followup 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/followup/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 body is actionable and well-structured with concrete CLI commands and a validation-backed connection workflow, but it carries some padded prose and a dangling 'Step 2' reference.

Suggestions

Trim filler sentences such as 'so you can focus on the integration logic rather than auth plumbing' and the vague 'Use action names and parameters as needed'.

Define or relabel the referenced 'Step 2' so the cross-reference in the connection flow resolves.

Note where placeholders like CONNECTION_ID and <actionId> must be substituted, or show one fully-resolved end-to-end example.

Dimension	Reasoning	Score
Conciseness	Most content is efficient executable commands, but padded phrases like 'so you can focus on the integration logic rather than auth plumbing' and the vague 'Use action names and parameters as needed' could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready bash commands for install, login, connection, action search/run, and proxy requests, plus an actions table; minor gaps remain around substituting placeholders like CONNECTION_ID.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state-based validation (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but references to an undefined 'Step 2' leave a minor gap.	4 / 5
Progressive Disclosure	As a single well-organized file with no bundle references, it uses clear section headers (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) for easy navigation.	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 includes an explicit 'Use when' trigger and ties itself to a named product, but its capability statement is generic ('Manage Organizations, Users') and lacks concrete actions or keyword variations.

Suggestions

Replace the generic 'Manage Organizations, Users' with concrete actions, e.g. 'Create and list reminders, manage contacts and follow-ups'.

Add keyword variations and synonyms users might say, such as 'CRM', 'leads', 'email campaigns', or 'Followup.cc'.

Tighten the 'when' clause with concrete trigger phrases, e.g. 'Use when the user wants to manage Followup reminders, contacts, or email campaigns'.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage Organizations, Users' names the domain and two entities, but the action 'Manage' is minimal and generic rather than listing concrete operations.	2 / 5
Completeness	It states both a 'what' ('Manage Organizations, Users') and an explicit 'when' ('Use when the user wants to interact with Followup data'), though the 'what' is generic and could be more concrete.	4 / 5
Trigger Term Quality	Relevant keywords appear ('Followup data', 'Organizations', 'Users') via the 'Use when the user wants to interact with Followup data' clause, but common variations and synonyms are missing.	3 / 5
Distinctiveness Conflict Risk	Tying triggers to the named 'Followup' product gives it a clear niche with minimal conflict risk, though 'Manage Organizations, Users' is generic CRM territory that could overlap related skills.	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/followup/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.