Andrew Boehner

---
name: jupiter-quote
description: [TODO: Complete and informative explanation of what the skill does and when to use it. Include WHEN to use this skill - specific scenarios, file types, or tasks that trigger it.]
---

# Jupiter Quote

## 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.**

---
name: snapapi
description: Give your agent web intelligence — screenshot any URL, extract structured page data, detect page changes, and analyze websites via the SnapAPI REST API.
metadata:
  openclaw:
    requires:
      env:
        - SNAPAPI_API_KEY
      bins: []
    primaryEnv: SNAPAPI_API_KEY
tags:
  - web
  - screenshot
  - scraping
  - ai-agents
  - page-analysis
  - monitoring
  - browser
version: 1.0.0
---

# SnapAPI — Web Intelligence for AI Agents

SnapAPI gives your agent eyes on the internet. One API, six capabilities:

**Base URL:** `https://snapapi.tech`
**Auth:** `X-API-Key: $SNAPAPI_API_KEY`
**Free tier:** 100 requests/month — get a key at https://snapapi.tech

---

## Screenshot any URL

```bash
curl "https://snapapi.tech/v1/screenshot?url=https://example.com&format=png" \
  -H "X-API-Key: $SNAPAPI_API_KEY" \
  --output screenshot.png
```

Options: `format=png|jpeg|webp`, `fullPage=true`, `darkMode=true`, `width=1280`, `height=800`

---

## Analyze a page (structured intelligence)

```bash
curl "https://snapapi.tech/v1/analyze?url=https://example.com" \
  -H "X-API-Key: $SNAPAPI_API_KEY"
```

Returns:
```json
{
  "title": "Example Domain",
  "description": "...",
  "headings": [{ "level": 1, "text": "..." }],
  "links": [{ "text": "More info", "href": "https://..." }],
  "text_content": "...",
  "forms": [],
  "technologies": ["nginx"],
  "load_time_ms": 832
}
```

Use this when your agent needs to **understand** a page, not just see it.

---

## Extract metadata (fast — no full render)

```bash
curl "https://snapapi.tech/v1/metadata?url=https://example.com" \
  -H "X-API-Key: $SNAPAPI_API_KEY"
```

Returns: title, description, OG tags, Twitter card, favicon, canonical URL. Faster than `/analyze` — use for link previews and SEO research.

---

## Generate a PDF

```bash
curl "https://snapapi.tech/v1/pdf?url=https://example.com" \
  -H "X-API-Key: $SNAPAPI_API_KEY" \
  --output page.pdf
```

Options: `format=A4|Letter`, `landscape=true`, `margin=20`

---

## Render HTML to image

Useful for generating OG images, email previews, or screenshots from dynamic HTML:

```bash
curl -X POST "https://snapapi.tech/v1/render" \
  -H "X-API-Key: $SNAPAPI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"html": "<h1 style=\"color:blue\">Hello</h1>", "width": 800, "height": 400}'
```

---

## Monitor a page for changes

```bash
curl -X POST "https://snapapi.tech/v1/monitor" \
  -H "X-API-Key: $SNAPAPI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://competitor.com/pricing", "interval": "1h", "webhook": "https://your-server.com/hook"}'
```

Fires a webhook when content changes — use for competitor price tracking, compliance monitoring, stock signals.

---

## Batch process multiple URLs

```bash
curl -X POST "https://snapapi.tech/v1/batch" \
  -H "X-API-Key: $SNAPAPI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls": ["https://a.com", "https://b.com"], "action": "screenshot"}'
```

---

## Check your usage

```bash
curl "https://snapapi.tech/v1/usage" \
  -H "X-API-Key: $SNAPAPI_API_KEY"
```

Returns: `{ "used": 23, "limit": 100, "tier": "free", "resets": "2026-04-01" }`

---

## Agent prompting examples

```
Use snapapi to screenshot https://news.ycombinator.com and describe the top 5 stories.
```

```
Use snapapi_analyze on https://competitor.com and tell me their primary CTA and pricing structure.
```

```
Use snapapi to monitor https://example.com/pricing every hour and alert me when the price changes.
```

```
Use snapapi to batch-screenshot these 5 URLs and compare their layouts.
```

---

## Works great with

- **OpenClaw** — install the native plugin: `openclaw plugins install snapapi`
- **LangChain** — use as a tool via the REST API
- **n8n** — HTTP Request node pointing to any endpoint
- **AutoGPT / any agent** — standard REST, no SDKs required

---

Full docs: https://snapapi.tech/docs
Get your free API key: https://snapapi.tech