CtrlK
BlogDocsLog inGet started
Tessl Logo

inbox-triage

Process all notes in 00-Inbox/: scan, classify by content, route to correct vault location, update MOCs, extract action items, and generate a daily digest. Triggers: EN: "triage the inbox", "clean up the inbox", "sort my notes", "empty inbox", "file my notes", "process the inbox". IT: "smista l'inbox", "svuota l'inbox", "ordina le note", "triage dell'inbox", "processa l'inbox". FR: "trier la boite de réception", "vider l'inbox", "classer mes notes". ES: "clasificar la bandeja de entrada", "vaciar el inbox", "ordenar mis notas". DE: "Inbox sortieren", "Inbox leeren", "Notizen einordnen". PT: "triagem da inbox", "esvaziar a inbox", "organizar minhas notas".

68

Quality

81%

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

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

The skill is a thorough, well-structured instruction skill with clear sequencing and concrete filing rules, but it is verbose in places and lacks explicit validation/feedback loops for batch move operations, capping workflow clarity and conciseness.

Suggestions

Add an explicit validation checkpoint in Step 3 (e.g., verify all moves succeeded and wikilinks resolve before updating MOCs) to support the batch file-move operation and lift workflow_clarity.

Move the MOC format, daily digest, and post-it templates into separate reference files under references/ and link to them, reducing inline length and improving progressive_disclosure.

Tighten repeated Architect-handoff guidance between the Inter-Agent Coordination and Conflict Resolution sections to remove redundancy and improve conciseness.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence, but several sections repeat guidance (e.g., Architect handoff appears in both Inter-Agent Coordination and Conflict Resolution) and example templates add length that could be tightened.

2 / 3

Actionability

Guidance is concrete in places (frontmatter field changes, exact token defaults, wikilink formats), but routing examples use non-executable template placeholders like {{YYYY}}/{{MM}}/{{Project Name}} rather than fully concrete, copy-paste-ready instructions.

2 / 3

Workflow Clarity

The six-step triage workflow is clearly sequenced with checklists, but batch move operations across the vault lack an explicit validate-then-confirm feedback loop, and the rubric caps batch/destructive operations at 2 when validation checkpoints are missing.

2 / 3

Progressive Disclosure

Content is well-sectioned and points to two one-level-deep platform references (agent-orchestration.md, agents-registry.md), but large MOC/digest/post-it templates live inline rather than in separate reference files, and no bundle files exist to offload detail.

2 / 3

Total

8

/

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 strong, specific description that names concrete actions, gives explicit trigger terms in six languages, and answers both what and when. It is concise and avoids fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — scan, classify, route, update MOCs, extract action items, generate daily digest — against a specific target (00-Inbox/), matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers both 'what' (scan, classify, route, update MOCs, extract action items, daily digest) and 'when' via an explicit 'Triggers:' clause, satisfying the top anchor.

3 / 3

Trigger Term Quality

Provides extensive natural trigger phrases across six languages ('triage the inbox', 'empty inbox', 'sort my notes', etc.), covering the common variations a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The narrow Obsidian-vault inbox-triage niche with multilingual trigger phrases is clearly distinguishable from other skills and unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

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
gnekt/My-Brain-Is-Full-Crew
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.