x-act-on-notifications

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# X Act On Notifications

Use ai-chrome-pilot to inspect X notifications, build a candidate list, and perform only the requested action on the notifications that match the user's criteria.

Keep the skill profile-agnostic. Use `default` unless the user explicitly requested another profile.

Use this skill for notification actions. If the user only wants to inspect notifications first, use `x-get-notifications` instead. If the user wants to reply or quote-post from a target post, use `x-compose-post`.

## Supported Actions

- `like`
- `bookmark`
- `repost`

Do not overload this skill with reply or quote composition. Treat those as posting workflows.

## Prerequisites

- ai-chrome-pilot server is available in the current repo
- Google Chrome is installed
- The user is already logged in to X in the chosen Chrome profile
- The UI is expected to be Japanese; match labels such as `すべて`, `@ツイート`, `いいねする`, `いいねしました`, `ブックマーク`, `リポスト`, and `リポストを取り消す`

If X shows a login screen, stop and use `x-login` first.

## Inputs To Resolve

Resolve these before acting:

- `profile_name`: default to `default` if unspecified
- `action`: one of `like`, `bookmark`, `repost`
- `types`: `reply`, `quote`, or both
- `filters`: actor handle/name, text substring, date substring, and optional limit
- `mode`: `dry-run` or `execute`

Default resolution rules:

- If `profile_name` is unspecified, use `default` without asking
- If the user explicitly asked to `like` or `bookmark`, default `mode=execute`
- If the user explicitly asked to `repost`, default `mode=dry-run` unless the request already includes clear matching conditions
- If `types` is unspecified, inspect both `reply` and `quote`
- If `filters` is unspecified and the action is `like` or `bookmark`, treat the request as applying to all matching pending notifications currently collected

If the user says only "interact with notifications" without enough detail to infer an action, default to `dry-run` and present candidates instead of clicking anything.

Recommended decision rule:

- Use `x-get-notifications` for read-only collection and review
- Use `x-act-on-notifications` only after the user supplied a clear action and matching conditions
- Prefer `dry-run` before `repost`, because reposting has broader visibility impact than likes or bookmarks

## Workflow

### 1. Ensure the server is running

Check health:

```bash
curl -s http://127.0.0.1:3333/health
```

If not running, start it with the requested profile:

```bash
HEADLESS=0 PROFILE_NAME=<profile_name> npx tsx src/index.ts
```

### 2. Open notifications

Navigate to notifications and wait for rendering:

```bash
curl -s -X POST http://127.0.0.1:3333/goto \
  -H 'Content-Type: application/json' \
  -d '{"url":"https://x.com/notifications"}'
sleep 2
```

Take a screenshot to confirm the user is logged in and the page loaded:

```bash
curl -s http://127.0.0.1:3333/screenshot -o /tmp/x_notifications.png
```

### 3. Inspect both notification tabs

Check both:

- `すべて`: quote reposts often appear here
- `@ツイート`: replies often appear here

Before any click, take a fresh `/snapshot` and use fresh refs from that snapshot only.

If the needed tab is not active, click the corresponding tab ref, then wait briefly and take another `/snapshot`.

### 4. Collect candidate notifications

Use `/snapshot` and limited scrolling to gather visible notifications. Repeat 2-3 times when needed:

```bash
curl -s http://127.0.0.1:3333/snapshot
curl -s -X POST http://127.0.0.1:3333/eval \
  -H 'Content-Type: application/json' \
  -d '{"js":"window.scrollBy(0, window.innerHeight * 2)"}'
sleep 1
```

Normalize each candidate with:

- `tab`: `all` or `mentions`
- `type`: `reply` if it contains `返信先:`, `quote` if it contains `引用`
- `actor`: display name and handle when visible
- `date`: visible date text such as `3月3日`
- `notification_text`: reply or quote text
- `original_post_text`: quoted or replied-to post text when visible
- `action_ref`: ref of the requested action button in the same article
- `action_state`
  - `like`: `done` if the button says `いいねしました`, `pending` if it says `いいねする`
  - `bookmark`: `present` if a bookmark button exists and is not already toggled off by stateful UI text; when state is ambiguous, do not act automatically

From shinshin86/ai-chrome-pilot, MIT.

More from shinshin86/ai-chrome-pilot