CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

engagement-inbox-manager

Use when the user asks to "triage our comments, DMs, and mentions", "draft replies to this thread", "can we repost this fan post", or "set up inbox SLAs and an escalation path"; produces a ranked triage queue with register detection (sincere / ironic / performative / parasocial, sentiment-inversion table included — "this is so bad" under a comedy register is praise), a commenter taxonomy (troll monitor-only / rager / misguided / unhappy-customer / advocate) with a response-tier ladder and per-channel SLAs, an escalation matrix ending at the crisis path, a moderation ladder plus house rules for owned spaces, and a UGC curation-and-rights mode whose dated permission entries route to the channel registry — every reply is a ranked DRAFT a human posts; nothing is ever auto-sent. Not for launch-window feedback triage — use launch-feedback-synthesizer. 评论私信提及分诊/语域识别/回复草稿/UGC授权

Quality

87%

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

81%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 well-structured operational skill with a clearly sequenced 8-step workflow, explicit validation checkpoints, and concrete file-level guidance throughout. The main gaps are repeated boundary statements that could be consolidated, missing request-format examples for the registry proposal path, and reliance on cross-repo references that are not verifiable from the skill bundle itself.

Suggestions

Consolidate the repeated never-auto-sends / registry-sole-writer guardrail (currently stated in the Scope guard, Contract, Data Sources, and Instruction 5) into one authoritative statement to save tokens.

Add a short example of the actual 'operation: propose' request payload/flags for registry-events.py and a sample receipt entry, so the proposal and receipt-binding steps are executable without consulting external files.

Move the inline commenter taxonomy, register definitions, and per-channel SLA tiers into a single bundled reference file with a clearly signaled link, reducing SKILL.md length and cross-repo reference hops.

DimensionReasoningScore

Conciseness

The body is dense with operational content and explains nothing Claude already knows, but the never-auto-send / registry-sole-writer guardrail is repeated in the Scope guard, Contract, Data Sources, and Instruction 5, and the ECHO H-item preamble is long. This fits 'minor instances of over-explanation that could be trimmed' rather than the fully lean 5 anchor, but is more efficient than the 3 anchor's unnecessary explanations.

4 / 5

Actionability

Guidance is concrete throughout — named registers and classes, exact rights statuses ('active | expired | revoked | disputed | unknown'), exact paths ('memory/events/channels.ndjson', 'memory/social/engagement-inbox-manager/YYYY-MM-DD-<topic>.md'), named scripts ('registry-events.py', 'bluesky.py'), and Quick Start prompts. It stops short of 5 because the 'operation: propose' request format and a receipt-binding example are referenced but never shown, so the guidance is not copy-paste ready.

4 / 5

Workflow Clarity

Eight clearly sequenced steps carry explicit validation checkpoints and feedback loops: 'return NEEDS_INPUT naming the exact export', 'No receipt means not replied', removal requests that stay open 'until every removal receipt exists', receipts bound to the exact reply version, a 'Done when' checklist, and an escalation stop-rule. For a batch triage operation, validation is present, so the batch cap does not apply; this matches the 5 anchor rather than the 4 anchor's implicit checkpoints.

5 / 5

Progressive Disclosure

The body is a genuine overview and the Reference Materials section clearly signals what each link provides, one reference level deep. It does not reach 5 because there are 9+ references hopping across the parent repo tree ('../../../references/...', '../../craft/...') with no local bundle files to verify against, and taxonomy/SLA detail is inlined rather than split into a reference file.

4 / 5

Total

17

/

20

Passed

Description

92%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 dense, highly specific description with exemplary quoted trigger phrases, an explicit what/when pair, and explicit boundary routing to sibling skills. Its only weakness is that a few natural entry phrases (community moderation, responding to comments) are not covered, and its length borders on over-packed.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete deliverables — 'a ranked triage queue with register detection (sincere / ironic / performative / parasocial)', 'a commenter taxonomy (troll monitor-only / rager / misguided / unhappy-customer / advocate) with a response-tier ladder and per-channel SLAs, an escalation matrix', 'a moderation ladder plus house rules', and 'a UGC curation-and-rights mode' — comprehensive coverage matching the top anchor. It exceeds the 4 anchor because action coverage is comprehensive rather than having minor gaps.

5 / 5

Completeness

It explicitly answers both questions with concrete trigger phrases: 'Use when the user asks to...' gives the when, and the full output inventory (triage queue, taxonomy, escalation matrix, moderation ladder, UGC rights mode) gives the what, plus explicit negative scope ('Not for launch-window feedback triage'). This clearly matches the 5 anchor rather than the 4 anchor's weaker 'when'.

5 / 5

Trigger Term Quality

Natural user utterances are quoted directly ('triage our comments, DMs, and mentions', 'draft replies to this thread', 'can we repost this fan post', 'set up inbox SLAs and an escalation path') alongside terms like DMs, mentions, fan post, and repost. It falls short of the 5 anchor because common phrasings such as 'respond to comments', 'moderate our community/Discord', or 'social media management' are not covered.

4 / 5

Distinctiveness Conflict Risk

A clear niche (inbox triage with register detection and UGC rights) with distinctive triggers and active deconfliction — 'Not for launch-window feedback triage — use launch-feedback-synthesizer' — minimizes conflict risk, matching the 5 anchor. It is not a 4 because overlap with sibling skills is explicitly disambiguated rather than merely minor.

5 / 5

Total

19

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 34 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

social/host/engagement-inbox-manager/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.