with one click
documents
Documents tools for Dataspheres AI
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Documents tools for Dataspheres AI
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Local dev skill for the Dataspheres AI Content API. Wraps /api/v1/ REST endpoints for local-to-production content workflows. Use when the user wants to push pages, generate release notes from git log, list pages, or update content in a datasphere from their local machine.
Full newsletter lifecycle — create, configure all settings (frequency, personalization, AI model, web search, reply threading, plan mode wiring), manage subscribers, attach forms, draft and manage issues, preview personalized letters, enable private chat and email replies, and test in dev.
Drive the Dataspheres AI platform from Claude Code — read conversation history, post messages as the user (via API key), poll for ARI replies, read the Reality Engine debug log, update the plan and outcomes, and control orchestration flow. Use when you need Claude Code to interact with ARI or inspect/modify a running reality session.
Knowledge-graph tools for Dataspheres AI — build typed graphs, relate nodes with VISUAL or executable TASK edges, group into colored container bubbles, auto-detect article hero images, embed graphs in pages, run scheduled searches, and report.
Sequencers tools for Dataspheres AI
Manage Kanban tasks, plan modes, and project workflows in Dataspheres AI
| name | documents |
| description | Documents tools for Dataspheres AI |
Tool reference for this resource group, mirrored by hand from the platform live
/api/mcp/schemaschema.
find_pdf_media — Find PDF Pages / ImagesFind extracted pages or embedded images from a PDF. Use this AFTER the user has run Extract Pages / Extract Images on a PDF. Pick your render strategy based on user intent:
| Field | Type | Required | Description |
|---|---|---|---|
documentId | string | yes | Parent PDF Document id |
kind | string | no | Filter: "pages" for page renders, "images" for embedded images, omit for both |
pageNumber | number | no | Filter to a specific page number |
limit | number | no | Max items to return (default 20) |