Name: beacon
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

beacon

Beacon integration. Manage data, records, and automate workflows. Use when the user wants to interact with Beacon data.

Quality

66%

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/beacon/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 body is well-structured and largely executable, with concrete Membrane CLI commands and a clear connection-readiness workflow. Main weaknesses are mild over-explanation and missing explicit validation/feedback-loop guidance for destructive action runs.

Suggestions

Add a brief validation/retry step for batch or destructive action runs (e.g. check the `output` and `error` fields before proceeding) to strengthen workflow feedback loops.

Trim the marketing intro and auth-plumbing commentary so the file assumes Claude's competence and earns every token.

Resolve the dangling 'Step 2' reference or renumber the connection steps so the sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and a flags table, but includes some over-explanation (e.g. the marketing-style intro 'helps businesses manage and respond to customer inquiries' and 'you can focus on the integration logic rather than auth plumbing') that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy with concrete flags, but minor gaps remain (e.g. popular-actions section reuses generic placeholders and the 'Searching for actions' intent is just 'QUERY').	4 / 5
Workflow Clarity	There is a clear sequence for connection readiness with explicit polling states and a state-machine (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), though the 'Step 2' / step numbering is incomplete and validation feedback loops for batch/destructive action runs are only weakly implied.	4 / 5
Progressive Disclosure	Content is well organized into overview, install, auth, connecting, searching, running, proxy, and best-practices sections with no nested references and no bundle files; minor gaps only (the Overview lists entity types without pointing to where action details live).	4 / 5
	Total	16 / 20 Passed

Description

58%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 names the Beacon niche and includes a 'Use when' clause, but the action verbs are generic and the trigger language is vague. It is functional but would benefit from concrete actions and natural trigger phrases users actually say.

Suggestions

Replace generic verbs with concrete Beacon actions, e.g. 'Search and update contacts, companies, deals, tasks, and notes; run and proxy Beacon API actions'.

Expand trigger terms with natural user phrasing such as 'customer support tickets', 'contacts', 'deals', or 'Beacon records'.

Make the 'when' clause explicit with concrete triggers: 'Use when the user wants to query or update Beacon contacts, companies, deals, tasks, or notes.'

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the domain and a couple of actions (manage data/records, automate workflows), but the verbs are generic and not comprehensive like the anchor 'Processes PDF files and extracts content'.	3 / 5
Completeness	It answers 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Beacon data'), though the 'when' is generic rather than tied to concrete trigger phrases, fitting the 'both present but when could be more specific' anchor.	4 / 5
Trigger Term Quality	'Beacon data' is the main natural keyword, with 'records' and 'workflows' as weak synonyms, but it misses common variations users would say (e.g. tickets, contacts, support requests), matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Beacon' names a niche but the actions ('manage data, records, automate workflows') are broad and could overlap with other CRM/data skills, matching 'somewhat specific but could still overlap with similar skills'.	3 / 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/beacon/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.