Raindrop Io

Manage, organize, and access your bookmarks and saved webpages using Raindrop.io integration for seamless content collection and retrieval.

Security Scan

The skill claims a Raindrop.io integration but the runtime instructions and metadata are just a generic unfinished template — it lacks the authentication, API calls, or any concrete behavior needed to do what it says.

Purpose & Capability

The name/description promise integration with Raindrop.io, however the package declares no environment variables, no primary credential, no endpoints, and the SKILL.md contains only template TODOs. A real Raindrop.io integration would need authentication (API token or OAuth flow) and concrete API usage; those are missing, so the declared purpose and the actual content are inconsistent.

Instruction Scope

SKILL.md is an unfinished template with high-level guidance about how to structure a skill but contains no runtime commands, no references to Raindrop APIs, no file or env access, and no instructions to call external services. The instructions are vague and incomplete (granting the agent broad discretion if later filled in), but currently do not perform suspicious actions.

Install Mechanism

There is no install spec and no code files. That is low-risk for now because nothing is downloaded or written to disk.

Credentials

A Raindrop.io skill would normally require at least one credential (API token or OAuth client credentials). The absence of any declared env vars or primary credential is disproportionate to the stated purpose and suggests the metadata is incomplete or the skill was published prematurely.

Persistence & Privilege

always is false and the skill is user-invocable with normal autonomous invocation allowed. There is no indication this skill requests persistent or elevated privileges.

What to consider before installing

This skill appears to be an unfinished template rather than a working Raindrop.io integration. Do not rely on it to access or manage bookmarks yet. Before installing or enabling it, ask the publisher to provide: (1) a completed SKILL.md with concrete runtime behavior and example requests, (2) the authentication method (OAuth flow or API token) and the exact environment variables required (e.g., RAINDROP_TOKEN) and why they are needed, (3) the API endpoints called and any external domains the skill will contact, and (4) storage/retention details for any tokens. If the author cannot supply those, treat the skill as non-functional. When it does request credentials, prefer least-privilege tokens, verify the skill's source/homepage, and avoid providing high-privilege secrets until you confirm the implementation and hosting are trustworthy.

Overview

[TODO: 1-2 sentences explaining what this skill enables]

Structuring This Skill

[TODO: Choose the structure that best fits this skill's purpose. Common patterns:

1. Workflow-Based (best for sequential processes)

• Works well when there are clear step-by-step procedures
• Example: DOCX skill with "Workflow Decision Tree" -> "Reading" -> "Creating" -> "Editing"
• Structure: ## Overview -> ## Workflow Decision Tree -> ## Step 1 -> ## Step 2...

2. Task-Based (best for tool collections)

• Works well when the skill offers different operations/capabilities
• Example: PDF skill with "Quick Start" -> "Merge PDFs" -> "Split PDFs" -> "Extract Text"
• Structure: ## Overview -> ## Quick Start -> ## Task Category 1 -> ## Task Category 2...

3. Reference/Guidelines (best for standards or specifications)

• Works well for brand guidelines, coding standards, or requirements
• Example: Brand styling with "Brand Guidelines" -> "Colors" -> "Typography" -> "Features"
• Structure: ## Overview -> ## Guidelines -> ## Specifications -> ## Usage...

4. Capabilities-Based (best for integrated systems)

• Works well when the skill provides multiple interrelated features
• Example: Product Management with "Core Capabilities" -> numbered capability list
• Structure: ## Overview -> ## Core Capabilities -> ### 1. Feature -> ### 2. Feature...

Patterns can be mixed and matched as needed. Most skills combine patterns (e.g., start with task-based, add workflow for complex operations).

Delete this entire "Structuring This Skill" section when done - it's just guidance.]

[TODO: Replace with the first main section based on chosen structure]

[TODO: Add content here. See examples in existing skills:

• Code samples for technical skills
• Decision trees for complex workflows
• Concrete examples with realistic user requests
• References to scripts/templates/references as needed]

Resources (optional)

Create only the resource directories this skill actually needs. Delete this section if no resources are required.

scripts/

Executable code (Python/Bash/etc.) that can be run directly to perform specific operations.

Examples from other skills:

• PDF skill: fill_fillable_fields.py, extract_form_field_info.py - utilities for PDF manipulation
• DOCX skill: document.py, utilities.py - Python modules for document processing

Appropriate for: Python scripts, shell scripts, or any executable code that performs automation, data processing, or specific operations.

Note: Scripts may be executed without loading into context, but can still be read by Codex for patching or environment adjustments.

references/

Documentation and reference material intended to be loaded into context to inform Codex's process and thinking.

Examples from other skills:

• Product management: communication.md, context_building.md - detailed workflow guides
• BigQuery: API reference documentation and query examples
• Finance: Schema documentation, company policies

Appropriate for: In-depth documentation, API references, database schemas, comprehensive guides, or any detailed information that Codex should reference while working.

assets/

Files not intended to be loaded into context, but rather used within the output Codex produces.

Examples from other skills:

• Brand styling: PowerPoint template files (.pptx), logo files
• Frontend builder: HTML/React boilerplate project directories
• Typography: Font files (.ttf, .woff2)

Appropriate for: Templates, boilerplate code, document templates, images, icons, fonts, or any files meant to be copied or used in the final output.

---

Not every skill requires all three types of resources.