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

alphasense

AlphaSense integration. Manage data, records, and automate workflows. Use when the user wants to interact with AlphaSense 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/alphasense/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 highly actionable with concrete, executable Membrane CLI commands and a clear connection-setup workflow with validation feedback loops, held back by a slightly padded intro and a few minor organization gaps.

Suggestions

Trim the opening platform-explainer paragraph and the marketing phrases to assume Claude's competence and save tokens.

Resolve the dangling "Step 2" reference by labeling the searching/running section as Step 2 or removing the cross-reference.

Populate the "Popular actions" section with a few concrete example AlphaSense actions instead of restating the discovery command.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but it opens with a platform-explainer paragraph and includes marketing-flavored filler ("so you can focus on the integration logic rather than auth plumbing", "burn less tokens"), so it could be tightened; this fits 'mostly efficient but includes some unnecessary explanation.'	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action discovery, action run, and proxy requests with flag tables, but relies on placeholders (CONNECTION_ID) and the "Popular actions" section restates discovery without listing actual popular actions, leaving minor gaps.	4 / 5
Workflow Clarity	The install→login→connection→search→run sequence is clear with explicit state polling and feedback loops for connection states (READY/BUILDING/CLIENT_ACTION_REQUIRED), though the referenced "Step 2" is unlabeled and action execution lacks validation guidance, fitting 'clear sequence with most checkpoints present; minor validation gaps.'	4 / 5
Progressive Disclosure	With no bundle files present, the skill is self-contained and well-organized into clearly labeled sections with one external link to official docs; minor duplication between "Searching for actions" and "Popular actions" keeps it just below the ideal, fitting 'good structure; most content appropriately placed; minor organization gaps.'	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 answers both what and when and is anchored to a clearly named platform, but its capability list is generic and it lacks the natural AlphaSense-specific trigger terms (search, filings, documents) users would actually say.

Suggestions

Replace the generic actions with concrete AlphaSense capabilities, e.g. "Search documents and filings, read notes and expert calls, and build dashboards."

Add natural trigger terms users say, such as "search AlphaSense", "company filings", "expert calls", or "AlphaSense documents".

Tighten the 'when' clause to mention concrete intents like analyzing a company or researching market intelligence.

Dimension	Reasoning	Score
Specificity	It names the domain ("AlphaSense integration") but the actions "Manage data, records, and automate workflows" are minimal and generic rather than concrete capabilities; this matches the anchor 'Names the domain but actions are minimal or generic.'	2 / 5
Completeness	It has both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with AlphaSense data"), though the 'what' is generic and could be more specific, matching the anchor for having both with room for improvement.	4 / 5
Trigger Term Quality	The natural trigger term "AlphaSense" and "interact with AlphaSense data" are present, but it misses common variations users would say such as search, filings, documents, or expert calls, fitting 'some relevant keywords but missing common variations or synonyms.'	3 / 5
Distinctiveness Conflict Risk	Naming a specific platform (AlphaSense) gives it a clear niche with distinct triggers, but the generic phrasing "manage data, records, automate workflows" leaves minor overlap risk with related data-integration skills, fitting 'mostly distinct; minor overlap risk.'	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/alphasense/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.