CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

crm-connector-development

Use this skill when creating, modifying, or debugging CRM connectors for the RingCentral App Connect extension. This includes implementing connector interfaces, handling OAuth/API key authentication, contact matching, call logging, and message logging.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 body is a dense, actionable reference: concrete interface contracts, executable code patterns, and pointers to four real example connectors, with no filler. Its main weakness is the absence of an explicit ordered workflow — no step sequence or validation/testing guidance for verifying a new connector works.

Suggestions

Add a short numbered 'Building a new connector' workflow (scaffold file → implement interfaces → test auth → test contact match → test logging) with an explicit validation step, e.g., comparing behavior against a reference connector before finishing.

Include a testing/verification section describing how to exercise the connector locally (e.g., sample request payloads or how to trigger each interface) so implementations can be checked before delivery.

Consider moving the full interface table and response-format specs into a references/ file, keeping SKILL.md as a leaner overview that links to it.

DimensionReasoningScore

Conciseness

The body is efficient and project-specific (exact paths like 'src/connectors/<crm-name>/index.js', exact imports, rate-limit header fields) with no explanation of concepts Claude already knows. A few sections (e.g., three separate response-format examples) could be tightened slightly, keeping it at the 4 anchor rather than 5.

4 / 5

Actionability

Mostly executable guidance: a concrete file scaffold with real require statements, exact response shapes, a full error-handling pattern, and four reference connectors to copy from. The '// ... implement all interfaces' placeholder keeps it just short of fully copy-paste ready, fitting the 4 anchor.

4 / 5

Workflow Clarity

The sequence for building a connector is only implicit (file structure → interface table → response formats → patterns → error handling) with no ordered steps, no testing/validation checkpoints, and no feedback loop for verifying a connector works — matching the 3 anchor ('sequence present but checkpoints missing or implicit') rather than 4. No destructive/batch cap applies.

3 / 5

Progressive Disclosure

Good structure: well-organized sections of moderate length with clearly signaled pointers to real reference implementations ('src/connectors/pipedrive/index.js - OAuth connector with deals/leads', etc.). No bundle reference files exist, so everything is inline in one file — solid but short of the clear multi-file overview pattern at 5.

4 / 5

Total

15

/

20

Passed

Description

87%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 strong example: it opens with an explicit 'Use this skill when...' trigger, names a highly specific product niche, and enumerates concrete capability areas. The only weakness is slightly incomplete action coverage (dispositions, user mapping, widget) and a few missing synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'implementing connector interfaces, handling OAuth/API key authentication, contact matching, call logging, and message logging' — but coverage has minor gaps (e.g., call dispositions, user mapping, contact widget are not mentioned), matching the 'several specific actions; minor gaps' anchor rather than the fully comprehensive 5.

4 / 5

Completeness

Explicitly answers both: what ('creating, modifying, or debugging CRM connectors... implementing connector interfaces, handling OAuth/API key authentication, contact matching, call logging, and message logging') and when ('Use this skill when creating, modifying, or debugging CRM connectors for the RingCentral App Connect extension'), with concrete trigger conditions rather than the vaguer 'when' of the 4 anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'CRM connectors', 'RingCentral App Connect', 'OAuth', 'API key', 'contact matching', 'call logging', 'message logging'. A few natural terms users might say are missing (e.g., 'integration', 'SMS logging'), so it falls just short of the comprehensive-synonyms anchor at 5.

4 / 5

Distinctiveness Conflict Risk

'CRM connectors for the RingCentral App Connect extension' carves out a clear niche with distinct, product-specific triggers; minimal risk of firing for an unrelated skill.

5 / 5

Total

18

/

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

ringcentral/rc-unified-crm-extension

Path

.agent-skills/crm-connector-development/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.