dataverse-python-usecase-builder
Generate complete solutions for specific Dataverse SDK use cases with architecture recommendations
Install with Tessl CLI
npx tessl i github:github/awesome-copilot --skill dataverse-python-usecase-builder50
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%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 identifies a specific technology domain (Dataverse SDK) but suffers from vague action language and completely lacks trigger guidance. It would benefit significantly from concrete examples of what 'complete solutions' means and explicit 'Use when...' conditions to help Claude select it appropriately.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Dataverse', 'Power Platform SDK', 'Dynamics 365 development', 'CDS plugins', or 'entity operations'
Replace 'complete solutions' with specific concrete actions such as 'create plugins, implement entity operations, configure web API calls, build custom workflows'
Include common alternative terms users might use: 'Power Platform', 'Dynamics 365', 'Common Data Service', 'CDS', '.NET SDK for Dataverse'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Dataverse SDK) and mentions 'complete solutions' and 'architecture recommendations', but lacks concrete actions like 'create plugins', 'configure entities', or 'implement CRUD operations'. | 2 / 3 |
Completeness | Describes what it does (generate solutions with architecture recommendations) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Dataverse SDK' which is a relevant technical term, but misses natural variations users might say like 'Power Platform', 'Dynamics 365', 'CDS', 'Common Data Service', or specific operations like 'plugin development'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Dataverse SDK' provides some specificity that distinguishes it from generic coding skills, but 'complete solutions' and 'architecture recommendations' are vague enough to potentially overlap with other architecture or solution design skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive framework for Dataverse SDK solution architecture but suffers from verbosity and incomplete actionability. The content would benefit from being split into a concise overview with references to detailed pattern files, and the code examples need to be either fully executable or removed in favor of references to complete implementations.
Suggestions
Split content into SKILL.md overview + separate files for patterns (PATTERNS.md), use case categories (USE_CASES.md), and complete code templates (TEMPLATES.md)
Replace placeholder code ('# Methods here', 'pass') with either complete executable examples or remove scaffolding entirely
Add explicit validation checkpoints in Phase 4 template, e.g., 'Validate connection before proceeding' and 'Test with single record before bulk operations'
Remove the 6 use case categories section entirely - Claude can infer these from context without enumeration
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful content but is verbose with extensive framework descriptions, category lists, and template scaffolding that Claude could generate on demand. The phase-by-phase breakdown and use case categories add bulk without proportional value. | 2 / 3 |
Actionability | Code examples are present but many are incomplete scaffolding (e.g., 'Methods here', 'pass' placeholders) or pseudocode-like patterns rather than fully executable implementations. The template structure shows intent but lacks copy-paste ready solutions. | 2 / 3 |
Workflow Clarity | The 5-phase framework provides clear sequencing, but validation checkpoints are missing. There's no explicit 'validate before proceeding' step, no error recovery loops, and the quality checklist at the end is a static list rather than an integrated verification workflow. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files. All content is inline including detailed category lists, multiple pattern descriptions, and extensive templates that could be split into separate reference documents. | 1 / 3 |
Total | 7 / 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.
- 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.