# opensink-skills

> OpenSink integration tools for OpenClaw agents. Includes session management and activity logging for audit trails and observability, with more integrations coming. Use when the agent needs to log actions, track progress, or interact with OpenSink's agent platform.

- Author: Daniel Dorne
- Repository: opensinkai/openclaw-skills
- Version: 20260209172715
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-09
- Source: https://github.com/opensinkai/openclaw-skills
- Web: https://mule.run/skillshub/@@opensinkai/openclaw-skills~opensink-skills:20260209172715

---

---
name: opensink-skills
displayName: OpenSink Skills
description: OpenSink integration tools for OpenClaw agents. Includes session management and activity logging for audit trails and observability, with more integrations coming. Use when the agent needs to log actions, track progress, or interact with OpenSink's agent platform.
metadata: {"openclaw":{"emoji":"⚡","requires":{"bins":["curl"],"env":["OPENSINK_API_KEY"]}}}
---

# OpenSink Skills

A collection of OpenSink integrations for OpenClaw agents. One install, multiple tools.

## Setup

Requires:
- `OPENSINK_API_KEY` — API key from [app.opensink.com](https://app.opensink.com)
- `OPENSINK_AGENT_ID` — your agent's ID in OpenSink (create one with `agent.sh` or use an existing one)

---

## Agent Manager

Create and manage OpenSink agents. If `OPENSINK_AGENT_ID` is not set, create an agent first.

### Create an agent

```bash
# Returns the agent ID — set it as OPENSINK_AGENT_ID
AGENT_ID=$(scripts/agent.sh create "My Agent" "Description of what it does")
export OPENSINK_AGENT_ID=$AGENT_ID
```

### List existing agents

```bash
scripts/agent.sh list
```

### Get agent details

```bash
scripts/agent.sh get $AGENT_ID
```

---

## Session Manager

Create and manage OpenSink sessions. A session should be created at the start of a task and completed when done. The session ID is used by other tools (like the activity logger).

### Start a session

```bash
# Returns the session ID — store it for use with other tools
SESSION_ID=$(scripts/session.sh start)
```

### Update session status

```bash
scripts/session.sh status $SESSION_ID completed
scripts/session.sh status $SESSION_ID failed
```

### Get session details

```bash
scripts/session.sh get $SESSION_ID
```

---

## Activity Logger

Log significant agent actions to OpenSink as Activities. Creates an inspectable timeline visible in the OpenSink dashboard.

### Requires
- `OPENSINK_SESSION_ID` — set this after creating a session with `session.sh start`

### Log an activity

```bash
export OPENSINK_SESSION_ID=$(scripts/session.sh start)
scripts/activity.sh log "Processed 12 emails, flagged 3 as urgent" "message"
```

### Log with structured payload

```bash
scripts/activity.sh log "Daily report complete" "message" '{"emails_processed": 12, "flagged": 3}'
```

### List recent activities

```bash
scripts/activity.sh list
scripts/activity.sh list --session $SESSION_ID
scripts/activity.sh list --type message
```

### Activity types

| Type | When to use |
|---|---|
| `message` | Agent produced output or progress update |
| `sink_item_created` | Agent wrote data to a Sink |
| `state_updated` | Session state changed |

### When to log

Think of activities as a **captain's log** — milestones, not a transcript. If someone asks "what did the agent do today?", your activities should tell the full story without the noise.

**Log these:**
- Task completed ("Generated weekly report for Q1")
- External interactions ("Sent deployment notification to Slack")
- Decisions made ("Escalated ticket #42 to engineering")
- Errors and recoveries ("API rate limited, retried 3x, succeeded")
- State changes ("Order #456 moved to shipped")

**Skip these:**
- Every chat message or reply
- File reads and internal reasoning
- Routine tool calls (reading files, searching)
- Intermediate steps that don't matter on their own

**Rule of thumb:** If you'd mention it in a daily standup, log it. If not, skip it.

---

## Typical workflow

1. **Create or set agent** → `export OPENSINK_AGENT_ID=$(scripts/agent.sh create "Mars")` (or use an existing ID)
2. **Start a session** → `SESSION_ID=$(scripts/session.sh start)`
3. **Set the session ID** → `export OPENSINK_SESSION_ID=$SESSION_ID`
4. **Log activities as you work** → `scripts/activity.sh log "..." "message"`
5. **Complete the session** → `scripts/session.sh status $SESSION_ID completed`

---

## More coming soon

Future integrations planned:
- **Input Requests** — structured human-in-the-loop approval workflows
- **Knowledge Base** — read from curated Sinks as shared knowledge

## API Reference

See [references/api.md](references/api.md) for REST API details.