CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-meeting-finder

Deploy a production-ready Manifest V3 extension that detects meeting links and injects Join buttons into any webpage. Use when: Deploy a fully functional "Meeting Finder" extension to the Chrome Web Store; Bootstrap a content-rewriter extension using a proven Manifest V3 template; Add platform-specific badges and buttons to any website dynamically.

Quality

56%

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-meeting-finder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

11%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 promotional landing page rather than a skill: it markets a shipped extension, but contains no instructions, no code, no workflow, and no bundle files — the advertised extension source is missing from the package entirely. Invoking this skill would leave Claude with nothing actionable to execute. The description is well written, which makes the hollow content especially misleading.

Suggestions

Include the actual extension source (manifest.json, content.js, platforms.js, popup.html, etc.) in the bundle so the promised `assets/extension/` reference resolves, and list the files with one-line descriptions so Claude knows what each contains.

Replace the marketing and FAQ sections with actionable guidance: how to scaffold the extension, how to load it in Chrome Developer Mode, how to add a new platform pattern, and the concrete steps for Web Store publishing.

Add a sequenced workflow with validation checkpoints (e.g., detect links -> inject button -> verify host-page layout is unbroken -> test on a dynamic app like Gmail), and trim the restated 'Why use this skill' / 'What you get' / FAQ padding to respect the token budget.

DimensionReasoningScore

Conciseness

The body is padded marketing copy: 'battle-tested, production-ready', a 'Why use this skill?' section, a 'What you get' section, and a six-question FAQ whose answers restate earlier sections. This matches the 'noticeably verbose; several unnecessary explanations or padded sections' anchor; not 1 because it does not explain concepts Claude already knows, it just self-promotes.

2 / 5

Actionability

There is no executable guidance anywhere: no code, no commands, and no steps — the body only describes behavior ('Scans pages for meeting links... using a robust MutationObserver') rather than instructing. The Example even claims output 'in `assets/extension/`', a path that does not exist in the bundle, which is a perfect match for the 'entirely vague; only describes rather than instructs' anchor.

1 / 5

Workflow Clarity

No sequence of operations is present; the body never tells Claude what to do when the skill is invoked, and there are no validation checkpoints of any kind. This matches the bottom anchor ('steps missing or incoherent; no sequence').

1 / 5

Progressive Disclosure

Although the body has section headers, the skill's entire payload is supposed to live in bundle files that are absent: 'A complete `/extension` directory' and '`assets/extension/`' are dangling references, and the body admits 'Scripts, extension source, and templates from the original package are not in this folder.' This matches the 'minimal structure' anchor; not 3 because the promised separate files do not exist at all, leaving the disclosure structure broken rather than merely improvable.

2 / 5

Total

6

/

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.

The description is strong: it clearly states concrete capabilities and provides an explicit multi-scenario 'Use when' clause with distinct, relevant triggers. Its main weaknesses are missing natural platform keywords (Zoom, Meet, Teams) and mildly promotional padding that keeps specificity and distinctiveness just below top marks.

DimensionReasoningScore

Specificity

Lists several concrete actions ('detects meeting links and injects Join buttons into any webpage', 'Bootstrap a content-rewriter extension using a proven Manifest V3 template', 'Add platform-specific badges and buttons'), matching the anchor for several specific actions with minor gaps. Not 5 because the actions are largely variants of a single deploy task and include promotional fluff ('production-ready', 'fully functional').

4 / 5

Completeness

Explicitly answers both what ('detects meeting links and injects Join buttons into any webpage') and when ('Use when: Deploy...; Bootstrap...; Add...') with three concrete trigger scenarios. This matches the top anchor for clearly and explicitly answering both; anchor 4's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Good keyword coverage ('meeting links', 'Join buttons', 'Chrome Web Store', 'Manifest V3', 'content-rewriter extension') that fits the 'good coverage, a few natural terms missing' anchor. Not 5 because common user phrasings like 'Zoom', 'Google Meet', 'Teams', or 'browser extension' are absent; not 3 because coverage clearly exceeds the thin single-keyword examples at that anchor.

4 / 5

Distinctiveness Conflict Risk

The core niche (meeting-link detection with Join button injection) is distinct, but the broader triggers ('Bootstrap a content-rewriter extension', 'Add platform-specific badges and buttons to any website dynamically') create minor overlap risk with generic extension-boilerplate skills, matching the 'mostly distinct; minor overlap risk' anchor rather than the minimal-conflict anchor 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-meeting-finder/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.