CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-receipt-vault

Deploy a complete Manifest V3 extension to capture and dashboard online receipts locally without bank access. Use when: Deploy a private, local-only spending tracker for online shoppers; Build a robust web scraper extension using pre-configured platform detectors; Create a data-extraction tool that works without a backend or server.

Quality

57%

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

Quality

Content

15%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 marketing copy for a product whose deliverables are missing: it claims to provide "the complete, working source code" yet no bundle files exist and its single path reference is broken. It is not executable guidance, and it contains a self-contradictory FAQ answer ("Does this tool send my purchase data to an external database? Absolutely." followed by an answer describing purely local storage).

Suggestions

Ship the actual bundle (extension source in assets/extension/, scripts, or references) or remove the claim of complete source code, and replace the dangling "Files are in assets/extension/" pointer with a real file listing (actionability).

Replace the prose description with an explicit numbered workflow — load unpacked in chrome://extensions, edit a detector, reload, verify a receipt is captured — including a validation checkpoint (workflow_clarity).

Delete the "Why use this skill?" section, the redundant FAQ, and the duplicate attribution lines, and fix the contradictory "Absolutely." answer to the external-database question (conciseness).

DimensionReasoningScore

Conciseness

Several padded sections add no instructional value: the marketing prose of "Why use this skill?" ("a masterclass in professional extension development"), attribution repeated in two places ("Built by Nex AI. More skills and info at..."), and a FAQ that largely restates "What it does" (detectors, privacy, zero-build). This matches 'noticeably verbose; several unnecessary explanations or padded sections' rather than score 1, since it does not tutor Claude on known concepts.

2 / 5

Actionability

The body contains no code, commands, or file listings — it only describes ("its specialized extraction engine parses merchant details, itemized lists, totals, and dates"). The sole concrete pointer, "Files are in assets/extension/", targets a directory that does not exist, and the header concedes "Scripts, extension source, and templates from the original package are not in this folder", so nothing in the skill can actually be executed. This is the 'only describes rather than instructs' anchor; score 2's 'high-level hints' would require at least usable steps.

1 / 5

Workflow Clarity

No step sequence appears anywhere: deployment and customization fragments ("Load unpacked" in chrome://extensions, "Edit and reload instantly", "Requires manual reload in developer mode") are scattered across sections with no ordering and no validation checkpoints. Steps are missing outright, matching anchor 1 rather than anchor 2's 'rough sequence present'.

1 / 5

Progressive Disclosure

Section headers (What it does, When to use, Known limitations, Example) give the body some structure, but the only bundle reference — "Files are in assets/extension/" — is dangling, since no assets/, references/, or scripts/ directories exist, and the material that should live in those files is simply absent rather than split out. Anchor 3's 'some structure but could be better organized' fits best; not 4-5 because navigation leads nowhere.

3 / 5

Total

7

/

20

Passed

Description

83%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 strong description: it explicitly states what the skill does and gives three concrete 'Use when' triggers in third-person imperative voice with no first/second person. Its only weaknesses are un-enumerated capabilities and one overly broad trigger phrase that could overlap with generic data-extraction skills.

DimensionReasoningScore

Specificity

The what-clause "Deploy a complete Manifest V3 extension to capture and dashboard online receipts locally without bank access" names the domain and several concrete actions (deploy, capture, dashboard), matching the 'several specific actions; minor gaps' anchor. Not 5 because capabilities like platform detectors, extraction, and local storage are not enumerated; not 3 because more than 1-2 actions are named.

4 / 5

Completeness

Both parts are explicit: a clear what-statement plus an explicit "Use when:" clause enumerating three concrete triggers ("Deploy a private, local-only spending tracker for online shoppers; Build a robust web scraper extension...; Create a data-extraction tool that works without a backend"). This matches the 5 anchor's pattern of concrete trigger phrases; the 4 anchor's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Natural phrases users would say appear: "spending tracker", "web scraper extension", "online receipts", "without bank access". Falls short of the 5 anchor because common variations like "Chrome extension" (vs. the technical "Manifest V3"), "purchase tracker", or "order history" are missing.

4 / 5

Distinctiveness Conflict Risk

Local receipt capture without bank access is a clear niche with distinct triggers, but the trigger "Create a data-extraction tool that works without a backend or server" is broad and overlaps generic scraper/extraction skills, preventing a 5.

4 / 5

Total

17

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

NexaiGuy/nex-ai-skills

Path

skills/nex-receipt-vault/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.