CtrlK
BlogDocsLog inGet started
Tessl Logo

gmail-inbox-triage

Triage a Gmail inbox into actionable buckets such as urgent, needs reply soon, waiting, and FYI using connected Gmail data. Use when the user asks to triage the inbox, rank what needs attention, find what still needs a reply, or separate important mail from noise.

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A concise, well-structured instruction skill that gives concrete tool-driven guidance and explicit bucket heuristics with a clearly sequenced, conditionally-gated workflow. It stays lean while remaining fully actionable.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and assumes Claude's competence, with no concept explanations or filler; every section earns its tokens.

3 / 3

Actionability

Names specific tools (search_emails, batch_read_email, read_email_thread) with concrete decision rules for when to use each and explicit bucket criteria, giving actionable guidance despite the absence of code.

3 / 3

Workflow Clarity

The numbered 1-6 workflow is clearly sequenced with explicit conditional gates ('only when snippets are not enough', 'when a message appears to be part of an active conversation') plus verification caveats in the Output section.

3 / 3

Progressive Disclosure

Well-organized into Overview, Workflow, Bucket Heuristics, and Output sections, with the single external reference (../gmail/SKILL.md) clearly signaled and one level deep; no unnecessary bundle files.

3 / 3

Total

12

/

12

Passed

Description

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

A tight, third-person description that states concrete capabilities and gives explicit, natural trigger phrases for when to use the skill. It answers both 'what' and 'when' without fluff or over-claims.

DimensionReasoningScore

Specificity

Lists concrete actions and named buckets ('urgent, needs reply soon, waiting, and FYI') rather than vague language, matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what ('Triage a Gmail inbox into actionable buckets...') and when ('Use when the user asks to triage the inbox...') with explicit triggers.

3 / 3

Trigger Term Quality

Phrases like 'triage the inbox', 'rank what needs attention', 'find what still needs a reply', and 'separate important mail from noise' are natural terms a user would say, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

The Gmail inbox-triage niche with triage-specific triggers is clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
openai/plugins
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.