Name: dynamics-crm
Rating: 60.8 (1 reviews)
Author: membranedev

dynamics-crm

Microsoft Dynamics 365 integration. Manage crm and sales data, records, and workflows. Use when the user wants to interact with Microsoft Dynamics 365 data.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/dynamics-crm/SKILL.md

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 highly actionable with executable commands throughout and a solid connection-state feedback loop. It loses points for explaining concepts Claude already knows and for lacking validation guidance around potentially destructive action runs.

Suggestions

Remove the introductory paragraph explaining what Dynamics 365 is and the 'competitor to Salesforce' comparison; assume Claude knows this.

Add a validation/verification checkpoint before running mutating actions (create/update/delete on records), e.g. confirming the target record or dry-running a query first.

Consider moving the proxy flag table and detailed clientAction state handling into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph explains what Dynamics 365 is and adds 'Think of it as a competitor to Salesforce', which is background Claude already knows and the rubric penalizes.	3 / 5
Actionability	It provides copy-paste-ready commands for install, auth, connection, action search/run, and proxy requests, plus a flag table, covering the common cases with executable guidance.	5 / 5
Workflow Clarity	The connection flow has an explicit polling/validation feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED), but running actions on CRM records can be destructive and the skill provides no verification step before executing them, which caps workflow clarity per the rubric.	3 / 5
Progressive Disclosure	The single-file content is well-organized into clear sections (install, auth, connecting, searching, running, proxy, best practices) with no nested references, though everything is inlined with no separate reference files for the longer detail.	4 / 5
	Total	15 / 20 Passed

Description

73%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 clearly identifies a distinct niche and includes both a 'what' and a 'when' clause with reasonable trigger terms. Its main weakness is generic action verbs ('manage') that limit specificity and completeness.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'Create, update, query, and delete CRM records, sales data, and workflows'.

Broaden the 'when' trigger with natural variations users say, e.g. 'Use when the user mentions Dynamics 365, CRM records, leads, opportunities, or sales pipelines'.

Add explicit trigger nouns like 'leads', 'opportunities', 'contacts', and 'accounts' that map to the skill's actual capabilities.

Dimension	Reasoning	Score
Specificity	It names the domain ('Microsoft Dynamics 365') and a few actions ('Manage crm and sales data, records, and workflows'), but 'manage' is generic and coverage is not comprehensive, matching the anchor for naming a domain with 1-2 concrete actions.	3 / 5
Completeness	Both 'what' (manage crm/sales data, records, workflows) and 'when' ('Use when the user wants to interact with Microsoft Dynamics 365 data') are present, but the 'when' clause is fairly generic and could be more specific.	4 / 5
Trigger Term Quality	Natural keywords like 'crm', 'sales data', 'records', 'workflows', and 'Microsoft Dynamics 365' give good coverage a user would plausibly say, though a few synonyms or variant phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	The 'Microsoft Dynamics 365' niche is clearly distinct with specific triggers, making conflict with other skills minimal.	5 / 5
	Total	16 / 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/dynamics-crm/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.