CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mailbox

Load to send, read or resolve repository mailbox messages and owner questions.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/mailbox/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 model of token efficiency: it assumes competence, points to one executable entry point, and pushes all protocol detail into the script and its --help. Its main weaknesses are the absence of any validation/verification guidance for destructive mailbox writes and a dense prose paragraph that obscures the helper-dependency matrix.

Suggestions

Add explicit validation checkpoints for the destructive/batch operations, e.g., "After sending, confirm the receipt line was appended; after resolving, re-read the mailbox to confirm the message is resolved".

Restructure the helper-dependency paragraph as a short list or table mapping each operation (owner questions, lane sends, hosted mail, compaction, notice attachments) to its required sibling skill.

Include one or two example `scripts/lane-mail` invocations (e.g., a send and a resolve) so common cases are copy-paste ready without opening --help first.

DimensionReasoningScore

Conciseness

Every sentence earns its place: the entry point ("Use `scripts/lane-mail`"), delegation of protocol detail to its `--help`, the helper-dependency matrix, system dependencies, and the internal writer libraries. Nothing explains concepts Claude already knows, and heavy detail is pushed to the script rather than inlined.

5 / 5

Actionability

"Use `scripts/lane-mail` to send, read and resolve repository messages. Its `--help` defines verbs, envelopes, receipts and refusal keys" gives a concrete, executable pointer, and the referenced scripts (scripts/lane-mail, scripts/lib/file-lock.sh, scripts/lib/mailbox-append.sh) all exist in the bundle. It falls short of anchor 5 because no example invocations of specific verbs are shown, leaving a minor gap beyond the single entry point.

4 / 5

Workflow Clarity

The single-entry-point framing is unambiguous, but the skill's operations include destructive/batch writes (resolving messages, compaction rewrites) and the body describes no validation or verification steps, which the rubric caps at 3. The prose dependency matrix also lacks an explicit sequence or checkpoints; it is above anchor 2 because the entry point and prerequisites are clearly stated.

3 / 5

Progressive Disclosure

The body is a lean overview that references real bundle files one level deep and delegates protocol detail to the script's own `--help` — an appropriate split verified against the actual bundle (scripts/lane-mail plus scripts/lib/*). The dense single-paragraph dependency matrix (which operations need orch vs. work alone) is a minor organization gap that a list or table would fix, keeping it below anchor 5.

4 / 5

Total

16

/

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 is concise, domain-specific, and names three concrete actions, but it completely lacks a 'when to use' trigger clause and under-represents the skill's fuller capability set. Its trigger terms are natural for the niche, with only modest overlap risk against sibling kendex skills.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user wants to send, read, or resolve repository mailbox messages or answer owner questions."

Mention the additional capabilities guarded by the orch helper (lane sends, hosted mail, compaction, notice attachments) so the description reflects the skill's real scope.

Include a synonym or two users might naturally say (e.g., "reply to", "notices") to broaden trigger coverage without adding fluff.

DimensionReasoningScore

Specificity

"send, read or resolve repository mailbox messages and owner questions" names a specific domain and three concrete actions, but omits several capabilities documented in the body (lane sends, hosted mail, compaction, notice attachments), so coverage is not comprehensive. It exceeds anchor 2 because the actions are concrete rather than generic, but the omissions go beyond the 'minor gaps' of anchor 4.

3 / 5

Completeness

The description clearly answers 'what' (send, read, resolve mailbox messages and owner questions) but contains no 'Use when...' clause or any equivalent explicit trigger guidance, which the rubric caps at 3. It is above anchor 2 because the 'what' is specific, and below anchor 4 because 'when' is entirely absent rather than just imprecise.

3 / 5

Trigger Term Quality

Terms like "mailbox messages", "owner questions", and the verbs "send", "read", "resolve" are natural phrases a user of this repository would say when needing the skill. A few natural variants are missing (e.g., "reply", "notices", "lane"), keeping it below the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"repository mailbox messages" carves out a clear niche unlikely to trigger the wrong skill, but "owner questions" overlaps with the sibling owner-question tracker skill the body itself mentions, creating minor overlap risk with a closely related skill. Not 5 because of that named overlap; not 3 because the core mailbox trigger terms are distinct.

4 / 5

Total

14

/

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

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 2 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

vanillagreencom/kendex

Path

.agents/skills/mailbox/SKILL.md

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.