CtrlK
BlogDocsLog inGet started
Tessl Logo

messages-ops

Evidence-first live messaging workflow for ECC. Use when the user wants to read texts or DMs, recover a recent one-time code, inspect a thread before replying, or prove which message source was actually checked.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

The canonical home for this skill is tdg-personal/messages-ops

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 compact, well-structured instruction skill with a clear workflow, explicit guardrails, and a concrete output template. It is token-efficient and actionable; the main room for improvement is formalizing a retry/escalation feedback loop for blocked surfaces and tightening the verification into an explicit validation step.

Suggestions

Add an explicit validate-then-retry-or-escalate feedback loop in the Guardrails/Workflow for blocked auth paths (e.g., 'if blocked, surface the exact blocker; do not retry blindly'), so the recovery path is formalized rather than implied.

In the Verification section, frame the checks as a numbered checklist that mirrors the Workflow steps so the validation checkpoint is unambiguous.

Consider a one-line 'Scope boundary' note distinguishing retrieval/inspection from outbound drafting to make the handoff to email-ops / connections-optimizer even more explicit.

DimensionReasoningScore

Conciseness

Lean, bullet-driven body that assumes Claude's competence; no padding, no explanations of basic concepts, and every section earns its place.

5 / 5

Actionability

Provides concrete, executable guidance — a numbered workflow, guardrails, and a copy-paste output-format template — with minor gaps (no executable code, but the skill is instruction-only and the guidance is actionable).

4 / 5

Workflow Clarity

A clear four-step sequence with an explicit Verification checklist; the retrieve/inspect task is largely non-destructive, and most checkpoints are present, though an explicit validate-and-retry feedback loop for blocked auth paths is implied rather than formalized.

4 / 5

Progressive Disclosure

Well-organized into clearly labeled sections (When to Use, Guardrails, Workflow, Output Format, Pitfalls, Verification) with one-level-deep inline cross-references to sibling skills; no bundle files are present or needed, so organization is the main signal.

4 / 5

Total

17

/

20

Passed

Description

87%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 well-crafted description that states concrete capabilities, natural trigger phrases, and explicit when-to-use guidance while carving out a distinct messaging niche. Minor room for more synonyms and surface extensions, but it clearly answers what and when.

DimensionReasoningScore

Specificity

Names the domain and multiple concrete actions ('read texts or DMs, recover a recent one-time code, inspect a thread before replying, or prove which message source was actually checked'), with minor coverage gaps versus a fully comprehensive list.

4 / 5

Completeness

Explicitly answers both what ('Evidence-first live messaging workflow for ECC') and when ('Use when the user wants to read texts or DMs, recover a recent one-time code...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('read texts', 'DMs', 'one-time code', 'inspect a thread') with good coverage, though a few common synonyms or surface names are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (live messaging) with distinct triggers and minimal conflict risk; the 'this is not email work' boundary is reinforced in the body via email-ops.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.