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.

75

Quality

94%

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

The canonical home for this skill is inbox-setup in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-sequenced interview skill: verbatim grill-me questions, skip-logic, per-section file commits, an error-handling table, and a validator gate before handoff. The weaknesses are mild duplication of content already stated elsewhere (triggers, error rows) and a main file that fronts the full question bank instead of pushing it one level down into the grill-me reference.

Suggestions

Drop the 'Invocation Triggers' section — the eight triggers are already verbatim in the frontmatter description, so this spends ~10 lines of context budget on every load for zero new information.

Trim the Error Handling rows that restate other sections ('Re-run on existing setup' duplicates Re-Run Behavior; 'Sensitive info volunteered' duplicates Privacy Boundary) to one-line pointers, keeping only rows that add new behavior.

Move the full per-section question scripts into references/grill_me_section_walk.md and keep a one-line summary per section in SKILL.md, so the main file works as an overview of the 8-section walk and the question detail loads only when needed.

DimensionReasoningScore

Conciseness

The body is disciplined — verbatim question scripts with forcing-format options and per-section Actions, no explanations of concepts Claude already knows. But there is avoidable duplication: the 8-bullet 'Invocation Triggers' list repeats the frontmatter triggers verbatim, the Error Handling rows 'Re-run on existing setup' and 'Sensitive info volunteered' restate the Re-Run Behavior and Privacy Boundary sections, and the Stop Condition re-explains the one-at-a-time rule already in Conduct Discipline. Anchor 4 fits (efficient with minor instances that could be trimmed) rather than 3 because redundancy is ~10% of the body and the rest earns its tokens.

4 / 5

Actionability

Copy-paste-ready question scripts with multi-choice options ('Run frequency: once daily / 2x daily / 3x daily / on-demand only?'), exact outputs per section ('Generate email-taxonomy.md with categories, signals... and default actions per category'), and exact commands ('Run scripts/kb_validator.py --workspace ${WORKSPACE}'). As an instruction-only skill the guidance is fully executable with no step left to improvisation, matching the anchor-5 standard.

5 / 5

Workflow Clarity

Eight dependency-ordered sections with per-section commit checkpoints ('Each section commits its file(s) before moving on'), explicit S4 skip-logic, a stop condition with a 35-question hard ceiling, an Error Handling table as recovery feedback, and a final validation gate ('Run scripts/kb_validator.py ... to confirm the 7-file contract is satisfied before final handoff'). Validation and error recovery are explicit rather than implicit, so it exceeds anchor 4.

5 / 5

Progressive Disclosure

References are well signaled and one level deep ([references/kb_file_contract.md], [references/grill_me_section_walk.md], [references/voice_calibration.md]) with a References index section. However SKILL.md is a ~215-line operational manual that inlines the entire question bank rather than acting as an overview, and no bundle directories (references/, scripts/) were provided to verify the linked files exist. Anchor 4 fits: good structure, mostly appropriate placement, minor organization gaps.

4 / 5

Total

18

/

20

Passed

Description

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

A model description: third-person, explicit what (interview topics, KB generation, grill-me mechanics), explicit when (first-run plus re-run conditions), and eight natural trigger phrases with a variation clause. The only nitpick is length — the parenthetical process detail is dense but every clause is informative rather than padded.

DimensionReasoningScore

Specificity

Concrete actions are named throughout: 'Interviews the user about their email patterns, business context, reply style, and priorities', 'generates the knowledge base files that power the companion inbox-triage skill', plus the mechanics ('one question at a time, forcing format where possible, dependency-ordered') and lifecycle ('Run this once... Re-run when business, pricing, or priorities change'). Not a 4: inputs, outputs, process, and re-run conditions are all explicitly named, leaving no minor coverage gap.

5 / 5

Completeness

What is explicit ('builds a personalized inbox triage knowledge base via interactive interview... generates the knowledge base files') and when is explicit ('Run this once before using inbox-triage for the first time. Re-run when business, pricing, or priorities change significantly.') with a concrete trigger list. Both halves answered clearly and concretely, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Eight natural quoted triggers ('set up my inbox', 'set up my email system', 'configure inbox triage', 'build my email knowledge base', 'initialize email management'...) plus 'any variation where someone wants to get the email triage system running for the first time' give comprehensive synonym coverage (set up/configure/build/initialize/onboard, inbox/email). No common first-time-setup phrasing is missing.

5 / 5

Distinctiveness Conflict Risk

A clear niche — the one-time setup half of a paired skill ('Run this once before using inbox-triage for the first time') with setup-specific triggers that won't fire for routine triage requests. The companion-skill relationship is stated, which explicitly draws the setup-vs-run boundary; conflict risk is minimal.

5 / 5

Total

20

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 7 missing

Warning

referenced_paths_exist

Referenced path issues: 19 missing

Warning

Total

14

/

16

Passed

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.