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

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 well-engineered process skill: the interview is fully scripted, the output contract is tabulated and validated, and the workflow has explicit sequencing, skip-logic, stop conditions, and error recovery. The two minor flaws are verbatim duplication of the trigger list between frontmatter and body, and a question bank that could be externalized to the existing discipline reference to slim the overview.

DimensionReasoningScore

Conciseness

The bulk of the body is skill-specific payload Claude could not derive elsewhere — verbatim interview questions with their 'Why I'm asking' rationales, the file-contract table, and script invocations — so it is largely efficient. Minor trimmable duplication exists: the 'Invocation Triggers' section repeats the frontmatter description verbatim, and 'Anti-Patterns To Reject' partially re-states the Conduct Discipline, Error Handling, and Privacy Boundary sections. This matches the score-4 anchor (efficient, minor instances that could be trimmed) rather than score 5 (every token earns its place) or score 3 (noticeably unnecessary explanation).

4 / 5

Actionability

The guidance is fully executable for an instruction-only skill: every section has its questions written out verbatim with forcing-format options ('pick the top 1–2: sales pitches / client work / internal team / newsletters / customer support / financial / other'), a concrete per-section 'Action' (e.g., 'Generate email-taxonomy.md with categories, signals … and default actions per category'), exact file outputs with required/conditional flags, and a runnable command ('Run scripts/kb_validator.py --workspace ${WORKSPACE} to confirm the 7-file contract'). This matches the score-5 anchor (specific examples covering the common cases); no key execution detail is left to inference.

5 / 5

Workflow Clarity

The 8-section process is explicitly sequenced with dependency ordering, skip-logic ('Section 4 (Evaluation Framework) is skipped entirely when Section 1 surfaced no opportunity-email category'), a hard stop condition with question ceiling ('Hard ceiling: 35 questions … never re-open it'), per-section commit checkpoints ('Each section commits its file(s) before moving on'), a final validation step before handoff, and an error-handling table with per-situation recovery behaviors. This matches the score-5 anchor (clear sequence, explicit validation steps, feedback loops, checklists); score 4 would require missing checkpoints, which are not missing.

5 / 5

Progressive Disclosure

The body is organized as an overview with three well-signaled, one-level-deep references — kb_file_contract.md (verified: the canonical 7-file contract), grill_me_section_walk.md (verified: 8-section discipline and skip-logic), and voice_calibration.md (verified: sample-based voice extraction) — all confirmed to exist and match their claimed purposes, plus a scripts table with per-script roles. It falls short of the score-5 anchor because the full inline question bank (~120 lines of interview questions) is detail that arguably belongs in grill_me_section_walk.md, making SKILL.md longer than a pure overview; this matches score 4 (good structure, most content appropriately placed, minor organization gaps) rather than score 3 (content that should be separate is inline is not pervasive here).

4 / 5

Total

18

/

20

Passed

Description

96%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 strong description: it clearly states what the skill does, when to run it (first-time setup plus re-run conditions), and provides a rich set of natural trigger phrases. The only soft spot is deliberate overlap with its companion skill's vocabulary, which is inherent to the pairing rather than a drafting flaw.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'builds a personalized inbox triage knowledge base via interactive interview', 'Interviews the user about their email patterns, business context, reply style, and priorities', and 'generates the knowledge base files that power the companion inbox-triage skill' — with comprehensive coverage of what the skill does. This matches the score-5 anchor (multiple specific concrete actions, comprehensive coverage); score 4 would require gaps in coverage that are not present.

5 / 5

Completeness

It explicitly answers both 'what' (interviews the user and generates the KB files that power inbox-triage) and 'when' ('Run this once before using inbox-triage for the first time. Re-run when business, pricing, or priorities change significantly') with concrete trigger phrases. This exactly matches the score-5 anchor; the score-4 anchor's 'when could be more explicit' criticism does not apply since the when-clause is fully explicit.

5 / 5

Trigger Term Quality

It includes eight natural trigger phrases users would actually say ('set up my inbox', 'configure inbox triage', 'set up my email system', 'build my email knowledge base', 'initialize email management', 'onboard email triage', etc.) plus a catch-all 'or any variation', giving comprehensive natural-term coverage including synonyms. This is the score-5 anchor; score 4 would require natural terms to be missing, and the synonym coverage (inbox / email system / email triage / knowledge base / email management) is thorough.

5 / 5

Distinctiveness Conflict Risk

The niche is clear — a one-time onboarding/interview skill distinct from the runtime triage companion — and the triggers are all setup-flavored. However, it is deliberately paired with 'inbox-triage', and trigger phrases like 'configure inbox triage' share vocabulary with that closely related companion skill, leaving minor overlap risk. This matches the score-4 anchor (mostly distinct, minor overlap risk with closely related skills) rather than score 5 (minimal conflict risk).

4 / 5

Total

19

/

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.

Validation — 16 / 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.