CtrlK
BlogDocsLog inGet started
Tessl Logo

inbox-setup

One-time setup skill that builds a personalized inbox triage knowledge base via interactive interview. Interviews the user about their email patterns, business context, reply style, and priorities using grill-me discipline (one question at a time, forcing format where possible, dependency-ordered, each question explains why I'm asking), then generates the knowledge base files that power the companion 'inbox-triage' skill. Run this once before using inbox-triage for the first time. Re-run when business, pricing, or priorities change significantly. Triggers: 'set up my inbox', 'configure inbox triage', 'set up my email system', 'configure email triage', 'build my email knowledge base', 'initialize email management', 'set up inbox triage', 'onboard email triage', or any variation where someone wants to get the email triage system running for the first time.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

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 body is a tightly structured, highly actionable 8-section interview workflow with explicit questions, per-section file actions, real referenced bundle files, error handling, and a final validation checkpoint. Its only real weaknesses are mild redundancy (re-listed triggers, repeated grill-me framing) and an end-only rather than per-step validation loop.

Suggestions

Remove the duplicate 'Invocation Triggers' list in the body since the same triggers already appear in the frontmatter description, or keep only the body version and trim the frontmatter list.

Add a brief per-section validate→fix→retry note (e.g., after each 'Action:' step, re-run the relevant validator) to lift workflow_clarity from 4 to 5.

De-duplicate the grill-me discipline statement so it is stated once and referenced thereafter.

DimensionReasoningScore

Conciseness

Largely lean and actionable, but the body re-lists the invocation triggers already present in the frontmatter and restates the grill-me discipline in multiple places; not 5 because of that duplicated trigger list and repeated grill-me framing, and not 3 because the bulk is concrete, non-padded content.

4 / 5

Actionability

Fully executable: each section provides copy-paste-ready interview questions with forcing formats and explicit per-section 'Action:' file-generation steps, plus three named scripts (kb_validator.py, voice_sample_analyzer.py, section_progress_tracker.py) with defined roles, matching the 5-anchor example.

5 / 5

Workflow Clarity

Clear 8-section sequence with commit-per-section checkpoints, explicit skip-logic, a stop condition (~25–31 questions, hard ceiling 35), and a final kb_validator checkpoint; not 5 because validation is end-only with no explicit validate→fix→retry loop, and not 3 because validation is present (so the batch/destructive cap does not apply).

4 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references to three real reference files (kb_file_contract.md, grill_me_section_walk.md, voice_calibration.md) and three scripts, with detail appropriately split out and easy navigation; matches the 5-anchor example, and the referenced bundle files all exist.

5 / 5

Total

18

/

20

Passed

Description

86%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 names concrete actions, answers both what and when with explicit trigger phrases, and carves a distinct one-time-setup niche. The main weakness is the embedded first-person 'I'm asking' phrasing, which violates the third-person-voice guideline and costs a specificity point.

Suggestions

Rewrite 'each question explains why I'm asking' in third person (e.g., 'each question explains why it is being asked') to comply with the third-person-voice guideline and recover the specificity point.

Tighten the 'what' clause so the two overlapping actions ('builds a ... knowledge base' and 'generates the knowledge base files') read as one comprehensive action list rather than a near-repeat.

DimensionReasoningScore

Specificity

Lists several concrete actions ('builds a personalized inbox triage knowledge base', 'Interviews the user', 'generates the knowledge base files') but the embedded first-person phrase 'each question explains why I'm asking' triggers the rubric's first-person penalty, reducing the base of 4 by one.

3 / 5

Completeness

Explicitly answers both 'what' (interviews the user and generates the 7-file knowledge base) and 'when' ('Run this once before using inbox-triage', 'Re-run when business, pricing, or priorities change significantly', plus an explicit Triggers list), matching the 5-anchor example.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural trigger phrases users would actually say ('set up my inbox', 'configure inbox triage', 'set up my email system', 'build my email knowledge base', 'onboard email triage') plus a catch-all variation clause, matching the 5-anchor example.

5 / 5

Distinctiveness Conflict Risk

Clear niche (one-time onboarding/setup) with distinct setup-oriented triggers and explicit pairing with the companion 'inbox-triage' skill, but minor overlap risk with that closely related skill's triggers; not a 5 because the inbox/email domain is shared.

4 / 5

Total

17

/

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
alirezarezvani/claude-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.