CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

ai-ecoverse/advanced-skills

Quarantined high-risk skills (browser session capture, WebSocket interception) for Slack and Microsoft Teams. Install only after reviewing the security implications.

Quality

96%

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

Overview
Quality
Evals
Security
Files

Quality

Content

92%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.

An unusually strong CLI reference: fully executable examples, explicit validation loops around every destructive or batch operation, and a clean one-level-deep reference structure with all cited files present. The only weakness is sheer inline length, with a few illustrative blocks that could be tightened without losing information.

DimensionReasoningScore

Conciseness

The body is dense command/flag/example reference with essentially no explanation of concepts Claude already knows, but at 746 lines there are minor trims available (four sample users under 'slack find', full sample output blocks, repeated error-handling prose across react/unreact). It fits 'efficient; minor instances of over-explanation that could be trimmed' better than the lean-every-token-earns-its-place anchor.

4 / 5

Actionability

Every command is documented with exact syntax, flags, copy-paste-ready invocations, and expected output (e.g. the ts-capture sed pipeline for thread posting, jq pipelines over --json output), matching the fully-executable anchor with common cases covered.

5 / 5

Workflow Clarity

Multi-step flows carry explicit validation and error recovery: approve/deny includes a re-list verification step plus expired-button recovery guidance, admin writes are dry-run by default with --confirm and read-back, and the U000000BOGUS0 trick verifies auth without side effects. Destructive operations all have checkpoints, so the validation cap does not apply.

5 / 5

Progressive Disclosure

The body is an overview-plus-usage reference that offloads internals to six one-level-deep reference files (endpoints.md, watch-architecture.md, jsh-host.md, support-portal.md, app-manifest.md, enterprise-grid.md), all present on disk, each annotated in a References section and cited inline down to named sections. Navigation is easy and the split is appropriate, matching the top anchor.

5 / 5

Total

19

/

20

Passed

Description

100%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 a model example: it enumerates concrete capabilities, includes an explicit 'Use when...' clause with concrete triggers, and lists natural trigger terms including product-specific synonyms. Its only cost is length, but every clause carries information for a four-command tool family.

DimensionReasoningScore

Specificity

The description lists ten-plus concrete actions ('read and post Slack messages, add or remove emoji reactions, search messages and channels, read threads, look up users by name or email, view the activity feed, and watch channels, running a command for each new message') covering the tool's full surface, matching the comprehensive-coverage anchor rather than the 'minor gaps' level below.

5 / 5

Completeness

It explicitly answers both what (the full action list) and when ('Use when the user wants to check, post, react to or search Slack messages, watch a channel or thread, or file or follow up a Slack support ticket') with concrete trigger phrases, the top anchor.

5 / 5

Trigger Term Quality

'Triggers on Slack, channels, DMs, threads, @mentions, reactions, Slackbot, notifications, Slack support, help request, support case, Salesforce Help, Fin, Intercom' covers the natural phrases a user would say plus product-specific synonyms, matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

Terms like 'Slackbot', 'Slack support', 'Salesforce Help', 'Fin' carve a clear niche with minimal conflict risk; 'channels' and 'notifications' are slightly generic but firmly scoped to the Slack domain, so it fits the clear-niche anchor rather than the minor-overlap level.

5 / 5

Total

20

/

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

skill_md_line_count

SKILL.md is long (747 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Reviewed

On this page