CtrlK
BlogDocsLog inGet started
Tessl Logo

protocol-quiet-in-groups

Enforces PROTOCOLS.md "stay quiet in group chats" deterministically. Blocks outbound messages in Discord/Telegram/Slack/etc group channels when the bot was not @mentioned and recently spoke.

61

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 ./skills/protocol-quiet-in-groups/SKILL.md
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 content is a compact, well-structured description of a deterministic interceptor with concrete firing conditions, priorities, and limits. The only gaps are minor: the undefined "first few turns" parameter and the unexplained relationship between the 1-in-5 heuristic and the implemented conditions.

DimensionReasoningScore

Conciseness

The body is lean with no explanation of concepts Claude already knows; every section carries information. "In group chats you will notice the agent participating less often than it would otherwise" partially restates the intro, keeping it at anchor 4 rather than the fully lean anchor 5.

4 / 5

Actionability

Guidance is concrete and specific: "not @mentioned in the last 3 turns", "has spoken within the past minute", "High priority (90)", "Up to 50 fires per session", plus an exact source file path. It misses anchor 5 only because "the first few turns of joining" is left undefined.

4 / 5

Workflow Clarity

The single action is unambiguous with explicit firing conditions and a stated bypass ("When it is directly addressed (@bitterbot or @bot), the block is bypassed"). It falls short of 5 because "first few turns" is vague and the mapping from the "speak ~1 in 5 turns" rule to the actual deterministic conditions is never reconciled.

4 / 5

Progressive Disclosure

The body is under 50 lines with no bundle files and no need for external references; sections ("What you'll see", "Implementation") are well-organized and the single source-file pointer is one level deep and clearly signaled. Per the simple-skill guideline this earns a 5.

5 / 5

Total

17

/

20

Passed

Description

67%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 specific and distinct, clearly stating what the skill does and the exact conditions under which it fires. Its main weakness is trigger-term coverage: the platform list is truncated with "etc" and it lacks the natural phrasings a user would say when they want a bot to be quieter in group chats.

Suggestions

Replace "Discord/Telegram/Slack/etc" with the full supported platform list (or a natural category phrase like "any group chat platform") so trigger matching is not left ambiguous.

Add natural trigger phrasing users would actually say, e.g. "Use when the bot is being too talkative or chatty in group chats, speaking every turn, or ignoring PROTOCOLS.md quiet rules."

State the user-visible outcome in plain language (e.g. "keeps the bot quiet in group chats unless directly @mentioned") alongside the mechanical description.

DimensionReasoningScore

Specificity

"Blocks outbound messages in Discord/Telegram/Slack/etc group channels when the bot was not @mentioned and recently spoke" names the domain and concrete actions with precise firing conditions. It lists several specifics but is a single enforcement action rather than comprehensive capability coverage, so it fits anchor 4 rather than 3 or 5.

4 / 5

Completeness

The "what" is explicit ("Blocks outbound messages in ... group channels") and "when the bot was not @mentioned and recently spoke" serves as explicit trigger guidance, satisfying the Use-when requirement. It falls short of anchor 5 because the "when" is framed as interceptor mechanics rather than concrete user-facing trigger phrases.

4 / 5

Trigger Term Quality

Natural terms like "stay quiet in group chats", "group channels", and "@mentioned" are present, but "Discord/Telegram/Slack/etc" truncates the platform list and common user phrasings ("too chatty", "talk less", "lurk") are missing. This matches anchor 3 (relevant keywords, missing common variations) rather than 4, whose coverage is broader.

3 / 5

Distinctiveness Conflict Risk

A narrow niche (group-chat quiet enforcement) with distinct triggers ("group channels", "@mentioned", "recently spoke") that few other skills would share. Minor overlap risk remains with other protocol/discipline enforcement skills, so anchor 4 rather than 5.

4 / 5

Total

15

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Bitterbot-AI/bitterbot-desktop
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.