This skill provides comprehensive instructions for interacting with the Raindrop.io bookmarks service via its REST API using curl and jq. It covers authentication, CRUD operations for collections, raindrops (bookmarks), tags, highlights, filters, import/export, and backups. Use this skill whenever the user asks to work with their bookmarks from Raindrop.io, including reading, creating, updating, deleting, searching, or organising bookmarks and collections.
94
92%
Does it follow best practices?
Impact
100%
1.28xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
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 specific service (Raindrop.io), lists comprehensive capabilities, and includes an explicit 'Use when' clause with natural trigger terms. The description effectively distinguishes itself from generic bookmark or API skills by naming the specific service and detailing the full range of operations supported.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'authentication, CRUD operations for collections, raindrops (bookmarks), tags, highlights, filters, import/export, and backups' - comprehensive coverage of capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('comprehensive instructions for interacting with Raindrop.io... covers authentication, CRUD operations...') AND when ('Use this skill whenever the user asks to work with their bookmarks from Raindrop.io'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'bookmarks', 'Raindrop.io', 'reading, creating, updating, deleting, searching, or organising bookmarks and collections' - good coverage of user-facing terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting 'Raindrop.io' service explicitly - unlikely to conflict with other bookmark or API skills due to the named service and specific feature set. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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-structured, highly actionable API skill with excellent executable examples and clear workflow guidance. The confirmation requirements for destructive actions are explicitly documented, and progressive disclosure is handled well with external references. Minor verbosity in some sections (OAuth2 flow, repeated curl patterns) prevents a perfect conciseness score.
Suggestions
Consider moving the OAuth2 flow section to a separate reference file since most users will use test tokens, reducing the main skill's token footprint
Consolidate the repeated curl header patterns into a single 'Request Template' section to reduce redundancy
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., repeated curl patterns, documentation links that could be consolidated). Some sections like the OAuth2 flow could be moved to a reference file since most users will use test tokens. | 2 / 3 |
Actionability | Excellent executable examples throughout with complete curl commands, proper headers, and jq parsing. Every operation has copy-paste ready code with clear variable placeholders. | 3 / 3 |
Workflow Clarity | Clear token resolution order, explicit confirmation requirements for destructive actions, well-defined pagination workflow, and a concise workflow summary at the end. The confirmation requirement section explicitly lists what needs user approval. | 3 / 3 |
Progressive Disclosure | Good structure with quick reference tables, common patterns section for immediate use, and clear references to external files (search-operators.md, collections-sharing.md, highlights.md) for detailed topics. One-level-deep references are well-signaled. | 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (558 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
9f7f750
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.