Add the agent Tasks tab (schedule automated periodic agent tasks with run logs) to your Next.js app
Scanned 9/2/2026
Install to Claude Code
npx -y skills add iblai/vibe --skill iblai-vibe-agent-task --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Iblai Vibe Agent Task?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/iblai-iblai-vibe-agent-task)More formats (shields.io, HTML) on the badges page.
---
name: iblai-vibe-agent-task
description: Add the agent Tasks tab (schedule automated periodic agent tasks with run logs) to your Next.js app
globs:
alwaysApply: false
---
# /iblai-vibe-agent-task
Add the agent **Tasks tab** -- schedule automated tasks that run your
agent on a cron cadence (one-off, daily, weekly, or monthly), then track
each run. The tab bundles four surfaces into one component: a searchable,
date-filterable task list with status badges, metric cards (total /
completed / failed), a **Schedule Task** dialog, a per-task run-logs panel,
and a log-details modal. This is one tab in the wider agent-settings
family (`access`, `api`, `datasets`, `disclaimers`, `embed`, `history`,
`llm`, `memory`, `prompts`, `safety`, `settings`, `tasks`, `tools`). Each
tab is a separate skill. All tabs share the same `AgentSettingsProvider`
wrapper -- set it up once and mount as many tabs as you need.




Do NOT add custom styles, colors, or CSS overrides to ibl.ai SDK components.
They ship with their own styling. Keep the components as-is.
Do NOT implement dark mode unless the user explicitly asks for it.
When building custom UI around SDK components, use the ibl.ai brand:
- **Primary**: `#0058cc`, **Gradient**: `linear-gradient(135deg, #00b0ef, #0058cc)`
- **Button**: `bg-gradient-to-r from-[#2563EB] to-[#93C5FD] text-white`
- **Font**: System sans-serif stack, **Style**: shadcn/ui new-york variant
- Follow the component hierarchy: use ibl.ai SDK components
(`@iblai/iblai-js`) first, then shadcn/ui for everything else
(`npx shadcn@latest add <component>`). Do NOT write custom components
when an ibl.ai or shadcn equivalent exists. Both share the same
Tailwind theme and render in ibl.ai brand colors automatically.
- Follow [BRAND.md](https://raw.githubusercontent.com/iblai/vibe/refs/heads/main/BRAND.md) for
colors, typography, spacing, and component styles.
You MUST run `/iblai-vibe-ops-test` before telling the user the work is ready.
After all work is complete, start a dev server (`pnpm dev`) so the user
can see the result at http://localhost:3000.
`iblai.env` is NOT a `.env.local` replacement — it only holds the 3
shorthand variables (`DOMAIN`, `PLATFORM`, `TOKEN`). Next.js still reads
its runtime env vars from `.env.local`.
Use `pnpm` as the default package manager. Fall back to `npm` if pnpm
is not installed.
> **Common setup (brand, conventions, env files, verification):** see [docs/skill-setup.md](https://raw.githubusercontent.com/iblai/vibe/refs/heads/main/docs/skill-setup.md).
## Prerequisites
- Auth must be set up first (`/iblai-vibe-auth`)
- MCP server + skills configured (`@iblai/mcp` in `.mcp.json`)
- `AgentSettingsProvider` must wrap the route (see `/iblai-vibe-agent-setting`
Step 2 if not already set up)
- Ask the user for a real `mentorId` (agent UUID). Do NOT invent one.
## Step 1: Check Environment
Before proceeding, check for an `iblai.env` in the project root. Look for
`PLATFORM`, `DOMAIN`, and `TOKEN` variables. If the file does not exist or
is missing these variables, tell the user:
"You need an `iblai.env` with your platform configuration. Download the
template and fill in your values:
`curl -o iblai.env https://raw.githubusercontent.com/iblai/vibe/refs/heads/main/iblai.env`"
## Step 2: Mount `AgentTasksTab`
```tsx
// app/(app)/agents/[mentorId]/tasks/page.tsx
"use client";
import { AgentTasksTab } from "@iblai/iblai-js/web-containers/next";
export default function AgentTasksPage() {
return (
<div className="flex h-full flex-col bg-white">
<AgentTasksTab />
</div>
);
}
```
`AgentTasksTab` reads `tenantKey`, `mentorId`, and `username` from
`AgentSettingsProvider` (via `useAgentSettings()`) and handles all of its
own data fetching and mutations (list, create, delete, run logs). No
props are required.
### With custom pagination
Both the task list and the run-logs panel paginate (5 per page). Without a
`PaginationComponent` the built-in web-containers `IblPagination` is used.
Inject your own to match the host app's pagination UI:
```tsx
<AgentTasksTab
PaginationComponent={({ currentPage, totalPages, onPageChange, disabled }) => (
<MyPagination
page={currentPage}
total={totalPages}
onChange={onPageChange}
disabled={disabled}
/>
)}
/>;
```
## Step 3: Customize Labels (Optional)
`AgentTasksTab` renders with the default agent-facing copy
(`AGENT_TASKS_TAB_LABELS`). Override any string via the `labels` prop. Pass
a full `TasksTabLabels` bundle (for a full agent re-skin) or a
partial object (for one-off edits).
```tsx
import {
AgentTasksTab,
type TasksTabLabels,
AGENT_TASKS_TAB_LABELS,
} from "@iblai/iblai-js/web-containers/next";
<AgentTasksTab
labels={{
header: {
title: "Scheduled tasks",
description: "Schedule automated runs for your agent.",
},
toolbar: { scheduleTask: "New task" },
}}
/>;
```
The label bundle is grouped by surface: `header`, `toolbar`, `metrics`,
`list`, `logs`, `states`, `scheduleDialog`, `deleteDialog`, `logDetails`,
and `toasts`. Override only the keys you need.
## Step 4: Use MCP Tools for Customization
```
get_component_info("AgentTasksTab")
get_component_info("AgentSettingsProvider")
```
## Tab surfaces
`AgentTasksTab` is a single mounted component, but it renders four distinct
surfaces. The corresponding web-containers source (under
`web-containers/.../edit-mentor-modal/tabs/tasks-tab`) is listed for
reference -- these pieces are internal to `AgentTasksTab` and are not
mounted separately.
| Surface | Screenshot | Source component | What it shows |
|---------|-----------|------------------|---------------|
| **Task list** | [list](https://raw.githubusercontent.com/iblai/vibe/refs/heads/main/skills/iblai-vibe-agent-task/iblai-vibe-agent-task-1-list.png) | `tasks-tab-content` / `task-list` / `task-metrics-cards` / `tasks-tab-toolbar` | Search + date filter + Schedule Task button, metric cards (Total / Completed / Failed), and a list of tasks with time, repeat cadence, and a status badge (Scheduled / Running / Completed / Failed / Disabled) |
| **Schedule Task dialog** | [create](https://raw.githubusercontent.com/iblai/vibe/refs/heads/main/skills/iblai-vibe-agent-task/iblai-vibe-agent-task-2-create.png) | `schedule-task-dialog` | Calendar date picker plus Task Name, Task Prompt, Time, Repeat (Don't repeat / Daily / Weekly / Monthly), and a "Notify me by email" toggle |
| **Run-logs panel** | [logs](https://raw.githubusercontent.com/iblai/vibe/refs/heads/main/skills/iblai-vibe-agent-task/iblai-vibe-agent-task-3-logs.png) | `task-logs-panel` | Per-task run logs; click a task on the left to load its logs, click a log row to open its details |
| **Log Details modal** | [log details](https://raw.githubusercontent.com/iblai/vibe/refs/heads/main/skills/iblai-vibe-agent-task/iblai-vibe-agent-task-4-log-details.png) | `task-log-details` | A single run's status, Created / Started / Ended timestamps, and full output |
Repeat cadence maps to a cron schedule: "Don't repeat" creates a `one_off`
task pinned to the chosen date; Daily / Weekly / Monthly create a recurring
cron. The list status is derived from the latest run log combined with the
task's `enabled` flag -- a one-off that ran successfully shows **Completed**,
not **Disabled**.
## `<AgentTasksTab>` Props
Import from `@iblai/iblai-js/web-containers/next`.
| Prop | Type | Required | Description |
|------|------|----------|-------------|
| `PaginationComponent` | `ComponentType<{ currentPage, totalPages, onPageChange, disabled, disableNumberedButtons? }>` | No | Custom pagination for the task list and logs panel. Defaults to the web-containers `IblPagination` |
| `labels` | `DeepPartial<TasksTabLabels>` | No | Override user-visible strings |
## Related Exports
From `@iblai/iblai-js/web-containers/next`:
- `AGENT_TASKS_TAB_LABELS` -- the default agent-facing label bundle.
- `TasksTabLabels` -- type for the full label bundle.
- `TaskListItem` -- a periodic agent normalized for the list (`id`, `name`,
`time`, `repeat`, `oneOff`, `enabled`, `status`, `rawData`).
- `TaskLog` -- a run log normalized for the logs panel (`id`, `entry`,
`timestamp`, `periodicAgentId`, `status`, `startTime`, `endTime`).
- `TaskDisplayStatus` -- the derived status union (`Disabled` | `Running` |
`Failed` | `Completed` | `Scheduled`).
## Step 5: Verify
Run `/iblai-vibe-ops-test` before telling the user the work is ready:
1. `pnpm build` -- must pass with zero errors
2. `pnpm test` -- vitest must pass
3. Start dev server and touch test:
```bash
pnpm dev &
npx playwright screenshot http://localhost:3000/agents/<id>/tasks /tmp/agent-tasks.png
```
## Important Notes
- **Redux store**: Must include `mentorReducer` and `mentorMiddleware` --
the periodic-agent API slice (list / create / delete / logs) ships inside
those bundles.
- **`initializeDataLayer()`**: 5 args (v1.2+)
- **`@reduxjs/toolkit`**: Deduplicated via webpack aliases in `next.config.ts`
- **Peer deps**: `sonner` and `@iblai/iblai-web-mentor` must be installed
(`pnpm add sonner @iblai/iblai-web-mentor`)
- **Shared provider**: `AgentSettingsProvider` must wrap the route at a
layout level. See `/iblai-vibe-agent-setting` Step 2 for the full snippet.
- **One-off vs recurring**: "Don't repeat" flags the task `one_off`; the
backend runs it once and the scheduler auto-disables it afterward. The
list still shows the last outcome (e.g. **Completed**), not **Disabled**.
- **Start time**: The dialog combines the picked date and time into the
task's `start_time`; it must be in the future or the dialog blocks save.
- **Brand guidelines**: [BRAND.md](https://raw.githubusercontent.com/iblai/vibe/refs/heads/main/BRAND.md)
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!