CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-sales-tax-nexus

US sales tax economic nexus evaluation, registration checklists, and exemption certificate workflows for e-commerce. Use when: Determine which states require sales tax registration based on revenue; Manage and validate MTC and SST exemption certificates for wholesale; Brief marketplace-only sellers on their specific registration requirements.

Quality

63%

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/nex-sales-tax-nexus/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

21%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 reads as a product landing page rather than operational skill instructions: it markets capabilities, repeats itself in an FAQ, and contains none of the tables, checklists, or templates it promises. A user following it could not actually evaluate nexus, register, or validate a certificate. It also embeds dated rules (June 2026) without a maintenance/deprecated section.

Suggestions

Replace descriptive capability claims with executable guidance: inline the actual per-state threshold table (or ship it as references/thresholds.md) and provide a concrete nexus-evaluation procedure Claude can follow step by step.

Add a real workflow with validation checkpoints (collect sales-by-state data → check physical nexus (warehouses/FBA) → check economic thresholds against the table → verify current rules on the state DOR site → produce registration checklist), instead of a single sample output.

Cut the 'Questions' FAQ (it duplicates 'What it does', 'Frameworks & tools', and 'Known limitations') and the marketing sections ('The problem', 'Why this beats prompting it yourself'), and move dated rule statements like '200-transaction test removed Jan 2026' into a clearly marked dated/deprecated section so they can be maintained.

Ship the promised artifacts as bundle files (e.g., references/registration-checklist.md, assets/mtc-sst-templates.md) and link to them from the body, since the current folder contains none of them.

DimensionReasoningScore

Conciseness

Marketing padding ('a logistical nightmare', 'Why this beats prompting it yourself') and a 'Questions' FAQ section that restates 'What it does', 'Frameworks & tools', and 'Known limitations' nearly verbatim add substantial unnecessary tokens. Time-sensitive claims ('updated with the latest June 2026 transaction and revenue rules', '200-transaction test removed Jan 2026') appear inline rather than in a dated/deprecated section.

2 / 5

Actionability

The body only describes capabilities ('Generates state-specific threshold reference tables', 'Produces registration checklists') without any actual thresholds, checklists, commands, or steps, and it admits the working materials are absent ('Scripts, extension source, and templates from the original package are not in this folder'). The single Example shows an output, not instructions for producing it.

1 / 5

Workflow Clarity

The Example output implies a rough order (physical nexus, then economic, then risk, then 'Next step: Register'), but no steps are defined anywhere and the claimed 'mandatory verification steps' baked into every workflow are never shown — only a generic manual DOR-verification caveat. It is above the 1 anchor only because a rough sequence is inferable.

2 / 5

Progressive Disclosure

Section headers give the ~75-line body readable structure, but the detailed materials it advertises (threshold tables, registration checklists, MTC/SST templates) exist in no file — the bundle has no references/, scripts/, or assets/ directories, only external storefront links. Structure is present, but the overview-to-detail split is missing rather than merely imperfect.

3 / 5

Total

8

/

20

Passed

Description

87%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.

A well-formed description: it names a specific domain, gives concrete actions, and provides an explicit multi-scenario 'Use when' trigger clause. The only weaknesses are a noun-phrase capability summary and a few missing natural synonyms (resale certificate, FBA, tax-exempt).

DimensionReasoningScore

Specificity

Lists several concrete actions ('Manage and validate MTC and SST exemption certificates', 'Brief marketplace-only sellers on their specific registration requirements') but the opening capability clause ('US sales tax economic nexus evaluation, registration checklists, and exemption certificate workflows') is noun-phrase-based, leaving minor coverage gaps versus the comprehensive 5 anchor.

4 / 5

Completeness

Explicitly answers what ('US sales tax economic nexus evaluation, registration checklists, and exemption certificate workflows for e-commerce') and when, via a 'Use when:' clause with three concrete trigger scenarios. It fits the 5 anchor rather than 4 because the when-guidance is explicit and specific, not merely present.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — 'sales tax', 'economic nexus', 'exemption certificates', 'wholesale', 'marketplace-only sellers' — but misses common variations such as 'resale certificate', 'FBA', 'Amazon', 'tax-exempt', or 'sales tax permit', so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear niche (US sales tax nexus for e-commerce) with distinct triggers like 'MTC and SST exemption certificates' and 'marketplace-only sellers' that are unlikely to fire for unrelated skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

skills/nex-sales-tax-nexus/SKILL.md

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.