7shifts
7shifts integration. Manage Companies. Use when the user wants to interact with 7shifts data.
61
52%
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/7shifts/SKILL.mdQuality
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too vague to effectively guide skill selection. While it correctly identifies the integration target (7shifts), it fails to enumerate specific capabilities beyond 'Manage Companies' and provides an overly broad trigger condition. The description would benefit significantly from listing concrete actions and more specific trigger scenarios.
Suggestions
List specific actions the skill can perform (e.g., 'Create, update, and delete companies, manage locations, retrieve employee schedules, handle shift assignments').
Add domain-specific trigger terms users would naturally say (e.g., 'restaurant scheduling', 'shift management', 'workforce', 'employee schedules', 'labor management').
Make the 'Use when' clause more specific with concrete scenarios (e.g., 'Use when the user mentions 7shifts, restaurant scheduling, shift management, or needs to manage workforce data').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only mentions 'Manage Companies' which is a single vague action. It doesn't list concrete capabilities like creating, updating, deleting, or querying specific data types within 7shifts. | 1 / 3 |
Completeness | Has a basic 'what' (Manage Companies) and a 'when' clause ('Use when the user wants to interact with 7shifts data'), but both are too vague. The 'when' clause is overly broad and doesn't provide explicit triggers. | 2 / 3 |
Trigger Term Quality | Includes '7shifts' and 'Companies' as keywords, but lacks natural variations users might say like 'scheduling', 'shifts', 'workforce management', 'restaurant staff', or specific operations users would request. | 2 / 3 |
Distinctiveness Conflict Risk | '7shifts' is a specific product name which helps distinctiveness, but 'Manage Companies' and 'interact with data' are generic enough to potentially conflict with other integration or company management skills. | 2 / 3 |
Total | 7 / 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 skill provides solid actionable guidance with executable CLI commands and a useful actions reference table. However, it wastes tokens on introductory context Claude doesn't need, includes a lengthy entity list without actionable context, and lacks validation checkpoints in its workflows. The structure could benefit from splitting reference material into separate files.
Suggestions
Remove the introductory paragraph explaining what 7shifts is and who uses it - Claude already knows this context
Either remove the entity overview bullet list or transform it into actionable guidance (e.g., which actions apply to which entities)
Add validation steps after key operations: verify connection success, confirm action execution, handle common errors
Move the popular actions table and proxy request details to separate reference files, keeping SKILL.md as a concise overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., describing what 7shifts is and who uses it - Claude knows this). The overview bullet list of entities adds little value without context. However, the CLI commands and action tables are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, a useful table of popular actions with keys and descriptions, and concrete examples for running actions with JSON parameters. Commands are copy-paste ready. | 3 / 3 |
Workflow Clarity | Steps for setup and connection are listed but lack validation checkpoints. No guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded. The workflow is sequential but missing error recovery patterns. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the long entity overview list could be moved to a reference file. The skill is somewhat monolithic - the popular actions table and proxy request details could be split into separate reference documents for better navigation. | 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
d19a82b
- 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.