10duke
10Duke integration. Manage data, records, and automate workflows. Use when the user wants to interact with 10Duke data.
58
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/10duke/SKILL.mdQuality
Discovery
57%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 relies heavily on the '10Duke' brand name for differentiation but fails to describe what 10Duke actually is or what specific capabilities the skill provides. The actions listed (manage data, records, automate workflows) are generic boilerplate that could apply to virtually any integration. While it does include an explicit 'Use when' clause, the overall lack of specificity makes it difficult for Claude to confidently select this skill in a crowded skill set.
Suggestions
Replace generic terms like 'manage data, records, and automate workflows' with specific 10Duke capabilities (e.g., 'manage software licensing, entitlements, user identity, and access control').
Add specific trigger terms users would naturally say, such as 'license management', 'entitlements', 'identity provider', or whatever 10Duke's domain-specific concepts are.
Briefly state what 10Duke is (e.g., 'a licensing and entitlement management platform') so Claude can match it even if the user describes the need without naming 10Duke directly.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying any concrete actions. It doesn't explain what kind of data, what records, or what workflows are involved with 10Duke. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with 10Duke data), with an explicit 'Use when...' clause. However, both parts are quite shallow. | 3 / 3 |
Trigger Term Quality | It includes '10Duke' as a specific trigger term which is useful for matching, but 'data', 'records', and 'workflows' are overly generic terms that could apply to dozens of integrations. Missing natural variations or specific 10Duke concepts (e.g., licensing, entitlements, identity management). | 2 / 3 |
Distinctiveness Conflict Risk | '10Duke' as a proper noun provides some distinctiveness, but 'manage data, records, and automate workflows' is extremely generic and could overlap with any CRM, database, or integration skill. Only the '10Duke' name prevents a score of 1. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid integration skill with excellent actionability — every operation has concrete, executable CLI commands. The workflow for connection setup is well-structured with explicit state handling and error recovery paths. The main weaknesses are minor verbosity (introductory explanations, some filler in best practices) and the monolithic structure that could benefit from splitting detailed reference material into separate files.
Suggestions
Remove the introductory sentence explaining what 10Duke is ('It's used by software vendors...') — Claude doesn't need this context to execute the integration.
Consider extracting the proxy request flags table and CLIENT_ACTION_REQUIRED details into a separate reference file to keep the main skill leaner.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content includes some unnecessary explanation (e.g., 'It's used by software vendors and technology companies to manage and control access to their products and services') and the overview section listing entities without context adds little value. The best practices section has some filler ('This will burn less tokens and make communication more secure'). However, most of the content is reasonably efficient. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear flag documentation and parameter examples. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors), polling instructions, and conditional branching. The authentication flow handles both interactive and headless environments with clear fallback steps. | 3 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear sections, but it's a monolithic file with no references to supporting documents. The proxy request options table and detailed CLIENT_ACTION_REQUIRED handling could be split into separate reference files. However, given no bundle files exist, the inline approach is acceptable but not optimal. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- membranedev/application-skills
- Commit
f484c82
- 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.