10duke
10Duke integration. Manage data, records, and automate workflows. Use when the user wants to interact with 10Duke data.
68
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 identification but fails to describe what 10Duke actually is or what specific operations the skill performs. The generic terms 'data', 'records', and 'workflows' provide almost no useful information for skill selection. While it does include an explicit 'Use when' clause, the overall lack of specificity makes it difficult for Claude to confidently select this skill over others.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Manage licensing entitlements, user permissions, and product configurations in 10Duke' instead of generic 'manage data and records'.
Include natural trigger terms users would actually say, such as specific 10Duke concepts (e.g., 'licensing', 'entitlements', 'identity management') and common user phrasings.
Briefly state what 10Duke is (e.g., 'a licensing and entitlement management platform') so Claude can match user requests even if they don't mention '10Duke' by name.
| 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 trigger clause, even though both parts are vague in substance. | 3 / 3 |
Trigger Term Quality | It includes '10Duke' as a specific trigger term which is useful for matching, but the remaining terms ('data', 'records', 'workflows') are extremely generic and wouldn't help distinguish this skill. Missing natural variations or specific 10Duke concepts users might mention. | 2 / 3 |
Distinctiveness Conflict Risk | '10Duke' as a proper noun provides some distinctiveness, but 'manage data, records, and automate workflows' is so generic it could overlap with many CRM, database, or integration skills. Only the brand name prevents a score of 1. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a functional integration skill with strong actionability — every operation has a concrete CLI command. However, it could be tighter: the introductory explanation and entity overview add little value, and the workflow would benefit from an explicit numbered sequence tying the full flow together. The structure is adequate but not optimally organized for progressive disclosure.
Suggestions
Remove or condense the introductory paragraph explaining what 10Duke is and the bare entity list — Claude doesn't need this context to execute the integration.
Add an explicit numbered end-to-end workflow (e.g., '1. Install CLI → 2. Authenticate → 3. Connect → 4. Discover actions → 5. Run action') to tie the sections together and improve workflow clarity.
Either remove the '10Duke Overview' entity list or make it actionable by linking each entity to relevant action examples or documentation.
| 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 'so you can focus on the integration logic rather than auth plumbing') but is mostly efficient. The overview section listing entities without explanation feels like filler since it doesn't provide actionable context. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, running actions with parameters. Each command includes the exact flags and syntax needed. | 3 / 3 |
Workflow Clarity | The workflow is reasonably sequenced (install → authenticate → connect → discover/create actions → run), and the action creation section includes a polling/validation loop with state checking. However, there's no explicit end-to-end numbered workflow tying these steps together, and the headless auth flow could be clearer about error recovery. | 2 / 3 |
Progressive Disclosure | The content is structured with clear headers and sections, but everything is inline in a single file. The '10Duke Overview' bullet list of entities serves no clear purpose and could either be removed or linked to detailed docs. For a skill of this length, some content (like best practices or the action creation flow) could be separated, but it's not egregiously monolithic. | 2 / 3 |
Total | 9 / 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
56d7336
- 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.