CtrlK
BlogDocsLog inGet started
Tessl Logo

messaging-adapter-parity

This skill should be used when the user asks to change "Slack adapter", "Telegram adapter", "Discord adapter", "Webhook adapter", "status delivery", "message routing", or "delivery receipts". Enforces cross-adapter parity and explicit delivery semantics.

67

Quality

80%

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

78%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 concise and well-structured with a clear gated verification sequence and appropriate handoff section. Its main weakness is actionability: the verification and parity checks name what to do but not the specific commands, test paths, or comparison procedure to execute.

Suggestions

Add concrete, executable specifics to the Verification Checklist, e.g. the actual test command/path to run for an adapter and the exact command for a parity comparison check.

Add an explicit feedback loop to the verification sequence (e.g. 'If any targeted test fails, fix the adapter path and re-run before proceeding to broad gate checks').

Specify how a parity comparison is performed (which adapters to diff against and where the expected-behavior contracts live) so the check is executable rather than aspirational.

DimensionReasoningScore

Conciseness

The body is a lean ~35 lines of bullet-list contracts and checklists with no padding and no explanation of concepts Claude already knows; every line earns its place, matching the anchor-5 example.

5 / 5

Actionability

It gives concrete check items ('Run targeted tests for the touched adapter', 'Run at least one parity comparison check across adapters') but no specific test names, commands, or comparison procedures, leaving the executable specifics incomplete — anchor 3 rather than 4.

3 / 5

Workflow Clarity

The Verification Checklist provides a clear gated sequence (targeted tests -> receipt paths -> parity comparison -> broad gate checks after targeted pass); it is not 5 because there is no explicit validate/fix/retry feedback loop on failure.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no external references needed and is well-organized into clearly labeled sections (Goal, Contract Areas, Parity Checklist, Verification Checklist, Required Handoff), qualifying for 5 under the simple-skill exception.

5 / 5

Total

17

/

20

Passed

Description

82%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 strong: it explicitly states both purpose and trigger conditions with natural, niche-specific trigger phrases and uses correct third-person voice. The main weakness is that the stated actions ('enforces parity', 'explicit delivery semantics') are somewhat abstract rather than concrete verbs.

Suggestions

Replace the abstract 'Enforces cross-adapter parity and explicit delivery semantics' with concrete verbs, e.g. 'Compares behavior contracts across Slack, Telegram, Discord, and Webhook adapters and validates delivery-receipt semantics.'

Add a couple of common synonyms to the trigger list (e.g. 'adapter consistency', 'delivery acks') to broaden natural-term coverage.

DimensionReasoningScore

Specificity

Names the messaging-adapter domain and two actions ('Enforces cross-adapter parity and explicit delivery semantics'), but those actions are fairly abstract rather than concrete extract/fill/merge-style verbs, so it sits at the anchor-3 level and not 4.

3 / 5

Completeness

Explicitly answers both what ('Enforces cross-adapter parity and explicit delivery semantics') and when ('This skill should be used when the user asks to change...') with concrete trigger phrases, matching the anchor-5 example.

5 / 5

Trigger Term Quality

Quotes seven natural trigger phrases a user would literally say ('Slack adapter', 'message routing', 'delivery receipts'), giving good coverage of the niche; it is not a clear 5 because a few common synonyms/variations are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (specific named adapters and delivery semantics) with distinct triggers and minimal overlap risk with other skills, matching the anchor-5 example.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
spacedriveapp/spacebot
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.