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.
64
76%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent-skills/crm-connector-development/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies its niche (RingCentral App Connect CRM connectors), lists specific capabilities, and provides explicit trigger conditions. The only minor issue is the use of second-person-adjacent phrasing ('Use this skill when') rather than third-person declarative voice, though this is a common and acceptable pattern for trigger guidance. The description would be nearly indistinguishable from the rubric's ideal examples.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating/modifying/debugging CRM connectors, implementing connector interfaces, handling OAuth/API key authentication, contact matching, call logging, and message logging. | 3 / 3 |
Completeness | Clearly answers both what (implementing connector interfaces, handling OAuth/API key auth, contact matching, call/message logging) and when ('when creating, modifying, or debugging CRM connectors for the RingCentral App Connect extension'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'CRM connectors', 'RingCentral', 'App Connect', 'OAuth', 'API key authentication', 'contact matching', 'call logging', 'message logging'. These are terms a developer working in this domain would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: RingCentral App Connect CRM connectors. The combination of product name, extension name, and specific integration tasks makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
52%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides excellent actionable reference material with concrete, executable code examples and clear response format specifications. However, it lacks a workflow for actually building or modifying a connector end-to-end, with no sequencing, validation steps, or testing guidance. The content is moderately well-organized but could benefit from better progressive disclosure by splitting detailed patterns into separate files.
Suggestions
Add a step-by-step workflow section (e.g., '## Creating a New Connector') with explicit steps: copy template → implement required interfaces → test contact matching → test call logging → validate all response formats → register connector.
Include validation/testing checkpoints such as how to verify a connector works (e.g., test commands, expected outputs, common failure modes to check for).
Split detailed patterns (User Assignment, Rate Limit Tracking, Error Handling) into a separate PATTERNS.md reference file and link from the main skill to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good use of tables and code blocks, but some sections could be tightened. The interface table is useful but the parameter lists are verbose. The user assignment pattern and some boilerplate code sections are lengthy but provide necessary context for a complex domain. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples for every major pattern: connector structure, response formats, user assignment, rate limit tracking, phone number handling, and error handling. The interface table with exact function signatures and parameters is highly concrete. | 3 / 3 |
Workflow Clarity | There is no clear sequenced workflow for creating a new connector from start to finish. The content presents reference patterns but lacks a step-by-step process with validation checkpoints. For a task involving creating/modifying connectors (which are multi-step, potentially error-prone operations), there's no guidance on testing, validation, or verification steps. | 1 / 3 |
Progressive Disclosure | The content references four example connectors at the bottom which is good for navigation, but the main body is a long monolithic document that could benefit from splitting detailed patterns (user assignment, error handling) into separate reference files. The structure uses headers well but everything is inline. | 2 / 3 |
Total | 8 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
f59d4a2
Table of Contents
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.