CtrlK
BlogDocsLog inGet started
Tessl Logo

alpaca

Alpaca integration. Manage Organizations, Users, Filters. Use when the user wants to interact with Alpaca 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

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/alpaca/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 body is highly actionable with executable commands and a well-structured connection workflow featuring explicit state checkpoints and feedback loops. Its main weaknesses are minor over-explanation and a slightly broken step cross-reference ('Step 2', '1b').

Suggestions

Fix the broken cross-reference: either label an explicit 'Step 2' or reword 'skip to Step 2' to a concrete anchor like 'Searching for actions'.

Trim the Alpaca company introduction and the 'so you can focus on the integration logic' aside, which explain context Claude already knows.

Consider moving the popular-actions reference table into a separate file referenced from the overview to tighten the main skill body.

DimensionReasoningScore

Conciseness

Largely lean procedural command documentation, with only minor over-explanation such as 'so you can focus on the integration logic rather than auth plumbing' and the brief Alpaca company intro that could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands across install, auth, connection, action search/run, and proxy, plus a comprehensive flags table covering the common cases.

5 / 5

Workflow Clarity

The connection workflow has explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a feedback loop (poll again after user action), but the prose references an unlabeled 'Step 2' and uses an odd '1b' heading, leaving minor sequencing gaps.

4 / 5

Progressive Disclosure

Single well-sectioned SKILL.md with no bundle files; sections are clearly organized, though the long popular-actions table is inlined where a separate reference file could keep the overview leaner.

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 answers both 'what' and 'when' and is anchored to a distinct brand, but its action verbs are generic ('Manage') and it omits natural trading-domain trigger terms. Note the described capabilities (Organizations, Users, Filters) appear mismatched with the body's actual trading focus.

Suggestions

Replace the generic 'Manage Organizations, Users, Filters' with concrete trading actions that match the body, e.g. 'Place orders, query positions, manage watchlists'.

Add natural trigger phrases users would say, such as 'trading', 'stocks', 'orders', or 'Alpaca API'.

Make the 'when' clause more specific, e.g. 'Use when the user wants to trade, check positions, or query market data via Alpaca.'

DimensionReasoningScore

Specificity

Names the domain (Alpaca) and lists concrete entities ('Manage Organizations, Users, Filters'), but the single generic verb 'Manage' applied to three nouns is less specific than distinct action verbs, so it falls short of the 4 anchor.

3 / 5

Completeness

Provides a clear 'what' ('Alpaca integration. Manage Organizations, Users, Filters.') and an explicit 'when' ('Use when the user wants to interact with Alpaca data.'), though the when clause is somewhat generic rather than listing concrete triggers.

4 / 5

Trigger Term Quality

Includes the brand keyword 'Alpaca' (the primary natural trigger) but misses common synonyms a user would say for a trading platform ('trading', 'stocks', 'orders'), and 'Organizations, Users, Filters' are not natural user phrases.

3 / 5

Distinctiveness Conflict Risk

Tied to a distinct brand niche ('Alpaca') with minimal conflict risk, but the broad 'interact with Alpaca data' trigger leaves minor overlap ambiguity versus a hypothetical 5-anchor with concrete, narrow 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.