dataverse-python-quickstart
Generate Python SDK setup + CRUD + bulk + paging snippets using official patterns.
56
32%
Does it follow best practices?
Impact
100%
1.63xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/dataverse-sdk-for-python/skills/dataverse-python-quickstart/SKILL.mdQuality
Discovery
42%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 reasonably specific about the concrete actions it performs (setup, CRUD, bulk, paging snippets) but critically lacks any 'Use when...' guidance, making it incomplete for skill selection. The unspecified SDK identity ('official patterns' for what?) creates ambiguity and potential overlap with other Python SDK skills.
Suggestions
Add an explicit 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks for Python SDK code, API client setup, CRUD operations, bulk data processing, or pagination examples.'
Specify which SDK or service this skill targets (e.g., 'Stripe Python SDK', 'AWS Boto3') to reduce conflict risk and improve distinctiveness.
Include natural user-facing synonyms like 'pagination', 'batch operations', 'API client', 'code examples' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'SDK setup', 'CRUD', 'bulk', 'paging snippets', and specifies 'Python' and 'official patterns'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Describes what it does (generate Python SDK snippets) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'when' is entirely absent, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'Python SDK', 'CRUD', 'bulk', 'paging', 'snippets', but lacks common user variations (e.g., 'API client', 'pagination', 'batch operations', specific SDK names) and is somewhat jargon-heavy without specifying which SDK. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Python SDK' + 'CRUD' + 'bulk' + 'paging' narrows the domain somewhat, but 'official patterns' is vague and doesn't specify which SDK, so it could overlap with any Python SDK-related skill. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a prompt or task description than an actionable skill document. It lacks any concrete code examples, specific API patterns, or executable snippets that Claude could follow. The content tells Claude what topics to cover but doesn't provide the actual patterns, making it essentially a wish list rather than a teaching document.
Suggestions
Add complete, executable Python code examples for each operation (client setup, CRUD, bulk operations, paging) rather than just listing them as bullet points.
Structure the content with clear markdown headers (## Setup, ## CRUD Operations, ## Bulk Operations, ## Paging) and include specific method signatures and parameter details.
Add validation/verification steps, such as checking the client connection succeeded or verifying CRUD operations returned expected results.
Remove the 'You are assisting with...' preamble and convert the bullet list into concrete, copy-paste-ready code blocks with brief inline comments.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary framing ('You are assisting with...') and vague qualifiers ('optionally demonstrate'). It could be tighter by removing the preamble and focusing purely on instructions. | 2 / 3 |
Actionability | The skill provides only high-level descriptions of what to generate ('Show CRUD single-record operations', 'Show bulk create and bulk update') without any concrete code examples, executable snippets, or specific API calls. It describes rather than instructs. | 1 / 3 |
Workflow Clarity | There is no clear sequencing of steps, no validation checkpoints, and no feedback loops. The bullet points are a loose list of topics rather than a structured workflow. For SDK setup and CRUD operations, there should be explicit ordering and verification steps. | 1 / 3 |
Progressive Disclosure | The content is short and organized as a single list, which is acceptable for a simple skill. However, there are no references to supporting files, no structured sections (headers), and no navigation aids. Given no bundle files exist, the lack of structure within the single file is a minor issue. | 2 / 3 |
Total | 6 / 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.
- Repository
- github/awesome-copilot
- Commit
9b74459
- 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.