@superagnt/superagnt 2.0.7 → 2.0.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,6 +1,6 @@
1
1
  # superagnt_ for OpenClaw — the agent value layer
2
2
 
3
- The agent value layer: one MCP connection = every data source (X, TikTok, YouTube, Instagram, Reddit, LinkedIn, web), people + company enrichment, a real workspace Postgres, schedules, webhooks and shareable canvases — plus the base skills that teach the workflows. OAuth on first use; the consent screen doubles as signup.
3
+ The agent value layer: one MCP connection = every data source (X, TikTok, YouTube, Instagram, Reddit, LinkedIn, web), people + company enrichment, a real workspace Postgres, schedules, webhooks and shareable dashboards — plus the base skills that teach the workflows. OAuth on first use; the consent screen doubles as signup.
4
4
 
5
5
  ## Install
6
6
 
@@ -48,7 +48,7 @@ it for their workspace in the superagnt app:
48
48
  - **People + company enrichment** — search, enrich, verified emails
49
49
  - **Workspace database** — a real Postgres per workspace, with migrations
50
50
  - **Schedules & webhooks** — recurring automations and inbound event ingestion
51
- - **Canvases** — shareable live dashboards
51
+ - **Dashboards** — live views the agent builds over the workspace's data
52
52
 
53
53
  ## Bundled skills
54
54
 
@@ -56,7 +56,7 @@ The same base skills as the superagnt Claude Code plugin, teaching the
56
56
  workflows on top of the tools:
57
57
 
58
58
  - `superagnt-automations`
59
- - `superagnt-canvas`
59
+ - `superagnt-dashboards`
60
60
  - `superagnt-data-pipelines`
61
61
  - `superagnt-data-sources`
62
62
  - `superagnt-lead-generation`
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "id": "superagnt",
3
3
  "name": "superagnt_",
4
- "description": "The agent value layer: one MCP connection = every data source (X, TikTok, YouTube, Instagram, Reddit, LinkedIn, web), people + company enrichment, a real workspace Postgres, schedules, webhooks and shareable canvases — plus the base skills that teach the workflows. OAuth on first use; the consent screen doubles as signup.",
5
- "version": "2.0.7",
4
+ "description": "The agent value layer: one MCP connection = every data source (X, TikTok, YouTube, Instagram, Reddit, LinkedIn, web), people + company enrichment, a real workspace Postgres, schedules, webhooks and shareable dashboards — plus the base skills that teach the workflows. OAuth on first use; the consent screen doubles as signup.",
5
+ "version": "2.0.9",
6
6
  "mcpServers": {
7
7
  "superagnt": {
8
8
  "url": "https://mcp.superagnt.com/mcp",
@@ -12,7 +12,7 @@
12
12
  },
13
13
  "skills": [
14
14
  "skills/superagnt-automations",
15
- "skills/superagnt-canvas",
15
+ "skills/superagnt-dashboards",
16
16
  "skills/superagnt-data-pipelines",
17
17
  "skills/superagnt-data-sources",
18
18
  "skills/superagnt-lead-generation",
package/package.json CHANGED
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "name": "@superagnt/superagnt",
3
- "version": "2.0.7",
3
+ "version": "2.0.9",
4
4
  "type": "module",
5
- "description": "The agent value layer: one MCP connection = every data source (X, TikTok, YouTube, Instagram, Reddit, LinkedIn, web), people + company enrichment, a real workspace Postgres, schedules, webhooks and shareable canvases — plus the base skills that teach the workflows. OAuth on first use; the consent screen doubles as signup.",
5
+ "description": "The agent value layer: one MCP connection = every data source (X, TikTok, YouTube, Instagram, Reddit, LinkedIn, web), people + company enrichment, a real workspace Postgres, schedules, webhooks and shareable dashboards — plus the base skills that teach the workflows. OAuth on first use; the consent screen doubles as signup.",
6
6
  "main": "index.js",
7
7
  "license": "MIT",
8
8
  "homepage": "https://superagnt.com/agent-toolkit",
@@ -15,7 +15,7 @@
15
15
  "database",
16
16
  "automation",
17
17
  "lead-generation",
18
- "canvas",
18
+ "dashboards",
19
19
  "ai-agent"
20
20
  ],
21
21
  "publishConfig": {
@@ -72,7 +72,7 @@ server. `agnt_tools_search` and `agnt_tools_list_enabled` keep their names.
72
72
  ## More
73
73
 
74
74
  - Schedules (cron) moved to the task-agents skill — see its `schedules.md`.
75
- - Live setup + endpoint reference: https://superagnt.com/agent-setup/prompt.md
75
+ - Setup guide, every client: https://www.superagnt.com/install
76
76
  - Packaged event-driven workflows: https://superagnt.com/skills
77
77
 
78
78
  <!-- skill_id: automations · source: https://github.com/superagnt/plugins -->
@@ -0,0 +1,70 @@
1
+ ---
2
+ name: superagnt-dashboards
3
+ description: This skill should be used when the user asks for a "dashboard", "shareable report", "KPI page", or "live chart", or wants results as a page someone else can open. Covers the superagnt workspace dashboard: views (HTML pages on sa-* elements) bound to named queries over the workspace database and platform data, the draft-and-publish loop, and public links. Use after data lands in the workspace database; see workspace-db for table design.
4
+ version: 0.3.0
5
+ ---
6
+
7
+ # The workspace dashboard: results as a living page
8
+
9
+ Every workspace has one dashboard of views. A view is an HTML page built from
10
+ `sa-*` elements (numbers, charts, tables, lists), each bound to a named query
11
+ over the workspace database or platform data (credits, usage, data jobs,
12
+ agent runs, pending approvals). Views stay current as the data changes.
13
+ People in the workspace see them in the superagnt app, and a person can share
14
+ one as a public link that anyone can open, no account needed.
15
+
16
+ ## Procedure
17
+
18
+ 1. Data first. Queries read tables; if the table does not exist yet, the
19
+ workspace-db skill's patterns come first.
20
+ 2. `agnt_dashboards_guide` once: the files, the query grammar, the `sa-*`
21
+ elements and publishing. `agnt_dashboards_describe_data` lists the tables
22
+ and platform datasets a query can read.
23
+ 3. Build in your own draft: `agnt_dashboards_apply_template` for a starter
24
+ view (number row, trend, breakdown, table with CSV, approvals, credits and
25
+ usage), or `agnt_dashboards_write_file` for `queries/<name>.sql`,
26
+ `views/<slug>.html` and the view's `dashboard.json` entry. Every write is
27
+ checked and returns its problems in plain words. Each query runs once with
28
+ its defaults, so aggregate in SQL (`group by date_trunc('day', ...)`).
29
+ 4. `agnt_dashboards_preview` renders the view as a PNG with a report on each
30
+ query. Fix what it names, then `agnt_dashboards_publish` with a one-line
31
+ summary: people in the workspace see the new version at once.
32
+ 5. Share: a person in the workspace turns on a view's public link from the
33
+ superagnt app. Agents can't make one; `agnt_dashboards_unshare_view` turns
34
+ one off.
35
+
36
+ ## Layout discipline
37
+
38
+ - Lead with a row of 3–5 numbers (`sa-value`), then trends (`sa-chart`),
39
+ then detail tables (`sa-table`).
40
+ - One measure per chart; failed/error series go in `danger-fields`, never the
41
+ accent.
42
+ - Time charts need `event_at`/`created_at` timestamptz columns; funnels bind
43
+ to stable status strings — schema rules in workspace-db.
44
+ - The dashboard tools are on for every workspace where the dashboard is on; a
45
+ deployed agent gets them with `dashboards_enabled`. What the plan caps is
46
+ the workspace database behind the queries (tables, rows, storage).
47
+
48
+ ## Tool names on grouped servers
49
+
50
+ New servers list one tool per family with an `action` argument. The flat
51
+ names above map to:
52
+
53
+ | Flat | Grouped tool, action |
54
+ |---|---|
55
+ | `agnt_dashboards_guide`, `_list_files`, `_read_file`, `_describe_data`, `_history`, `_preview` | `agnt_dashboards_read`: `guide`, `list_files`, `read_file`, `describe_data`, `history`, `preview` |
56
+ | `agnt_dashboards_write_file`, `_edit_file`, `_apply_template`, `_publish`, `_restore` | `agnt_dashboards_write`: `write_file`, `edit_file`, `apply_template`, `publish`, `restore` |
57
+ | `agnt_dashboards_delete_file`, `_discard_draft`, `_unshare_view` | `agnt_dashboards_remove`: `delete_file`, `discard_draft`, `unshare_view` |
58
+
59
+ Flat names still resolve on a grouped server but are not listed, so most
60
+ clients will not let you call them: use the grouped tool. Canvases (the old
61
+ `agnt_canvas_*` tools) were retired; those names now only answer with this
62
+ replacement.
63
+
64
+ ## More
65
+
66
+ - A view over a table a task agent keeps fresh is a live dashboard with zero
67
+ upkeep — pair with the task-agents skill.
68
+ - Worked examples: https://superagnt.com/skills
69
+
70
+ <!-- skill_id: dashboards · source: https://github.com/superagnt/plugins -->
@@ -40,7 +40,7 @@ you fetch).
40
40
  3. **Results must be written back to a workspace table.** Make sure the
41
41
  job's recipe upserts each item's output into a table with a `status`
42
42
  column — that table is the ONLY place this session, later sessions, task
43
- agents, and canvases can read outcomes from. A recipe that merely returns
43
+ agents, and dashboard views can read outcomes from. A recipe that merely returns
44
44
  its result stores it where only the superagnt app can show it.
45
45
  4. Report progress from the table, not memory: counts by status via
46
46
  `agnt_db_select`. Failed items keep their error (`agnt_data_job_inspect_run`
@@ -73,6 +73,6 @@ server. `agnt_tools_search` and `agnt_tools_list_enabled` keep their names.
73
73
 
74
74
  - Table design for pipelines: the workspace-db skill
75
75
  - Feeding a job from an inbound webhook: the automations skill
76
- - Live platform reference: https://superagnt.com/agent-setup/prompt.md
76
+ - Setup guide, every client: https://www.superagnt.com/install
77
77
 
78
78
  <!-- skill_id: data-pipelines · source: https://github.com/superagnt/plugins -->
@@ -8,10 +8,10 @@ version: 0.2.0
8
8
 
9
9
  ## Connecting / reconnecting
10
10
 
11
- The live setup doc handles every client:
12
- `https://superagnt.com/agent-setup/prompt.md` — fetch and follow it. The
13
- endpoint is `https://mcp.superagnt.com/mcp`, OAuth-first (the consent screen
14
- doubles as signup). On Claude the server is a claude.ai connector, not part of
11
+ The setup guide has the steps for every client, one section each:
12
+ `https://www.superagnt.com/install`. The endpoint is
13
+ `https://mcp.superagnt.com/mcp`, OAuth-first (the consent screen doubles as
14
+ signup). On Claude the server is a claude.ai connector, not part of
15
15
  the plugin: give the user https://claude.ai/customize/connectors/yours?modal=add-custom-connector&connectorName=superagnt&connectorUrl=https%3A%2F%2Fmcp.superagnt.com%2Fmcp&open_in_browser=1
16
16
  (claude.ai's Add custom connector dialog, prefilled) and they click Add. It
17
17
  opens in the browser, and the Claude desktop app only loads connectors when it
@@ -95,7 +95,8 @@ needs a field the table leaves out.
95
95
  - **Credit errors**: `agnt_credits_balance` for the number;
96
96
  `agnt_usage_recent` for where it went. Top-ups happen in the superagnt
97
97
  app. AI credits (what running agents spend) are topped up there on the
98
- builder plans and during the trial; those plans include data credits only.
98
+ builder plans and during the trial; the plans include data credits only,
99
+ and the trial adds a one-time AI credit for hosted agents.
99
100
 
100
101
  ## Finding more
101
102
 
@@ -57,8 +57,9 @@ client-scheduled task too.
57
57
  every tool is a liability, not a convenience.
58
58
  5. **Deploy.** `agnt_agents_deploy` flips it live and it starts billing from
59
59
  its first session, so confirm with the human before calling. Runs spend
60
- AI credits, which the builder plans and the trial don't include: the human
61
- tops them up in the superagnt app.
60
+ AI credits. The builder plans include none and the trial a one-time AI
61
+ credit for hosted agents: past that, the human tops them up in the
62
+ superagnt app.
62
63
  6. **Wire the trigger.** An event exists → bind a webhook to the agent
63
64
  (automations skill). Purely time-based → create a schedule
64
65
  ([schedules.md](schedules.md)). On-demand from another agent or session →
@@ -71,8 +72,8 @@ client-scheduled task too.
71
72
 
72
73
  ## Keeping it honest
73
74
 
74
- - Results land where the human already looks: a canvas (canvas skill), or a
75
- table the next session reads — never only in the agent's own transcript.
75
+ - Results land where the human already looks: a dashboard view (dashboards
76
+ skill), or a table the next session reads — never only in the agent's own transcript.
76
77
  - One job per agent. A second job is a second agent; they can hand off via
77
78
  `agnt_agents_dispatch` or agent-to-agent webhooks.
78
79
  - Misbehaving agent: `agnt_agents_set_enabled(false)` stops triggers
@@ -97,6 +98,6 @@ server. `agnt_tools_search` and `agnt_tools_list_enabled` keep their names.
97
98
 
98
99
  - Cron syntax, cadence discipline, timezones: [schedules.md](schedules.md)
99
100
  - Event triggers instead of clocks: the automations skill
100
- - Live platform reference: https://superagnt.com/agent-setup/prompt.md
101
+ - Setup guide, every client: https://www.superagnt.com/install
101
102
 
102
103
  <!-- skill_id: task-agents · source: https://github.com/superagnt/plugins -->
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: superagnt-workspace-db
3
- description: This skill should be used when an agent workflow needs durable state: "save these results", "track status across runs", "remember this between sessions", building a pipeline, queue, or CRM-like table, or logging events over time. Covers table design in the superagnt workspace Postgres (agnt_db_*): schema patterns for pipelines, HITL queues, KPI events, and audit logs, plus canvas-ready column rules. Prefer it over local files or scratch JSON for anything a later run must read.
3
+ description: This skill should be used when an agent workflow needs durable state: "save these results", "track status across runs", "remember this between sessions", building a pipeline, queue, or CRM-like table, or logging events over time. Covers table design in the superagnt workspace Postgres (agnt_db_*): schema patterns for pipelines, HITL queues, KPI events, and audit logs, plus dashboard-ready column rules. Prefer it over local files or scratch JSON for anything a later run must read.
4
4
  version: 0.2.0
5
5
  ---
6
6
 
@@ -16,7 +16,7 @@ if the database is not yet provisioned,
16
16
  `agnt_db_status` says so and provisioning is automatic on first use.
17
17
 
18
18
  Local files die with the session. Anything a later run, another agent, a
19
- schedule, or a canvas must read belongs here.
19
+ schedule, or a dashboard view must read belongs here.
20
20
 
21
21
  ## Schema patterns
22
22
 
@@ -36,9 +36,9 @@ schedule, or a canvas must read belongs here.
36
36
  - Migrations through `agnt_db_apply_migration` with a short descriptive
37
37
  name; ad-hoc DDL through `execute_sql` gets lost.
38
38
  - Ask before destructive SQL (drop/truncate/mass delete) — always.
39
- - Design for the canvas from day one: timestamptz + numeric measures +
40
- stable status strings are exactly what canvas widgets bind to (see the
41
- canvas skill).
39
+ - Design for the dashboard from day one: timestamptz + numeric measures +
40
+ stable status strings are exactly what dashboard views chart (see the
41
+ dashboards skill).
42
42
 
43
43
  ## Tool names on grouped servers
44
44
 
@@ -60,6 +60,6 @@ server. `agnt_tools_search` and `agnt_tools_list_enabled` keep their names.
60
60
  process at row scale with the data-pipelines skill.
61
61
  - Tables are the hand-off surface to task agents and schedules (task-agents
62
62
  skill): a hosted run has no chat history, it reads state from here.
63
- - Live platform reference: https://superagnt.com/agent-setup/prompt.md
63
+ - Setup guide, every client: https://www.superagnt.com/install
64
64
 
65
65
  <!-- skill_id: workspace-db · source: https://github.com/superagnt/plugins -->
@@ -1,63 +0,0 @@
1
- ---
2
- name: superagnt-canvas
3
- description: This skill should be used when the user asks for a "dashboard", "shareable report", "KPI page", or "live chart", or wants results as a URL someone else can open. Covers superagnt canvases: widgets bound to workspace-database queries (KPI rows, trends, funnels, tables, kanban), layout discipline, and share links. Use after data lands in the workspace database; see workspace-db for table design.
4
- version: 0.2.0
5
- ---
6
-
7
- # Canvases: results as a living page
8
-
9
- A canvas is a hosted page of widgets, each bound to a SQL query over the
10
- workspace database. It stays current as the data changes, and a share link
11
- opens for anyone — no account needed on the viewer's side.
12
-
13
- ## Procedure
14
-
15
- 1. Data first. Widgets bind to tables; if the table does not exist yet, the
16
- workspace-db skill's patterns come first.
17
- 2. `agnt_canvas_introspect_schema` to see what is bindable, then
18
- `agnt_canvas_preview_query` BEFORE `agnt_canvas_put_widget` — previews
19
- are capped at 50 rows, so aggregate in SQL (`group by date_trunc`), never
20
- in the widget.
21
- 3. Build the page: `agnt_canvas_put_widget` per widget,
22
- `agnt_canvas_set_layout` once at the end.
23
- 4. Share: `agnt_canvas_share_create` returns the public link;
24
- `agnt_canvas_share_revoke` kills it. Confirm with the user before
25
- creating a share link — it makes the page reachable outside the
26
- workspace.
27
-
28
- ## Layout discipline
29
-
30
- - Lead with a KPI row (3–5 single numbers), then trends, then detail tables.
31
- - One measure per widget; failed/error series in the danger tone, never the
32
- accent.
33
- - Time widgets need `event_at`/`created_at` timestamptz columns; funnels and
34
- kanbans bind to stable status strings — schema rules in workspace-db.
35
- - The canvas tools are missing only when neither the flat
36
- `agnt_canvas_put_widget` nor the grouped `agnt_canvas_write` (action
37
- `put_widget`) is listed. Then enable the family:
38
- `agnt_tools_enable({ families: ['canvas'] })`, or on a grouped server
39
- `agnt_tools_write` with `action: "enable"` and the same `families`.
40
- Canvases are on every plan and count against no limit; what the plan caps
41
- is the workspace database behind them (tables, rows, storage).
42
-
43
- ## Tool names on grouped servers
44
-
45
- New servers list one tool per family with an `action` argument. The flat
46
- names above map to:
47
-
48
- | Flat | Grouped tool, action |
49
- |---|---|
50
- | `agnt_canvas_get`, `_introspect_schema`, `_preview_query`, `_chart_render`, `_snapshot`, `_share_list` | `agnt_canvas_read`: `get`, `introspect_schema`, `preview_query`, `chart_render`, `snapshot`, `share_list` |
51
- | `agnt_canvas_put_widget`, `_update_widget`, `_set_layout`, `_share_create` | `agnt_canvas_write`: `put_widget`, `update_widget`, `set_layout`, `share_create` |
52
- | `agnt_canvas_remove_widget`, `_share_revoke` | `agnt_canvas_remove`: `remove_widget`, `share_revoke` |
53
-
54
- Flat names still resolve on a grouped server but are not listed, so most
55
- clients will not let you call them: use the grouped tool.
56
-
57
- ## More
58
-
59
- - A canvas over a table a task agent keeps fresh is a live dashboard with
60
- zero upkeep — pair with the task-agents skill.
61
- - Worked examples with real dashboards: https://superagnt.com/skills
62
-
63
- <!-- skill_id: canvas · source: https://github.com/superagnt/plugins -->