call-log-composition

Use this skill when working with call log composition, formatting call details, handling AI notes, transcripts, and understanding the call log flow in App Connect.

1.87x

Quality

—

Does it follow best practices?

Impact

92%

1.87x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with complete executable code and a clear call-log flow, but it is held back by missing validation checkpoints in its workflows and an inline-heavy structure that could benefit from splitting reference material into bundled files.

Suggestions

Add validation/error-recovery checkpoints to the createCallLog and getCallLog examples (e.g., check the API response status before using response.data) to support destructive or batch operations.

Move the full output-format samples and the per-function API reference into separate bundled reference files, keeping SKILL.md a concise overview with clearly signaled one-level-deep links.

Trim the static HTML/Markdown/Plain-text output blocks to a single representative example or a compact summary, reducing illustrative tokens that do not drive action.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable code and little concept lecturing, but it carries full static output-format samples (HTML/Markdown/Plain text) that are illustrative rather than action-driving and could be trimmed.	2 / 3
Actionability	Provides fully executable, copy-paste-ready code with real imports, concrete function signatures, and worked examples across all three log formats.	3 / 3
Workflow Clarity	A numbered "Call Log Flow" sequence exists, but the createCallLog/getCallLog examples perform no response validation or error-recovery checkpoints before using API results.	2 / 3
Progressive Disclosure	Sections are well-organized and no bundle files exist, but the ~215-line single file inlines extensive API reference and format samples that could be split into separate reference files for easier navigation.	2 / 3
	Total	9 / 12 Passed

Description

85%

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 concrete, scoped, and includes an explicit "Use when..." trigger, so it answers both what and when clearly. Its main weakness is trigger-term coverage, which relies on internal/product phrasing rather than the broad natural terms users would say.

Suggestions

Broaden trigger terms with natural user phrasings (e.g., "call logging", "logging calls", "call notes", "call transcripts") beyond the App Connect product name.

Keep the explicit "Use this skill when..." clause but pair it with the most common short trigger phrasings a user would actually say.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "call log composition, formatting call details, handling AI notes, transcripts" — rather than vague abstractions, matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly answers both what it does and when to use it via the "Use this skill when working with..." clause, satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	Includes some relevant natural terms ("call log", "AI notes", "transcripts") but leans on the product name "App Connect" and omits common variations a user might say, so coverage is partial rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	Scoped to App Connect call log composition, a clear niche with distinct triggers unlikely to collide with unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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
Commit: 25fc4c6

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.