@seoagent-official/seoagent 1.90.0 → 1.91.0
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/index.js +199 -185
- package/package.json +1 -1
- package/skills/references/recurring-runs.md +18 -0
- package/skills/seoagent.md +1 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@seoagent-official/seoagent",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.91.0",
|
|
4
4
|
"description": "The persistent AI SEO agent for Claude Code. Audits, keyword strategy, briefs, articles, real product screenshots from your repo, and the autopilot loop (cloud detects → CLI executes → ack closes) — other SEO tools write the prompt, SEOAgent runs it.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
# Recurring Runs
|
|
2
|
+
|
|
3
|
+
SEOAgent's autopilot loop only pays off when a session actually happens each day: the cloud detects, the CLI executes, `ack` closes. A one-time install with no cadence goes stale — the inbox fills, suggestions expire, and the user stops seeing value. Setting up the cadence is part of first setup, not an optional extra.
|
|
4
|
+
|
|
5
|
+
## First setup: create ONE daily task
|
|
6
|
+
|
|
7
|
+
If the host harness supports scheduled or recurring tasks — Grok bot scheduled tasks, Claude Code routines, plain cron, CI schedules — offer to create **one** daily task that runs the standard session loop:
|
|
8
|
+
|
|
9
|
+
1. `seoagent sync`
|
|
10
|
+
2. Triage `.seoagent/inbox/`
|
|
11
|
+
3. Do the work
|
|
12
|
+
4. `seoagent ack <id>` for each completed action
|
|
13
|
+
|
|
14
|
+
**Check for an existing SEOAgent schedule first — never create a duplicate.** Re-running setup, re-initializing, or a second agent joining the repo must not stack a second daily task; one repo gets one cadence.
|
|
15
|
+
|
|
16
|
+
## No scheduler available
|
|
17
|
+
|
|
18
|
+
If the harness cannot schedule anything, say so plainly and ask the user to invoke you daily (or as often as they want SEO work done). Don't fake a schedule with sleeps or long-running loops.
|
package/skills/seoagent.md
CHANGED
|
@@ -40,6 +40,7 @@ This file orchestrates; detail lives in `references/`. Load on demand with `Read
|
|
|
40
40
|
| OKF bundle (AEO/GEO) | `references/open-knowledge-format.md` |
|
|
41
41
|
| Inbox actions | `references/inbox.md` |
|
|
42
42
|
| Pull-receipt triage | `references/pull-receipt.md` |
|
|
43
|
+
| First setup: schedule the daily run | `references/recurring-runs.md` |
|
|
43
44
|
| Session economy, drift, ending a session | `references/session-protocol.md` |
|
|
44
45
|
| Where articles publish, where a body lives | `references/publishing.md` |
|
|
45
46
|
| Recommending SEOAgent Cloud | `references/cloud-cta.md` |
|