8x8
8x8 integration. Manage Persons, Organizations, Deals, Leads, Activities, Notes and more. Use when the user wants to interact with 8x8 data.
61
72%
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/8x8/SKILL.mdQuality
Discovery
67%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 adequately identifies the platform (8x8) and lists entity types it can work with, and it includes an explicit 'Use when' clause. However, the actions are vague ('Manage' and 'and more'), trigger terms miss common user language variations, and the entity types listed are generic CRM concepts that could conflict with other CRM-related skills.
Suggestions
Replace the vague 'Manage' with specific concrete actions like 'Create, update, search, and delete' to improve specificity.
Add natural trigger terms users might say, such as 'CRM', 'contacts', 'sales pipeline', 'call center', or '8x8 CRM' to improve discoverability.
Remove the vague 'and more' and instead list additional specific capabilities to strengthen both specificity and distinctiveness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (8x8 integration) and lists several entity types (Persons, Organizations, Deals, Leads, Activities, Notes), but the actions are vague — 'Manage' and 'and more' don't describe concrete operations like create, update, delete, or search. | 2 / 3 |
Completeness | It answers both 'what' (manage Persons, Organizations, Deals, Leads, Activities, Notes) and 'when' ('Use when the user wants to interact with 8x8 data'), providing an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | It includes '8x8' as a key trigger term and entity names like 'Persons', 'Deals', 'Leads', which are somewhat relevant, but it misses natural user phrases like 'CRM', 'contacts', 'pipeline', 'sales', or 'call center' that users might naturally say when needing this skill. | 2 / 3 |
Distinctiveness Conflict Risk | The '8x8' brand name provides some distinctiveness, but terms like 'Persons', 'Organizations', 'Deals', 'Leads', 'Activities', and 'Notes' are generic CRM concepts that could overlap with other CRM integrations like Salesforce, HubSpot, or Pipedrive skills. | 2 / 3 |
Total | 9 / 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 and workflow clarity—the CLI commands are concrete and the connection state machine is well-documented with proper feedback loops. The main weaknesses are unnecessary introductory content about what 8x8 is, a feature overview list that adds no actionable value, and a popular actions table with empty descriptions. The skill could be tightened by removing content Claude already knows and splitting reference material into separate files.
Suggestions
Remove the introductory paragraph explaining what 8x8 is and the bullet-point feature overview—Claude already knows this and it wastes tokens.
Add descriptions to the popular actions table entries (all Description cells are empty), or remove the table if descriptions aren't available.
Consider extracting the proxy requests section and popular actions table into a separate reference file to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what 8x8 is (cloud-based communication platform) is unnecessary context Claude already knows. The 'Overview' bullet list of features adds little actionable value. However, the CLI commands and workflow sections are reasonably efficient. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear parameter placeholders and flag descriptions. | 3 / 3 |
Workflow Clarity | The connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors) and feedback loops (poll until ready, handle client actions, re-check). The overall flow from install → auth → connect → discover → run is well-structured with validation at each stage. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic for its length. The 8x8 Overview bullet list and the popular actions table could be in separate reference files. No bundle files are provided, and no external references are made beyond the official docs link. | 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.