CtrlK
BlogDocsLog inGet started
Tessl Logo

cursor-tab-completion

Master Cursor Tab autocomplete, ghost text, and AI code suggestions. Triggers on "cursor completion", "cursor tab", "cursor suggestions", "cursor autocomplete", "cursor ghost text", "cursor copilot".

55

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 ./plugins/saas-packs/cursor-pack/skills/cursor-tab-completion/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

55%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-organized and clear for a simple advisory skill, but it is verbose in places and presents illustrative ghost-text demos rather than executable guidance. Its biggest weakness is progressive disclosure: four reference files exist but none are linked or signaled from the body, leaving the content as a monolithic overview.

Suggestions

Link the existing bundle files from the relevant body sections (e.g. point the 'Tips for Better Suggestions' section to references/best-practices.md, the patterns list to references/completion-patterns.md, the troubleshooting text to references/errors.md, and the examples to references/examples.md) to move from a monolith to signaled one-level-deep references.

Cut explanatory prose Claude already knows (the 'You type code in the editor' walkthrough and 'Tab quality depends heavily on available context' lead-in) to tighten conciseness toward 3.

Replace illustrative ghost-text demo blocks with actionable steps or short executable snippets (e.g. the exact settings JSON or keybinding override commands) to lift actionability toward 3.

DimensionReasoningScore

Conciseness

Mostly efficient with good tables and short code blocks, but it re-explains things Claude already knows (e.g. 'You type code in the editor... Cursor's model predicts what comes next') and includes padded prose like 'Tab quality depends heavily on available context', placing it at the score-2 'mostly efficient but could be tightened' anchor rather than the lean score-3.

2 / 3

Actionability

It gives specific keybindings and settings paths, but the code blocks are illustrative comments/ghost-text demos rather than executable commands, and guidance like 'Write descriptive function names and type signatures first' is direction without copy-paste-ready steps; this matches score-2 'some concrete guidance but incomplete' rather than fully executable score-3.

2 / 3

Workflow Clarity

For a single-purpose advisory skill the single action is unambiguous, and the sections that do describe sequences (How Tab Works, Conflict Resolution) are clearly numbered/ordered with explicit remediation steps, satisfying the scoring_note that simple skills can score 3 when content is clear and well-organized.

3 / 3

Progressive Disclosure

The body is a near-monolithic ~130-line overview with no links to the four existing bundle files in references/ (best-practices.md, completion-patterns.md, examples.md, errors.md), and a Resources section only points to external URLs; per the judging guideline to score against the actual bundle structure, this is a disconnected monolith matching the score-1 'monolithic wall of text' anchor.

1 / 3

Total

8

/

12

Passed

Description

72%Weight 40%Scale 1-3

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 has strong, natural trigger-term coverage and a clear niche, but it is padded with awkward line breaks and lists UI artifacts rather than concrete actions. It lacks an explicit 'Use when...' clause, so completeness is capped at 2 even though the 'Triggers on' keyword list gives a partial when-signal.

Suggestions

Convert the 'Triggers on ...' keyword list into an explicit 'Use when the user asks about Cursor Tab, autocomplete, ghost text, or AI code suggestions' clause to satisfy the completeness dimension.

Reword the capability list around actions rather than artifacts (e.g. 'Accept, reject, and partially accept inline AI code completions; configure Cursor Tab settings; resolve completion-key conflicts') to lift specificity to 3.

Collapse the multi-line description into a single tight sentence-plus-trigger clause to remove the broken formatting and reduce verbosity.

DimensionReasoningScore

Specificity

Names the domain and several concrete surface features ("autocomplete, ghost text, and AI code suggestions") but does not list distinct actions a user would perform; it enumerates UI artifacts more than capabilities, so it falls short of the score-3 'multiple specific concrete actions' anchor.

2 / 3

Completeness

It clearly states what the skill covers ("Master Cursor Tab autocomplete, ghost text, and AI code suggestions") but provides only the bare word 'Triggers on' followed by a keyword list rather than an explicit 'Use when...' clause describing when Claude should invoke it; per the rubric a missing explicit Use-when clause caps completeness at 2.

2 / 3

Trigger Term Quality

Good coverage of natural phrasings a user would actually say ("cursor completion", "cursor tab", "cursor suggestions", "cursor autocomplete", "cursor ghost text", "cursor copilot"), matching the score-3 'good coverage of natural terms' anchor.

3 / 3

Distinctiveness Conflict Risk

The trigger terms are tightly scoped to Cursor's Tab feature and unlikely to fire for generic code-completion skills, matching the score-3 'clear niche with distinct triggers; unlikely to conflict' anchor.

3 / 3

Total

10

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.