CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-tab-cost-ext

A production-ready Manifest V3 Chrome extension to monitor tab memory, manage resources, and gamify browser hygiene. Use when: Deploy a complete 'Nex Tab Cost' extension to the Chrome Web Store; Build memory-aware browser tools without an NPM/build step; Identify and auto-close resource-heavy idle browser tabs.

Quality

62%

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 ./plugins/nex-browser-extensions/skills/nex-tab-cost-ext/SKILL.md

The canonical home for this skill is nex-tab-cost-ext in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

25%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 brochure rather than a skill: it markets a shipped extension but contains none of the actual source, scripts, or templates it references, and offers no executable guidance for building or deploying anything. Its few redeeming parts are the features list, known limitations, and install instructions. Structurally the sections are well-labeled, but every referenced bundle path is dangling.

Suggestions

Ship the actual bundle: create assets/extension/ with the extension source (manifest.json, service worker, popup) and the heavysites.json heuristic database the body references, or remove the references and the 'not in this folder' disclaimer.

Replace the marketing copy ('Why use this skill', footer promos, and the FAQ that restates the description) with a concrete build workflow: file layout, the domain-weight/memory heuristic formula with a code snippet, and the Chrome Web Store packaging steps.

Add validation checkpoints to any workflow involving tab auto-closing (e.g., verifying tab age and excluding pinned/playing-media tabs before closing), since closing tabs is a semi-destructive batch operation.

DimensionReasoningScore

Conciseness

The body is padded with promotional material repeated three times ('Built by Nex AI' in the header note, the features section, and the footer) and a FAQ 'Questions' section that largely restates the description, plus paid-catalog marketing links.

2 / 5

Actionability

No code, commands, or build instructions appear anywhere; the only concrete items (chrome://extensions install steps, 'Green <2GB, Red >4GB' thresholds, 60-minute idle cutoff) are product specs rather than executable guidance, and the referenced 'assets/extension/' and 'heavysites.json' do not exist in the bundle.

2 / 5

Workflow Clarity

There is no workflow for the skill's core purpose: no file layout, no steps for implementing the heuristic engine, and no Chrome Web Store packaging sequence despite it being claimed as a feature; only a rough install sequence exists with no validation checkpoints.

2 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), yet the body points to 'assets/extension/' and 'heavysites.json' and admits 'Scripts, extension source, and templates from the original package are not in this folder' — navigation signals content that is not delivered.

2 / 5

Total

8

/

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 clearly states what the skill delivers and provides an explicit 'Use when:' clause with concrete, natural trigger scenarios. The main weaknesses are two vague capability phrases ('manage resources', 'gamify browser hygiene') and a few missing common trigger synonyms such as 'RAM usage' or 'tab manager'.

DimensionReasoningScore

Specificity

Lists several concrete actions ('monitor tab memory', 'Identify and auto-close resource-heavy idle browser tabs', 'Deploy... to the Chrome Web Store') but 'manage resources' and 'gamify browser hygiene' remain generic, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both 'what' (a production-ready Manifest V3 Chrome extension to monitor tab memory, manage resources, and gamify browser hygiene) and 'when' (a 'Use when:' clause with three concrete trigger scenarios), matching the top anchor's structure.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('tab memory', 'idle browser tabs', 'resource-heavy', 'Chrome Web Store', 'NPM/build step'), but common user phrasings like 'RAM usage' or 'tab manager' are missing.

4 / 5

Distinctiveness Conflict Risk

Distinctive niche markers ('Manifest V3', 'no NPM/build step', 'Chrome Web Store') minimize conflict, but 'Build memory-aware browser tools' leaves minor overlap risk with generic Chrome-extension development skills.

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

plugins/nex-browser-extensions/skills/nex-tab-cost-ext/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.