7shifts
7shifts integration. Manage Companies. Use when the user wants to interact with 7shifts data.
54
61%
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/7shifts/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 benefits from naming a specific product (7shifts) and including an explicit 'Use when' clause, but it is severely lacking in specificity about what actions can be performed. 'Manage Companies' and 'interact with 7shifts data' are too vague to help Claude distinguish this skill from other potential 7shifts-related skills or to understand the full scope of capabilities.
Suggestions
List specific concrete actions the skill can perform, e.g., 'Create, update, list, and delete companies in 7shifts. Retrieve company details, manage company settings.'
Narrow the 'Use when' clause to be more specific, e.g., 'Use when the user asks about 7shifts companies, company settings, or company management' rather than the overly broad 'interact with 7shifts data'.
Add natural trigger terms users might say, such as 'company details', 'company list', 'organization settings', or specific 7shifts terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Manage Companies' which is a single vague action. It doesn't list concrete actions like creating, updating, deleting companies, or any other specific operations. 'Interact with 7shifts data' is extremely abstract. | 1 / 3 |
Completeness | It does answer both 'what' (7shifts integration, manage companies) and 'when' (Use when the user wants to interact with 7shifts data). The 'Use when...' clause is explicitly present, though both parts are quite thin in detail. | 3 / 3 |
Trigger Term Quality | It includes '7shifts' which is a specific product name users would mention, and 'Companies' as a domain term. However, it lacks natural variations or specific task-related keywords users might say (e.g., 'scheduling', 'shifts', 'employees', 'restaurant workforce'). | 2 / 3 |
Distinctiveness Conflict Risk | '7shifts' is a distinctive product name which helps, but 'Manage Companies' and 'interact with 7shifts data' are broad enough that if there were multiple 7shifts-related skills (e.g., for shifts, employees, locations), this description would likely conflict due to the overly generic 'interact with 7shifts data' trigger. | 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.
The skill provides strong actionability with executable CLI commands covering the full workflow from installation to action execution and proxy requests. Its main weaknesses are unnecessary introductory context about 7shifts as a platform, a bulky entity list that doesn't serve a clear purpose, and missing validation/error-handling guidance for action execution. The connection setup workflow is well-documented but the overall structure could benefit from splitting reference material into separate files.
Suggestions
Remove the introductory paragraph explaining what 7shifts is and the full entity taxonomy list — Claude doesn't need this context to execute the integration.
Add error handling and validation guidance for action execution (e.g., what to do when `membrane action run` fails, how to interpret error responses).
Consider moving the popular actions table and proxy request documentation into separate reference files to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The overview section listing all 7shifts entities (Shift, Time Punch, User, etc.) adds little value since Claude doesn't need a taxonomy of the platform's data model. The introductory paragraph explaining what 7shifts is and who uses it is unnecessary context. However, the CLI commands and action tables are 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. The commands are copy-paste ready with clear parameter placeholders, and the popular actions table gives concrete action keys to use. | 3 / 3 |
Workflow Clarity | The connection setup workflow is well-sequenced with state handling (READY, BUILDING, CLIENT_ACTION_REQUIRED, etc.) and includes polling instructions. However, there are no explicit validation checkpoints or error recovery feedback loops for the action execution steps — if an action fails, there's no guidance on how to diagnose or retry. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic — the popular actions table and proxy request documentation could be in separate reference files. There are no bundle files to offload detail into, and the entity overview list adds bulk without clear navigation purpose. | 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
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.