CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

composio

Show the app connection picker or setup widget when users ask to connect apps, reopen setup, or need an app that isn't connected yet. Use QM’s authenticated backend for app discovery, consent, and execution without exposing project keys.

Quality

88%

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

88%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 excellent instruction-heavy skill body: executable code, verbatim UI directives, exact endpoints and error semantics, and workflows with genuine validation checkpoints and recovery loops. The only real improvements are marginal tightening of repeated Slack guidance and potentially splitting app-specific tips into reference files.

DimensionReasoningScore

Conciseness

The body is dense with QM-specific operational detail ("an absent sandbox API key is expected", "Inspect successful and error, not just the HTTP status") and explains nothing Claude already knows. Minor trimming is possible — Slack linking guidance is repeated in both the connect section and step 3, and a few cross-references ("the connect option above") could be consolidated.

4 / 5

Actionability

The `apps()` fetch helper is complete and copy-paste ready, directives are given verbatim (`::connect-apps{}`, `::add-to-slack{}`), and error handling is exact ("`409 choose_account` lists matching connections: ask which, then pass `accountId`"). Concrete steps 1-5 with executable calls cover the common cases.

5 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with explicit validation checkpoints ("only claim success once the returned account ID is listed", "remove the old one with apps(\"disconnect\", {accountId}), never before") and error-recovery feedback loops (on 502, read `cause`/`providerStatus` and "back off and shrink the page rather than repeating the same request"). Destructive and batch operations (disconnect, bulk reads) all carry validation, so the cap at 3 does not apply.

5 / 5

Progressive Disclosure

Sections are well-organized and easy to navigate (scenario-based headers, a routing table for app-specific skills), and with no bundle files there are no broken or nested references. At ~117 lines it exceeds the under-50-line simple-skill case, and app-specific content (Gmail drafting, X image upload, Slack flows) is inlined where it could arguably be split into reference files.

4 / 5

Total

18

/

20

Passed

Description

83%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 strong description: it states concrete capabilities in third person and gives an explicit, natural-language trigger clause covering connect, reconnect, and missing-app cases. The only weaknesses are slightly incomplete capability coverage and a few missing trigger synonyms.

DimensionReasoningScore

Specificity

"Show the app connection picker or setup widget" and "app discovery, consent, and execution without exposing project keys" name several concrete actions with minor gaps (reconnect/disconnect and Slack-specific flows are not surfaced). It exceeds the 1-2-action anchor but is not comprehensive coverage.

4 / 5

Completeness

It explicitly answers both: what ("Show the app connection picker or setup widget... Use QM's authenticated backend for app discovery, consent, and execution") and when ("when users ask to connect apps, reopen setup, or need an app that isn't connected yet") with three concrete trigger conditions. The 'when' is fully explicit, so the anchor-4 caveat ('when could be more explicit') does not apply.

5 / 5

Trigger Term Quality

"connect apps", "reopen setup", and "need an app that isn't connected" are phrases users would naturally say. A few natural variants are missing (e.g., "integrations", "link account", specific app names like Slack or Gmail), so it falls just short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"QM's authenticated backend" and the connection/consent scope carve a clear niche with distinct triggers. Minor overlap risk remains with closely related app-specific skills (gmail, zoom, linear) that operate over the same connected apps.

4 / 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

yc-software/qm

Path

skills-seed/composio/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.