Name: bluebeam
Rating: 59.2 (1 reviews)
Author: membranedev

bluebeam

Bluebeam integration. Manage Persons, Organizations, Deals, Projects, Activities, Notes and more. Use when the user wants to interact with Bluebeam data.

Quality

68%

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

Quality

Content

75%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 highly actionable with executable commands, a comprehensive action catalog, and a well-gated connection workflow with state-based validation. The main weakness is conciseness — an introductory conceptual paragraph about Bluebeam's domain and some auth-plumbing filler could be cut without losing utility.

Suggestions

Trim the opening paragraph explaining Bluebeam's AEC use cases and the 'focus on integration logic rather than auth plumbing' filler; Claude already knows this.

Fix the dangling 'skip to Step 2' reference by numbering the workflow steps (Step 1 connection, Step 2 actions) or removing the forward reference.

Consider moving the 20-row popular-actions table into a separate references file referenced from the body to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands and tables, but the opening paragraph explains what Bluebeam is and who uses it (AEC professionals, architects, engineers) plus filler like 'so you can focus on the integration logic rather than auth plumbing', which Claude already understands and could be trimmed.	3 / 5
Actionability	Every section provides fully executable bash commands (install, login, connection ensure, action run with --input JSON, request proxy) plus a popular-actions table and a proxy-options table, making the guidance copy-paste ready across common cases.	5 / 5
Workflow Clarity	Connection setup is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a polling loop, but the cross-reference 'skip to Step 2' points to a Step 2 that is never defined or numbered, leaving a minor sequencing gap.	4 / 5
Progressive Disclosure	The single file is well sectioned with no nested or buried references and no bundle files needed, though the long popular-actions table is inlined where it could optionally live in a separate reference file; structure is otherwise clear and navigable.	4 / 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 answers both what and when with a clear product niche, but leans on the single generic verb 'Manage' for all listed entities and offers few natural trigger terms beyond the product name itself. Tightening the verbs and adding concrete user-facing phrases would lift specificity and trigger quality.

Suggestions

Replace the blanket 'Manage' with concrete verbs per entity (e.g., 'Create, update, and delete Projects and Sessions; list and invite Session attendees').

Add natural trigger phrases users would say, such as 'Bluebeam Studio Projects/Sessions', 'PDF markup review', or 'collaborate on construction documents'.

Remove 'and more' or back it with the specific capabilities it covers so the scope is bounded rather than open-ended.

Dimension	Reasoning	Score
Specificity	The description names the domain (Bluebeam) and lists several concrete entities (Persons, Organizations, Deals, Projects, Activities, Notes), but every verb collapses to the generic 'Manage... and more', leaving the actual actions unenumerated and coverage incomplete.	3 / 5
Completeness	It states both what the skill does ('Manage Persons, Organizations, Deals...') and when to use it ('Use when the user wants to interact with Bluebeam data'), but the 'when' clause is generic and could be more specific.	4 / 5
Trigger Term Quality	'Bluebeam' and 'Bluebeam data' are the only natural keywords present; common variations, synonyms, or file extensions a user might say are absent, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Bluebeam' is a clear niche product with a distinct trigger, giving low conflict risk; the generic 'and more' and broad 'interact with Bluebeam data' phrasing leave a slight overlap/breadth risk versus a score of 5.	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/bluebeam/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.