Name: cdr-platform
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

cdr-platform

CDR Platform integration. Manage data, records, and automate workflows. Use when the user wants to interact with CDR Platform data.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/cdr-platform/SKILL.md

Quality

Content

61%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 reasonably actionable and well-structured CLI integration guide, but it is undermined by an injected LLM-refusal paragraph, broken step numbering, and a lack of validation for a destructive purchase action. Removing the stray paragraph and adding explicit checkpoints would materially raise workflow clarity and conciseness.

Suggestions

Delete the spurious opening paragraph ('I don't have enough information to do that. I'm a large language model...'); it is irrelevant noise that hurts conciseness and misleads.

Fix the workflow numbering: label a 'Step 1' / 'Step 2' sequence consistently and remove the dangling 'skip to Step 2' reference and the '1b' header with no '1a'.

Add a validation/confirmation checkpoint before destructive or money-spending actions like 'purchase-cdr' (e.g. confirm the calculated price and quantity with the user before running the purchase action).

Dimension	Reasoning	Score
Conciseness	The bulk is lean CLI examples and tables, but the body opens with an irrelevant LLM-refusal paragraph ('I don't have enough information to do that. I'm a large language model...') that wastes tokens and adds nothing Claude needs, matching anchor 3's 'includes some unnecessary explanation' rather than the lean anchor 4.	3 / 5
Actionability	It provides copy-paste-ready commands (install, login, connection ensure, action list/run, request) with a flag table and real action keys, but uses generic placeholders (CONNECTION_ID, <actionId>) without a complete end-to-end worked example, fitting anchor 4 instead of fully-executable anchor 5.	4 / 5
Workflow Clarity	The install→login→connect→poll→search→run sequence is present, but step numbering is broken ('skip to Step 2' with no Step 1/2 labeled, a '1b' with no '1a') and the money-spending 'purchase-cdr' action has no validation checkpoint; per the rubric, a destructive action without validation caps this at 3.	3 / 5
Progressive Disclosure	As a single-file skill with no external bundle files, it is organized into clearly labeled sections (Overview, Install, Auth, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references, fitting anchor 4's 'good structure' with only minor organization gaps like the broken step numbering.	4 / 5
	Total	14 / 20 Passed

Description

62%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 cleanly answers both what the skill does and when to use it with a clear niche, but its action verbs are generic and the trigger terms lack synonyms. Tightening 'manage' into specific operations and broadening trigger keywords would raise specificity and trigger quality.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete operations (e.g. 'Search and retrieve CDR records, run certificate and purchase actions, automate workflows').

Broaden the trigger clause to include natural synonyms users say, e.g. 'Use when the user wants to query CDR cases, records, or certificates, or automate CDR Platform workflows.'

Add the file/record-specific terms (cases, certificates, CDR purchases) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('CDR Platform integration') plus a couple of actions ('Manage data, records, and automate workflows'), but the verbs 'manage' are generic rather than the concrete, specific actions (e.g. extract/fill/merge) the anchor-4 example shows, so it lands at anchor 3 and not above.	3 / 5
Completeness	It has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with CDR Platform data'), but the trigger could be more specific, fitting anchor 4 rather than the fully concrete anchor 5.	4 / 5
Trigger Term Quality	The single trigger phrase 'interact with CDR Platform data' is relevant but the description misses common variations or synonyms a user might say (cases, records, certificates), matching anchor 3 rather than the broader coverage of anchor 4.	3 / 5
Distinctiveness Conflict Risk	'CDR Platform integration' is a clear, named niche with a distinct trigger, giving minimal conflict risk, though the generic 'manage data, records' phrasing leaves minor overlap with other data skills, placing it at anchor 4 instead of 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/cdr-platform/SKILL.md
Commit: f484c82

Reviewed: 4 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.