Manage Things 3 via the `things` CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks OpenClaw to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
92
93%
Does it follow best practices?
Impact
96%
3.55xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 strong skill description that clearly identifies the target application (Things 3), the mechanism (CLI + URL scheme + local database), and provides explicit 'Use when' triggers with natural user language. It covers both read and write operations with specific examples of each, making it easy for Claude to select this skill appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: add/update projects+todos via URL scheme, read/search/list from the local Things database. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (manage Things 3 via CLI, add/update projects+todos, read/search/list from database) and 'when' (explicit 'Use when' clause with specific trigger scenarios like adding tasks, listing inbox/today/upcoming, searching tasks, inspecting projects/areas/tags). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'add a task to Things', 'list inbox/today/upcoming', 'search tasks', 'inspect projects/areas/tags', plus the tool name 'Things 3' and CLI name 'things'. The term 'OpenClaw' is unusual (likely an agent name) but doesn't detract from the natural keywords. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific application (Things 3), a specific platform (macOS), a specific CLI tool ('things'), and a specific mechanism (URL scheme + local database). Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 strong, well-structured CLI reference skill. It's concise, highly actionable with numerous concrete examples, and well-organized for quick scanning. The only notable gap is the lack of explicit verification steps after write operations (e.g., confirming a todo was added or updated successfully).
Suggestions
Add a verification step after write operations, e.g., 'After adding, verify with: things search "Title" --limit 1' to confirm the todo was created.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows what a URL scheme is, what UUIDs are, and how CLI tools work. Every section delivers actionable information without preamble or unnecessary explanation. | 3 / 3 |
Actionability | Every operation is illustrated with concrete, copy-paste-ready CLI commands. The examples cover a wide range of use cases (basic add, notes, projects, headings, tags, checklists, STDIN, update, complete/cancel) with specific flags and arguments. | 3 / 3 |
Workflow Clarity | The modify workflow has a clear sequence (search for ID → set auth → update), and --dry-run is mentioned for safe preview. However, there are no explicit validation checkpoints or feedback loops for write operations—e.g., no step to verify the todo was actually created/updated after running the command. | 2 / 3 |
Progressive Disclosure | For a standalone skill with no bundle files, the content is well-organized into logical sections (Setup, Read, Write, Examples: add, Examples: modify, Delete, Notes) that are easy to scan. The skill is appropriately sized and doesn't need external references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
b4fc4af
Table of Contents
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.