CtrlK
BlogDocsLog inGet started
Tessl Logo

aleph-alpha

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

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/aleph-alpha/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 concrete, executable Membrane CLI commands and a clear connection state machine with feedback loops. It is well-organized and mostly concise, with only minor trimming and a broken step reference worth fixing.

DimensionReasoningScore

Conciseness

The body is mostly efficient command examples, but includes minor over-explanation Claude largely knows ("Aleph Alpha is an AI research company that offers large language models...") and slightly padded phrasing like "so you can focus on the integration logic rather than auth plumbing".

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands covering the common cases (install, login, connection ensure, action list/run, request proxy) with concrete flags and JSON examples, matching the anchor for fully executable guidance.

5 / 5

Workflow Clarity

There is a clear install→auth→connect→search→run sequence with an explicit state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, but the "skip to Step 2" reference is broken and running actions lacks output validation, leaving minor gaps.

4 / 5

Progressive Disclosure

No bundle files exist and the single SKILL.md is well-organized into clear sections (Overview, Install, Auth, Connecting, Searching, Running, Proxy, Best practices); structure is good, though inline tables (popular actions, proxy flags) could be split into references for a cleaner overview.

4 / 5

Total

17

/

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 correctly includes an explicit "Use when..." trigger and names the Aleph Alpha niche, but its action verbs are generic and it lacks concrete capability terms and synonyms. It is functional but would benefit from sharper, more specific language.

Suggestions

Replace generic verbs with concrete Aleph Alpha capabilities, e.g. "Generate completions, summarize text, create semantic embeddings, and evaluate Luminous models."

Expand trigger terms to natural user phrases and synonyms, e.g. "Use when the user wants to complete, summarize, embed, tokenize, or rerank text with Aleph Alpha models."

Tie the "when" clause to specific use cases (completions, embeddings, evaluation) rather than the vague "interact with Aleph Alpha data".

DimensionReasoningScore

Specificity

The description names the domain ("Aleph Alpha integration") and lists actions ("Manage data, records, and automate workflows"), but those verbs are generic rather than concrete like extract/fill/merge, so it stops at naming a few actions without comprehensive, specific coverage.

3 / 5

Completeness

It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Aleph Alpha data"), but the "what" is generic and the "when" could be more specific, fitting the anchor with both present but improvable.

4 / 5

Trigger Term Quality

The trigger "Use when the user wants to interact with Aleph Alpha data" includes the key brand term and "data", but lacks common variations or synonyms (e.g., completions, embeddings, summarization, Luminous) a user would naturally say.

3 / 5

Distinctiveness Conflict Risk

The "Aleph Alpha" brand gives it a clear, distinct niche with low conflict risk, but the generic action phrasing ("manage data, records") creates minor overlap with other data-management skills rather than fully distinct triggers.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.