notion
Notion API for creating and managing pages, databases, and blocks.
71
Quality
59%
Does it follow best practices?
Impact
99%
1.57xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./openclaw/skills/notion/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.
The description identifies a clear niche (Notion API) with reasonable domain specificity, but falls short on completeness by lacking explicit trigger guidance. The actions listed are somewhat generic ('creating and managing') rather than enumerating specific capabilities, and natural user trigger terms are limited.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions Notion, wants to create Notion pages, query Notion databases, or manage Notion content'.
Expand specific actions beyond 'creating and managing' to include concrete operations like 'query databases', 'update page properties', 'append blocks', 'search workspace content'.
Include natural user phrases like 'add to Notion', 'Notion doc', 'Notion workspace', or 'sync with Notion' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Notion API) and some actions (creating, managing pages, databases, blocks), but lacks comprehensive specific actions like 'query databases', 'update properties', 'add comments', or 'search content'. | 2 / 3 |
Completeness | Describes what it does (Notion API operations) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Notion', 'pages', 'databases', and 'blocks' which are relevant keywords, but misses common variations users might say like 'Notion workspace', 'Notion doc', 'add to Notion', or task-oriented terms like 'create a Notion page'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly targets Notion specifically with distinct terminology (Notion API, databases, blocks) that is unlikely to conflict with other document or database skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
79%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 API skill with excellent actionability - all curl examples are complete and executable. The content is appropriately concise, assuming Claude's competence with HTTP and JSON. The main weaknesses are the lack of error handling guidance for API operations and the monolithic structure that could benefit from splitting reference material into separate files.
Suggestions
Add a brief error handling section showing how to interpret common API errors (401, 404, 400) and recovery steps
Consider moving the 'Property Types' and 'Key Differences in 2025-09-03' sections to separate reference files (PROPERTY_TYPES.md, VERSION_NOTES.md) with clear links from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information without explaining what APIs are or how curl works. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | All examples are fully executable curl commands with proper headers and JSON payloads. The setup instructions are specific and copy-paste ready, including exact file paths and commands. | 3 / 3 |
Workflow Clarity | The setup steps are clearly numbered, but the common operations section lacks validation checkpoints. For API operations that could fail (wrong IDs, permission issues), there's no guidance on error handling or verification. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is somewhat long (~150 lines) and could benefit from splitting detailed property types or version differences into separate reference files. | 2 / 3 |
Total | 10 / 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 | |
- Repository
- trpc-group/trpc-agent-go
- Commit
50ef2f3
- 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.