@seoagent-official/seoagent 1.87.0 → 1.87.1
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 +159 -98
- package/package.json +1 -1
- package/skills/references/inbox.md +10 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@seoagent-official/seoagent",
|
|
3
|
-
"version": "1.87.
|
|
3
|
+
"version": "1.87.1",
|
|
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": {
|
|
@@ -20,6 +20,7 @@
|
|
|
20
20
|
| `cli_ai_files_update` | The AI-readable file layer (OKF bundle + `llms.txt`) is missing, unmanaged, or stale | Safe |
|
|
21
21
|
| `cli_new_landing_page` | High-value keyword (`easy_win`/`competitor_gap`) with no page covering it — write a landing page | Safe (new content) |
|
|
22
22
|
| `cli_draft_ready` | The cloud already wrote a complete article and synced it to `.seoagent/content/<slug>.md` — review and place it | Safe (new content) |
|
|
23
|
+
| `cli_send_outreach_email` | A human-approved link-building email to send **from the user's own email account** | **Outward-facing — confirm first send of the session** |
|
|
23
24
|
|
|
24
25
|
## Per-type procedure
|
|
25
26
|
|
|
@@ -88,3 +89,12 @@ Start by reading `.seoagent/inbox/README.md` (or `seoagent inbox`) to see the li
|
|
|
88
89
|
- **Review the draft** (frontmatter carries title, meta description, status), then place it where this project's content renders: repo-native (mdx_sync) → copy/adapt into the repo's content directory and `seoagent content track` it; CMS → create the entry and track it; cloud-hosted → flip frontmatter `status` to `published` and sync. The inbox file body walks through each strategy.
|
|
89
90
|
- Edit freely before publishing — the `.seoagent` copy is the user's now. Show the user the draft before publishing.
|
|
90
91
|
- Acknowledge: `seoagent ack <action_id>` (or `--failed --reason "not publishing; ..."`).
|
|
92
|
+
|
|
93
|
+
### `cli_send_outreach_email-<id>.md`
|
|
94
|
+
|
|
95
|
+
- `Read` it. The frontmatter has `action_id`, `to_email`, `to_name`, and `prospect_url`; the body carries the exact subject + email text the user **already reviewed and approved in the SEOAgent dashboard**. Your job is delivery only.
|
|
96
|
+
- **Send it from the user's own email account** using whatever email tooling this session has (Gmail connector/MCP, AgentMail, a mail CLI, …). SEOAgent never sends email itself.
|
|
97
|
+
- **Confirm once per session** before the first outbound email (show recipient + subject); then send subsequent approved emails without re-prompting. Send **verbatim** — no added signature, links, or attachments; the one allowed edit is fixing an obviously wrong greeting name.
|
|
98
|
+
- No `to_email`? Check the prospect page for the author's address or a contact form — a form submission with the body text counts as sent.
|
|
99
|
+
- Acknowledge after sending: `seoagent ack <action_id>` — the dashboard marks the draft **sent** and the prospect **contacted**. Declining (`--failed --reason "not sending; ..."`) dismisses the draft. A transient tooling failure should NOT be acked — leave it pending and it returns next sync.
|
|
100
|
+
- **No email tooling available at all?** Leave the action pending and tell the user what tooling would enable sending (or that they can send manually from the dashboard's drafts queue).
|