raindrop-api
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.
Install with Tessl CLI
npx tessl i github:intellectronica/agent-skills --skill raindrop-api90
Does it follow best practices?
Validation for skill structure
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 uses proper third-person voice and provides enough detail for Claude to distinguish this skill from other bookmark or API-related skills.
| 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 high-quality API skill with excellent actionability and clear workflow guidance. The confirmation requirement for destructive actions is well-documented, and the pagination/error handling patterns are production-ready. The main weakness is moderate verbosity - some content (OAuth2 flow, detailed field lists) could be moved to reference files to reduce the main skill's token footprint.
Suggestions
Move the OAuth2 flow section to a separate reference file (e.g., references/oauth2.md) since most users will use test tokens, and link to it with a brief mention
Consolidate the repeated curl header patterns into a single 'Request Template' section at the top, then use abbreviated examples below
| 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 workflow summary at the end, explicit confirmation requirements for destructive actions, token resolution order is well-defined, and pagination handling includes a complete loop example with termination condition. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections, tables for quick reference, and appropriate delegation to reference files (search-operators.md, collections-sharing.md, highlights.md) for detailed topics. Navigation is straightforward with one-level-deep references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 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 |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 12 / 16 Passed | |
- 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.