CtrlK
BlogDocsLog inGet started
Tessl Logo

gog-inbox-triage

Gmail inbox triage with gog: prioritize unread mail, inspect safely, and prepare reply drafts.

63

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/gog-inbox-triage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 content is a tight, executable triage workflow with strong safety discipline and clear sequencing. It only misses a 5 on actionability and workflow_clarity due to placeholder substitution and the absence of an explicit error-recovery loop.

DimensionReasoningScore

Conciseness

The body is lean and efficient: terse step headers, fully-specified commands, and a compact safety note, with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Steps 1-3 give concrete, executable gog commands with all flags; minor gaps are the unsubstituted placeholders 'user@example.com' and 'THREAD_ID', and steps 4-5 are instructional rather than runnable code.

4 / 5

Workflow Clarity

A clear numbered sequence with an auth-verification checkpoint (step 1), bounded read-only search, and write-gating on step 5; lacks an explicit error-recovery feedback loop (e.g., what to do if auth fails).

4 / 5

Progressive Disclosure

Under 50 lines and well-organized into numbered steps, with one-level-deep sibling references ('Read ../gog/SKILL.md and ../gog-gmail/SKILL.md first') clearly signaled; no bundle files needed.

5 / 5

Total

18

/

20

Passed

Description

61%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 clearly states what the skill does and targets a distinct niche, but it lacks an explicit 'when to use' trigger clause and one action ('inspect safely') is vague. Adding a 'Use when...' clause would raise completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to triage, sort, or clear their Gmail inbox or deal with unread mail.'

Replace the generic 'inspect safely' with a more concrete action such as 'inspect likely-actionable threads read-only' to sharpen specificity.

Add a natural synonym like 'email' alongside 'Gmail' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Gmail inbox triage with gog') and three actions ('prioritize unread mail, inspect safely, and prepare reply drafts'), but 'inspect safely' is generic and coverage is not comprehensive (no mention of buckets, read-only safety, or draft gating).

3 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

'Gmail inbox triage', 'unread mail', and 'reply drafts' are natural phrases a user would say; a few common synonyms ('email', 'sort my inbox') are missing.

4 / 5

Distinctiveness Conflict Risk

'Gmail inbox triage with gog' carves a clear niche tied to a specific tool and task; minor overlap risk only with the sibling gog-gmail skill.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openclaw/gogcli
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.