en un clic
sequences
Create and run automated workflows in Dataspheres AI
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Menu
Create and run automated workflows in Dataspheres AI
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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 | sequences |
| description | Create and run automated workflows in Dataspheres AI |
| argument-hint | [action] [options] |
Sequences are node-based automation pipelines scoped to a datasphere. Each sequence has a trigger type, a graph of nodes, and an execution history. Sequences run server-side and can be triggered manually, on a schedule, or via webhook.
list_sequences()
# → [{"id": "seq_...", "name": "Content Sync", "triggerType": "SCHEDULED", "status": "ACTIVE"}, ...]
list_sequences(status="ACTIVE", trigger_type="MANUAL")
Status values: DRAFT | ACTIVE | PAUSED | ARCHIVED
Trigger types: MANUAL | SCHEDULED | WEBHOOK
create_sequence(
name="Content Sync",
description="Sync pages from external CMS every hour",
trigger_type="SCHEDULED",
max_cost=0.50, # optional budget cap in USD per execution
)
# → {"id": "seq_abc123", "name": "Content Sync", "triggerType": "SCHEDULED"}
get_sequence(sequence_id="seq_abc123")
# → {"id": ..., "name": ..., "graphData": {...}, "status": "ACTIVE", "triggerType": "SCHEDULED"}
execute_sequence(sequence_id="seq_abc123")
# → {"id": "exec_...", "sequenceId": "seq_abc123", "status": "PENDING", "startedAt": "..."}
# With input data:
execute_sequence(sequence_id="seq_abc123", input_data={"topic": "AI trends 2026"})
list_executions(sequence_id="seq_abc123", limit=20)
# → [{"id": "exec_...", "status": "COMPLETED", "startedAt": "...", "completedAt": "...", "cost": 0.03}]
list_executions(sequence_id="seq_abc123", status="FAILED")
Execution status: PENDING | RUNNING | COMPLETED | FAILED
delete_sequence(sequence_id="seq_abc123")
# → None (204 No Content)
| Tool | Method | Endpoint | Notes |
|---|---|---|---|
list_sequences | GET | /api/v2/dataspheres/:dsId/sequences | Uses DB ID |
get_sequence | GET | /api/v2/dataspheres/:dsId/sequences/:sequenceId | |
create_sequence | POST | /api/v2/dataspheres/:dsId/sequences | |
execute_sequence | POST | /api/v2/dataspheres/:dsId/sequences/:sequenceId/execute | |
list_executions | GET | /api/v2/dataspheres/:dsId/sequences/:sequenceId/executions | |
delete_sequence | DELETE | /api/v2/dataspheres/:dsId/sequences/:sequenceId |
All endpoints use the datasphere DB ID (not URI) via v2 routes. This is resolved automatically by _ds_id().
Note: There is no v1 sequences API. All sequence operations must use v2.
| Error | Cause | Fix |
|---|---|---|
| "No active datasphere" | No datasphere set | Run dai use <uri> |
| 401 | Invalid key | Re-run dai login |
| 403 | Membership check failed | Ensure you're a datasphere member |
| 404 | Sequence not found | Check list_sequences() |