10to8
10to8 integration. Manage data, records, and automate workflows. Use when the user wants to interact with 10to8 data.
68
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/10to8/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 almost entirely on the '10to8' brand name for identification while providing extremely generic capability descriptions that could apply to virtually any integration. It has proper structure with a 'Use when' clause, but the lack of domain-specific actions (scheduling, appointments, bookings) and natural trigger terms significantly weakens its utility for skill selection.
Suggestions
Replace generic phrases like 'manage data, records, and automate workflows' with concrete 10to8-specific actions such as 'schedule appointments, manage bookings, view availability, and send reminders'.
Add natural trigger terms users would say, such as 'appointments', 'bookings', 'scheduling', 'calendar', 'availability', and 'reminders' to the 'Use when' clause.
Expand the 'Use when' clause to include specific scenarios like 'Use when the user mentions 10to8, appointment scheduling, booking management, or calendar automation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The actions described ('manage data, records, and automate workflows') are extremely vague and generic. There are no concrete actions specific to 10to8, such as scheduling appointments, managing bookings, or syncing calendars. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (when the user wants to interact with 10to8 data) with an explicit 'Use when' clause. However, both are quite shallow in substance. | 3 / 3 |
Trigger Term Quality | The term '10to8' is a specific product name that users would mention, which is helpful. However, it lacks natural keywords users would say like 'appointments', 'bookings', 'scheduling', 'calendar', which are the core use cases of 10to8. | 2 / 3 |
Distinctiveness Conflict Risk | The '10to8' product name provides some distinctiveness, but 'manage data, records, and automate workflows' is so generic it could overlap with dozens of other integration skills. Without domain-specific terms like 'appointments' or 'scheduling', it's only the brand name preventing conflicts. | 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 step has concrete, executable CLI commands. Its main weaknesses are the unnecessary overview/explanation content that doesn't aid Claude's task execution, and the lack of explicit validation checkpoints in the main workflow. The popular actions table, while useful, could be better handled through progressive disclosure.
Suggestions
Remove the '10to8 Overview' entity hierarchy section and the opening paragraph explaining what 10to8 is — these add no actionable value and waste tokens.
Add explicit validation steps after key operations (e.g., verify connection succeeded with `membrane connection list --json` before proceeding to action search).
Move the popular actions table to a separate ACTIONS.md reference file and link to it from the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary content. The '10to8 Overview' section listing entity types (Appointment, Customer, Staff, etc.) adds no actionable value. The opening paragraph explaining what 10to8 is wastes tokens on information Claude can infer. However, the CLI commands and workflow sections are reasonably tight. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste-ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, and running actions. Parameter formats and flags (--json, --wait, --input) are clearly specified with concrete examples. | 3 / 3 |
Workflow Clarity | The multi-step workflows (install → authenticate → connect → search → run) are present and sequenced, but there are no explicit validation checkpoints or error-handling feedback loops for the main workflow. The action creation section does include state polling and error states, which is good, but the overall connect-and-run workflow lacks verification steps (e.g., confirming connection succeeded before proceeding). | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but the popular actions table (15 rows) and the entity overview section could be split into separate reference files. The skill is somewhat monolithic for its length. It does link to official docs, but doesn't leverage separate files for detailed reference material. | 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.