uni-productivity
Productivity tools via uni CLI. Use when user wants to send Slack messages, search Notion, manage Linear issues, or handle Todoist tasks. Services: slack, notion, linear, todoist.
90
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
89%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 is a solid skill description that clearly identifies when to use it and covers multiple specific services. The explicit 'Use when...' clause with concrete examples provides good trigger coverage. The main weakness is that the actions could be more specific (e.g., 'create/update/close Linear issues' rather than just 'manage').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (productivity tools) and lists services, but actions are somewhat generic ('send', 'search', 'manage', 'handle') rather than listing multiple specific concrete actions for each service. | 2 / 3 |
Completeness | Clearly answers both what (productivity tools via uni CLI for Slack, Notion, Linear, Todoist) and when (explicit 'Use when user wants to...' clause with specific trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Slack messages', 'search Notion', 'Linear issues', 'Todoist tasks', plus explicit service names. These are terms users naturally use when requesting these tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche with distinct triggers - specifically names four services (Slack, Notion, Linear, Todoist) and the uni CLI tool, making it unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted CLI reference skill that excels at conciseness and actionability. It provides comprehensive command examples across four services without any unnecessary explanation. The main weakness is the lack of workflow guidance for multi-step operations or error handling patterns.
Suggestions
Add a brief workflow example showing a common multi-step task (e.g., 'To create and assign a Linear issue: 1. Create issue, 2. Verify with get, 3. Update assignee')
Include a note about error handling or how to verify successful operations for destructive commands like delete or send
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Slack, Notion, Linear, or Todoist are. Every line is a concrete command example with inline comments showing purpose. | 3 / 3 |
Actionability | Fully copy-paste ready commands with clear examples. Each service section provides complete, executable CLI commands covering common operations with realistic arguments. | 3 / 3 |
Workflow Clarity | Commands are well-organized by service, but no explicit workflows for multi-step processes. Missing validation steps for operations like sending messages or creating issues (no confirmation/error handling guidance). | 2 / 3 |
Progressive Disclosure | For a CLI reference skill of this scope, the flat structure with clear service-based sections is appropriate. No need for external files given the content is a command reference, and sections are clearly delineated. | 3 / 3 |
Total | 11 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Repository
- shockz09/uni-cli
- Commit
f1dfc90
- 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.