Name: bouncer
Rating: 63.2 (1 reviews)
Author: membranedev

bouncer

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

Quality

75%

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/bouncer/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.

Highly actionable content with copy-paste commands and a strong connection workflow, but it lacks validation/feedback steps for its batch and destructive email-verification operations, which caps workflow clarity. Structure is clean with no bundle files to navigate.

Suggestions

Add a validation checkpoint for batch operations, e.g. poll bouncer.get-batch-status until the job is complete before calling bouncer.get-batch-results, and surface this as an explicit step sequence.

Add a confirm-before-destruct note for bouncer.delete-batch, bouncer.delete-toxicity-job, and bouncer.finish-batch (which returns credits for unverified emails) so destructive calls are guarded.

Trim the padded intro line about Bouncer being a mobile permissions app, which also conflicts with the email-verification actions actually documented, to save tokens and remove confusion.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands and a useful actions table, but a few padded lines (the "mobile app that gives users temporary permissions" intro and "so you can focus on the integration logic rather than auth plumbing") could be trimmed; not verbose enough for a 3.	4 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (install, login, connection ensure, polling with --wait, action list/run with --input JSON, request proxy) with real flags and a concrete actions table covering the common cases.	5 / 5
Workflow Clarity	The connection flow is well sequenced with polling and state feedback loops, but the skill's central batch and destructive operations (create/delete batch, finish batch, delete toxicity job) have no validation checkpoints or confirm-before-destruct guidance, so the batch/destructive cap of 3 applies.	3 / 5
Progressive Disclosure	No bundle files exist, so scoring is on structure alone; the body is well organized with clear section headers and no nested references, though the popular-actions table is reference content that is arguably inline rather than split out.	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.

A solid description that answers both 'what' and 'when' with a named app and a concrete resource list. The main weakness is the generic trigger clause and the open-ended "and more", which keep it just short of the top anchors.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete resources to manage ("Organizations, Leads, Projects, Pipelines, Users, Goals"), but the trailing "and more" leaves minor coverage gaps, fitting the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.	4 / 5
Completeness	It states both what ("Manage Organizations, Leads, Projects, Pipelines, Users, Goals") and when ("Use when the user wants to interact with Bouncer data"), but the 'when' trigger is generic and could be more explicit, matching the 4 anchor rather than the concrete-trigger 5.	4 / 5
Trigger Term Quality	Good keyword coverage of the app name and resource types ("Bouncer", "Organizations", "Leads", "Projects", "Pipelines", "Users", "Goals") that users would naturally name, though a few natural phrases (e.g. email verification, which the body actually covers) are missing.	4 / 5
Distinctiveness Conflict Risk	The named app "Bouncer" plus its resource list gives a mostly distinct niche with minimal conflict risk, though the generic project/CRM-style terms (Leads, Projects, Goals) carry minor overlap risk with general management skills.	4 / 5
	Total	16 / 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/bouncer/SKILL.md
Commit: f484c82

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