notion
Notion API for creating and managing pages, databases, and blocks.
69
64%
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/notion/SKILL.mdQuality
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable API reference skill with fully executable curl examples covering all major Notion API operations. Its main weaknesses are the repetitive curl headers inflating token count, lack of error handling/validation guidance, and the monolithic structure that could benefit from splitting reference material into separate files.
Suggestions
Define the curl headers once as a reusable pattern or shell function at the top, then reference it in examples to reduce repetition across all 8+ curl blocks.
Add error handling guidance: show how to check response status codes, handle 429 rate limits with retry logic, and verify successful operations before proceeding.
Split the Property Types reference and Key Differences sections into separate reference files (e.g., PROPERTY_TYPES.md, API_CHANGES.md) and link to them from the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with concrete examples, but the repeated curl headers across every example add significant redundancy. A single template or variable approach would save many tokens. The property types reference section is useful but could be more compact. | 2 / 3 |
Actionability | Every operation includes fully executable curl commands with proper headers, JSON payloads, and realistic examples. The property types reference provides copy-paste ready formats. Setup instructions are concrete and specific. | 3 / 3 |
Workflow Clarity | The setup steps are clearly sequenced (1-4), and operations are well-organized. However, there are no validation checkpoints — no guidance on checking API responses for errors, handling 429 rate limits in practice, or verifying that operations succeeded before proceeding with dependent operations. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers, but it's a fairly long monolithic file. The property types reference and version differences sections could be split into separate reference files, with the main skill focusing on the most common operations and linking out for details. | 2 / 3 |
Total | 9 / 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
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.