Name: stripe-tax
Rating: 60 (1 reviews)
Author: membranedev

stripe-tax

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/stripe-tax/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 body is a lean, highly actionable guide with concrete CLI commands and a clear connection-setup workflow that includes state-validation branching, with only minor padding and slight section redundancy.

Suggestions

Trim the opening paragraph that defines what Stripe Tax is; Claude already knows this and it costs context.

Add a brief verification step after running actions (e.g. check the response state/error field) to close the workflow loop.

Merge the redundant 'Searching for actions' and 'Popular actions' sections that both demonstrate `action list --intent`.

Dimension	Reasoning	Score
Conciseness	Mostly lean, command-driven content with minor over-explanation (the opening paragraph defining what Stripe Tax is and the 'Agent Types' aside could be trimmed); not a 5 because of that light padding.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) with concrete flags and JSON examples covering the common cases.	5 / 5
Workflow Clarity	Clear install→auth→connect→search→run sequence with an explicit validation feedback loop in the connection 'wait for ready' step (state polling and CONFIGURATION_ERROR branching); not a 5 because action-running has no verification checkpoint.	4 / 5
Progressive Disclosure	Well-organized into clearly labeled sections with no nested or buried references and no bundle files to misplace; minor redundancy between 'Searching for actions' and 'Popular actions' keeps it just below 5.	4 / 5
	Total	17 / 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 tied to a distinct named service, but the capability phrasing is generic ('Manage data, records, and automate workflows') and lacks concrete tax actions or synonym coverage.

Suggestions

Replace generic verbs with concrete Stripe Tax actions, e.g. 'calculate and collect sales tax/VAT/GST, retrieve tax records, create and update transactions'.

Broaden the trigger clause to include natural synonyms: 'Use when the user wants to calculate sales tax, VAT, or GST, or interact with Stripe Tax data.'

Add file-format or entity triggers (e.g. tax transactions, tax calculations) to improve natural-keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Stripe Tax integration') but the listed actions ('Manage data, records, and automate workflows') are generic and lack concrete tax-specific operations, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	Both a 'what' ('Stripe Tax integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Stripe Tax data') are present; not a 5 because the 'what' is generic rather than concrete.	4 / 5
Trigger Term Quality	Includes the natural product term 'Stripe Tax' and 'Stripe Tax data', but misses common synonyms and variations a user might say (sales tax, VAT, GST, tax calculation, tax compliance).	3 / 5
Distinctiveness Conflict Risk	Tied to a named service ('Stripe Tax') with a distinct trigger, so mostly distinct; minor overlap risk with other Stripe-family skills keeps it below 5.	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/stripe-tax/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.