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) and mentions key concepts, making it distinctive. However, it lacks explicit trigger guidance ('Use when...') and could be more specific about the concrete actions it enables. The missing 'when' clause significantly limits Claude's ability to know when to select this skill.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Use when the user wants to create Notion pages, query Notion databases, add content to Notion, or integrate with Notion workspace'
Expand specific actions beyond 'creating and managing' to include concrete operations like 'query databases, create pages, append blocks, update properties, search content'
Include natural user phrases like 'add to Notion', 'Notion doc', 'Notion workspace', 'sync with Notion'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Notion API) and some actions (creating, managing pages, databases, blocks), but doesn't list comprehensive specific actions like 'query databases', 'update properties', 'append blocks', etc. | 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', '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 API specifically with distinct terms like 'Notion', 'databases', 'blocks' - unlikely to conflict with other skills as Notion is a specific product. | 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 strong, actionable skill with excellent conciseness and fully executable examples. The main weakness is the lack of validation/error handling guidance for API operations - there's no mention of checking response codes, handling rate limits, or verifying operations succeeded. The structure is good but could benefit from splitting detailed reference material into separate files.
Suggestions
Add a brief section on response validation (checking for 200 status, handling common error codes like 401/404/429)
Include an example of handling rate limit errors with retry logic or at minimum mention what a rate-limited response looks like
Consider moving Property Types and Key Differences sections to separate reference files, keeping SKILL.md focused on quick-start operations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information. It assumes Claude knows what Notion, APIs, and curl are, jumping straight to actionable setup and examples without explaining basic concepts. | 3 / 3 |
Actionability | Every operation includes complete, copy-paste ready curl commands with proper headers and JSON payloads. Property type formats are concrete and immediately usable. | 3 / 3 |
Workflow Clarity | The setup steps are clearly numbered, but the API operations lack validation checkpoints. There's no guidance on verifying successful responses, handling errors, or confirming operations completed correctly. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in one file. The property types reference and version differences could be split into separate files for a cleaner overview, though the current length is borderline acceptable. | 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
8763418
- 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.