CtrlK
BlogDocsLog inGet started
Tessl Logo

tecalliance

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

60

Quality

70%

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/tecalliance/SKILL.md
SKILL.md
Quality
Evals
Security

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 delivers actionable, executable guidance for the Membrane/TecAlliance flow with strong state-based validation checkpoints. Its weaknesses are minor: some redundant or background prose, placeholder-dependent examples, and an unlabeled "Step 2" reference.

Suggestions

Label the step sequence explicitly (Step 1a/1b, Step 2: Search actions) so the "skip to Step 2" reference resolves to a real section.

Merge the redundant "Popular actions" section into "Searching for actions" and trim the marketing-style intro paragraph about who uses TecAlliance.

Add at least one concrete end-to-end example using a real TecAlliance action id with actual input parameters, not just CONNECTION_ID placeholders.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable commands, but the introductory paragraph on who uses TecAlliance and the redundant "Popular actions" section (which repeats the action-list command) are minor over-explanation that could be trimmed.

4 / 5

Actionability

It provides concrete copy-paste-ready bash commands for install, login, connection, action list/run, and proxy requests, but relies on CONNECTION_ID placeholders and shows no real TecAlliance action id with actual parameters, leaving minor gaps.

4 / 5

Workflow Clarity

The connection setup has a clear state-driven sequence with checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and feedback loops (poll again after user action), but it references an unlabeled "Step 2" and uses loose numbering ("1b" with no labeled 1a), leaving minor navigation gaps.

4 / 5

Progressive Disclosure

No bundle files exist, so content lives in one file; it is well-organized with clear section headers (Overview, Authentication, Connecting, Searching, Proxy, Best practices) and no nested references, fitting the good-structure-minor-gaps anchor.

4 / 5

Total

16

/

20

Passed

Description

66%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 an explicit Use-when clause tied to a distinct named platform, avoiding major conflict risk. Its main weakness is generic action verbs and limited trigger-term variation beyond repeating the platform name.

Suggestions

Replace generic verbs ("Manage data, records") with concrete TecAlliance capabilities, e.g. "Search parts by article/OEM number, look up vehicles by VIN, and query parts catalogs".

Expand trigger terms to include natural user phrases like "parts lookup", "vehicle by VIN", "OEM number", or "TecDoc".

DimensionReasoningScore

Specificity

Names the domain (TecAlliance) and lists actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete API-level operations, matching the anchor for naming a domain with 1-2 non-comprehensive actions.

3 / 5

Completeness

It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with TecAlliance data"), but the when could be more specific about particular tasks, matching the both-present-but-could-be-more-explicit anchor.

4 / 5

Trigger Term Quality

"TecAlliance" and "interact with TecAlliance data" are relevant natural terms, but coverage lacks synonyms or variations beyond the platform name, fitting the anchor for some relevant keywords missing common variations.

3 / 5

Distinctiveness Conflict Risk

"TecAlliance" is a distinct named platform with dedicated triggers, giving it a clear niche and minimal risk of triggering for the wrong skill, matching the clear-niche-minimal-conflict anchor.

5 / 5

Total

15

/

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.