CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

connect-apps

Link a user's Slack account or add QM to the company Slack, or connect an administrator-enabled SaaS app with a one-time OAuth consent link.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 lean, highly actionable operational guide with concrete commands, explicit error handling, and clear task separation — no bundle files are needed at this size. The only refinements are cosmetic: fencing the mint command and showing how to extract the connectUrl response field.

DimensionReasoningScore

Conciseness

The body is entirely operational — API endpoints, curl commands, widget directives, and guardrails like 'Do not create a generic Composio Slack link or infer identity from matching emails' — with no explanations of concepts Claude already knows and no padding. Every token earns its place.

5 / 5

Actionability

Concrete executable guidance throughout: a fenced catalog curl with jq filtering, the consent-link mint POST with headers and payload, exact widget directives, and an admin-installation status check. Not 5 because the mint curl is prose-indented rather than fenced, and extracting 'connectUrl' from the response is described but not shown as a command.

4 / 5

Workflow Clarity

Both flows are sequenced with explicit checkpoints: Composio availability check, configured-provider filter, mint, relay URL, and error recovery ('If mint returns oauth_not_configured... Do not retry that direct OAuth path'), plus the admin installation check for Slack. Not 5 because steps are prose-ordered rather than enumerated and there is no post-connection verification step.

4 / 5

Progressive Disclosure

The skill is under 50 lines with two clear task-aligned section headers and no bundle files; its single external reference ('load the composio skill') is clearly signaled and one level deep. Per the rubric's simple-skill exception, well-organized sections alone earn a 5.

5 / 5

Total

18

/

20

Passed

Description

66%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, uses natural third-person trigger language, and carves out a distinct niche, but it omits any explicit 'Use when...' guidance, which both caps completeness and slightly limits its trigger coverage. Adding an explicit trigger clause with a few synonyms (install, integrate) would lift it to the top band.

Suggestions

Append an explicit trigger clause such as 'Use when the user asks to link or connect Slack, add QM to their Slack workspace, or connect a SaaS app/integration.'

Include common synonyms users would say — e.g., 'install', 'integrate', 'set up' — alongside 'connect' and 'add'.

Optionally mention the Composio discovery fallback so the description fully covers the skill's scope.

DimensionReasoningScore

Specificity

Lists three concrete third-person actions ('Link a user's Slack account', 'add QM to the company Slack', 'connect an administrator-enabled SaaS app with a one-time OAuth consent link') with only minor gaps such as the Composio fallback path. It exceeds the 3 anchor (1-2 actions) but lacks the comprehensive coverage of 5.

4 / 5

Completeness

The 'what' is clear (all three capabilities are named), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping this at 3 per the rubric guideline. The 'when' is only weakly implied by the action verbs.

3 / 5

Trigger Term Quality

Natural phrases users would say are present ('Link a user's Slack account', 'add QM to the company Slack', 'connect a SaaS app'), giving good keyword coverage. Not 5 because common synonyms like 'install', 'integrate', or example app names are missing.

4 / 5

Distinctiveness Conflict Risk

QM-specific terminology ('QM', 'company Slack', 'administrator-enabled SaaS app', 'OAuth consent link') makes it mostly distinct with only minor overlap risk. Not 5 because 'connect a SaaS app' is broad enough to overlap with a generic integration skill.

4 / 5

Total

15

/

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/connect-apps/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.