Name: beamer
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

beamer

Beamer integration. Manage Organizations, Users, Filters. Use when the user wants to interact with Beamer data.

Quality

70%

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

Quality

Content

78%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.

A highly actionable CLI integration guide with copy-paste membrane commands and a well-validated connection workflow including polling and state feedback loops. It loses points for inlined reference content with no external files, inconsistent step numbering, and minor verbosity in the intro and best-practices sections.

Suggestions

Move the 18-row Popular actions table into a references/ACTIONS.md file and link to it from the body to improve progressive disclosure.

Fix the step numbering (label "1a", add a clear "Step 2") and add a pre-run confirmation checkpoint for destructive actions (delete-post, delete-user, delete-comment).

Trim the opening "Beamer is a changelog..." paragraph and tighten the best-practices rationale to reduce token use.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight CLI commands and a compact action table, but the opening paragraph explaining what Beamer is and some padded best-practices rationale ("This will burn less tokens and make communication more secure") could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready membrane commands with flags and --json output covering install, login, connection ensure, polling, action list/run, and proxy requests, with concrete examples for the common cases.	5 / 5
Workflow Clarity	There is a clear sequence with explicit state-validation checkpoints and feedback loops (polling BUILDING, re-poll after CLIENT_ACTION_REQUIRED, handling CONFIGURATION_ERROR), but step numbering is inconsistent ("1b" with no "1a", "skip to Step 2" with no Step 2) and destructive actions lack pre-run confirmation.	4 / 5
Progressive Disclosure	Section headers give reasonable structure, but there are no bundle files or one-level-deep references and an 18-row Popular actions table is inlined that would be better placed in a separate reference file; the skill exceeds 50 lines so the simple-skill exception does not apply.	3 / 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 concise, third-person, and includes both a what and a Use-when clause, but the actions are generic ("Manage ...") and the trigger lacks concrete keywords like changelogs, posts, or announcements. Solid foundation with room to be sharper and more distinctive.

Suggestions

Replace the generic verb "Manage" with concrete operations, e.g. "Create, list, update, and delete posts, users, comments, and feature requests in Beamer."

Sharpen the trigger with natural user terms: "Use when the user wants to manage Beamer changelogs, posts, announcements, comments, or feature requests."

Disambiguate from LaTeX Beamer by signaling the SaaS/changelog context directly in the description.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Users, Filters" names the Beamer domain and three entities, but uses the generic verb "Manage" rather than specific concrete operations, so it sits at the domain-plus-actions-but-not-comprehensive anchor rather than a 4.	3 / 5
Completeness	Both "what" ("Beamer integration. Manage Organizations, Users, Filters.") and "when" ("Use when the user wants to interact with Beamer data.") are present, but the when clause is generic rather than concrete trigger phrases, keeping it just below a 5.	4 / 5
Trigger Term Quality	It includes "Beamer" and the entity names, but the trigger "Use when the user wants to interact with Beamer data" is generic and misses natural terms users would say like changelogs, posts, announcements, or feature requests.	3 / 5
Distinctiveness Conflict Risk	"Beamer" names a specific SaaS product making it mostly distinct, though the name also denotes LaTeX Beamer and the "interact with Beamer data" phrasing is broad enough to leave minor overlap risk.	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/beamer/SKILL.md
Commit: f484c82

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