10to8
10to8 integration. Manage data, records, and automate workflows. Use when the user wants to interact with 10to8 data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill 10to871
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
52%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 follows the correct structure with both 'what' and 'when' clauses, but fails to communicate what 10to8 actually is (an appointment scheduling platform). The generic language around 'data, records, and workflows' could apply to almost any integration, and the lack of domain-specific trigger terms means users asking about scheduling or appointments won't find this skill.
Suggestions
Add domain-specific trigger terms that users would naturally say: 'appointments', 'scheduling', 'bookings', 'calendar management', 'client bookings'
Replace generic actions with 10to8-specific capabilities: 'Schedule appointments, manage client bookings, send appointment reminders, sync calendars'
Expand the 'Use when' clause to include natural phrases: 'Use when the user mentions appointments, scheduling, bookings, or 10to8'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (10to8 integration) and mentions general actions ('Manage data, records, and automate workflows'), but these actions are generic and not specific to what 10to8 actually does (appointment scheduling). No concrete actions like 'book appointments', 'manage calendars', or 'send reminders' are listed. | 2 / 3 |
Completeness | Has explicit 'what' (manage data, records, automate workflows) and explicit 'when' clause ('Use when the user wants to interact with 10to8 data'). Both components are present, though the content itself is generic. | 3 / 3 |
Trigger Term Quality | Only includes '10to8' as a trigger term. Missing natural keywords users would say like 'appointments', 'scheduling', 'bookings', 'calendar', or 'reminders'. Users unfamiliar with the product name would never trigger this skill. | 1 / 3 |
Distinctiveness Conflict Risk | The '10to8' brand name provides some distinctiveness, but 'manage data, records, and automate workflows' is extremely generic and could overlap with dozens of other integration skills. Without scheduling-specific language, it's not clearly distinguishable. | 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 - all CLI commands are executable and well-documented. The workflow for connecting and using 10to8 is clear. However, the skill includes some unnecessary context (product description, entity hierarchy overview) that doesn't help Claude perform tasks, and could be trimmed for better token efficiency.
Suggestions
Remove the introductory sentence about what 10to8 is used for - Claude doesn't need this context to perform integration tasks
Remove or significantly condense the '10to8 Overview' entity hierarchy section - it provides no actionable guidance and the entity names are self-explanatory
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary explanation (e.g., 'It's used by businesses of all sizes to manage bookings, send automated reminders, and process payments' is context Claude doesn't need). The overview section listing entities without actionable context adds little value. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax examples. Commands are copy-paste ready with proper flags and JSON output options. The action table with keys and descriptions enables immediate use. | 3 / 3 |
Workflow Clarity | Clear sequential workflows for setup, connecting, and running actions. Steps are numbered and logically ordered. The headless environment alternative is explicitly called out. The flow from search -> connect -> list actions -> run is well-structured. | 3 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the overview section with nested bullet points adds little value and could be removed. The skill is self-contained without external file references, which is appropriate for its length, but the entity hierarchy section feels like filler. | 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 | |
- 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.