Name: teller
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

teller

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

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/teller/SKILL.md

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 executable commands and a well-designed connection state-machine including polling feedback loops. Its main weaknesses are a few padded explanatory lines, a dangling 'Step 2' cross-reference, and a 'Popular actions' heading that underdelivers.

Suggestions

Resolve the dangling 'skip to Step 2' reference by labeling the searching/running-actions section as Step 2, and rename '1b' to a coherent numbered step so the sequence is unambiguous.

Trim editorial padding such as 'so you can focus on the integration logic rather than auth plumbing' to keep the body token-lean.

Either populate 'Popular actions' with a short list of commonly used Teller actions or rename the section to 'Discovering actions' so the heading matches the content.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete commands and a useful state table, but a few lines pad concepts Claude already knows (e.g. 'so you can focus on the integration logic rather than auth plumbing'), placing it just below the lean/efficient anchor.	4 / 5
Actionability	It provides copy-paste-ready commands for every phase (install, login, connection ensure, action list/run, request) plus a concrete proxy-flag table, fully covering the common cases with executable guidance.	5 / 5
Workflow Clarity	The connect-to-ready flow has strong feedback loops (polling, READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR state checks, re-poll after user action), but a dangling 'skip to Step 2' with no Step 2 and an unexplained '1b' label create minor sequence gaps, capping it below 5.	4 / 5
Progressive Disclosure	No bundle files exist, so structure is judged on the single file; sections are well organized with clear headers and no nested references, but at ~140 lines (over the 50-line simple-skill exception) and with a 'Popular actions' section that is a discovery pointer rather than content, it stays at good-structure-with-minor-gaps.	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 is functional, naming the Teller domain and providing an explicit 'Use when' trigger, so it clears the completeness bar. Its weakness is generic action language and thin trigger-term variation, which keep specificity and trigger quality at the midpoint.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Teller capabilities such as 'sync transactions, reconcile accounts, and generate financial reports'.

Expand the trigger clause with natural user phrases and synonyms, e.g. 'Use when the user wants to pull Teller transactions, balance accounts, or automate bookkeeping workflows'.

Tighten the what/when pairing so the trigger names specific Teller objects (transactions, budgets, reports) to reduce overlap with generic data skills.

Dimension	Reasoning	Score
Specificity	Names the Teller domain and lists a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete, so it lands above the minimal/generic anchor (2) yet below comprehensive concrete actions (5).	3 / 5
Completeness	Explicitly answers both what ('Teller integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Teller data'), but the trigger could be more specific, fitting the 'both present, when could be more explicit' anchor rather than 5.	4 / 5
Trigger Term Quality	Includes relevant terms ('Teller', 'interact with Teller data') but lacks common variations or synonyms a user might naturally say, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming Teller gives a clear niche with minimal conflict risk, but the broad 'manage data, records, automate workflows' phrasing leaves minor overlap with general data skills, so it is mostly distinct rather than fully distinct.	4 / 5
	Total	14 / 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/teller/SKILL.md
Commit: f484c82

Reviewed: 4 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.