geo-ai-search-optimization 1.2.11 → 1.2.13
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 +59 -0
- package/package.json +1 -1
- package/resources/geo-ai-search-optimization/references/skill-bundle-map.md +20 -0
- package/resources/geo-ai-search-optimization-agent-progress-tracker/SKILL.md +23 -0
- package/resources/geo-ai-search-optimization-agent-progress-tracker/agents/openai.yaml +4 -0
- package/resources/geo-ai-search-optimization-agent-status-board/SKILL.md +23 -0
- package/resources/geo-ai-search-optimization-agent-status-board/agents/openai.yaml +4 -0
- package/resources/geo-ai-search-optimization-usage/SKILL.md +24 -14
- package/src/agent-progress-tracker.js +496 -0
- package/src/agent-session.js +20 -0
- package/src/agent-status-board.js +246 -0
- package/src/auto-flow.js +68 -1
- package/src/cli.js +74 -0
- package/src/index.js +6 -0
- package/src/skills.js +6 -0
package/README.md
CHANGED
|
@@ -145,6 +145,47 @@ geo-ai-search-optimization agent-batch-executor ./reports/apply-plan.json --task
|
|
|
145
145
|
- 批次收尾命令
|
|
146
146
|
- 可直接复制给 agent 的 batch prompt
|
|
147
147
|
|
|
148
|
+
## Agent Progress Tracker 命令
|
|
149
|
+
|
|
150
|
+
如果你希望 agent 不是只拿到执行队列,而是能够明确回答“现在做到第几包、当前卡在哪、下一包是什么”,可以直接用 `agent-progress-tracker`:
|
|
151
|
+
|
|
152
|
+
```bash
|
|
153
|
+
geo-ai-search-optimization agent-progress-tracker ./your-site
|
|
154
|
+
geo-ai-search-optimization agent-progress-tracker ./reports/apply-plan.json --completed fix-01,fix-02 --current fix-03
|
|
155
|
+
geo-ai-search-optimization agent-progress-tracker ./reports/agent-batch-executor.json --blocked "缺少仓库权限,缺少模板文件" --format json --out ./reports/agent-progress-tracker.json
|
|
156
|
+
```
|
|
157
|
+
|
|
158
|
+
`agent-progress-tracker` 会输出:
|
|
159
|
+
|
|
160
|
+
- 当前状态是未开始、进行中、阻塞还是已完成
|
|
161
|
+
- 已完成到哪几包
|
|
162
|
+
- 当前正在推进哪一包
|
|
163
|
+
- 下一包是什么
|
|
164
|
+
- 当前阻塞项
|
|
165
|
+
- 建议下一步命令
|
|
166
|
+
- 可直接复制给 agent 的 progress prompt
|
|
167
|
+
|
|
168
|
+
## Agent Status Board 命令
|
|
169
|
+
|
|
170
|
+
如果你希望把当前执行状态直接整理成更像团队协作看板的分栏视图,而不是只看一份文字进度摘要,可以直接用 `agent-status-board`:
|
|
171
|
+
|
|
172
|
+
```bash
|
|
173
|
+
geo-ai-search-optimization agent-status-board ./your-site
|
|
174
|
+
geo-ai-search-optimization agent-status-board ./reports/apply-plan.json --completed fix-01 --current fix-02
|
|
175
|
+
geo-ai-search-optimization agent-status-board ./reports/agent-progress-tracker.json --blocked "缺少仓库权限,缺少模板文件" --format json --out ./reports/agent-status-board.json
|
|
176
|
+
```
|
|
177
|
+
|
|
178
|
+
`agent-status-board` 会输出:
|
|
179
|
+
|
|
180
|
+
- 已完成栏
|
|
181
|
+
- 进行中栏
|
|
182
|
+
- 阻塞栏
|
|
183
|
+
- 下一步栏
|
|
184
|
+
- 排队中栏
|
|
185
|
+
- 收尾栏
|
|
186
|
+
- 建议下一步命令
|
|
187
|
+
- 可直接复制给 agent 的 status board prompt
|
|
188
|
+
|
|
148
189
|
## Quick Start
|
|
149
190
|
|
|
150
191
|
如果你要从 0 到 1 启动一个 GEO 项目,建议照这个顺序做。
|
|
@@ -543,6 +584,8 @@ geo-ai-search-optimization agent-session ./your-site
|
|
|
543
584
|
geo-ai-search-optimization agent-runbook ./your-site
|
|
544
585
|
geo-ai-search-optimization agent-executor ./your-site
|
|
545
586
|
geo-ai-search-optimization agent-batch-executor ./your-site
|
|
587
|
+
geo-ai-search-optimization agent-progress-tracker ./your-site
|
|
588
|
+
geo-ai-search-optimization agent-status-board ./your-site
|
|
546
589
|
geo-ai-search-optimization skills
|
|
547
590
|
geo-ai-search-optimization where
|
|
548
591
|
geo-ai-search-optimization doctor
|
|
@@ -613,6 +656,20 @@ geo-ai-search-optimization help
|
|
|
613
656
|
- 输出 do-now checklist、stop checklist、success checklist、验证命令和回报模板
|
|
614
657
|
- 新增 `geo-ai-search-optimization-agent-executor` skill
|
|
615
658
|
|
|
659
|
+
## New in 1.2.13
|
|
660
|
+
|
|
661
|
+
- 新增 `agent-status-board` 命令
|
|
662
|
+
- 把当前执行状态整理成更像看板的分栏视图
|
|
663
|
+
- 支持从 `apply-plan`、`agent-progress-tracker`、`agent-batch-executor` 等工件继续生成状态看板
|
|
664
|
+
- 新增 `geo-ai-search-optimization-agent-status-board` skill
|
|
665
|
+
|
|
666
|
+
## New in 1.2.12
|
|
667
|
+
|
|
668
|
+
- 新增 `agent-progress-tracker` 命令
|
|
669
|
+
- 可以从 `apply-plan`、`agent-executor`、`agent-batch-executor` 等工件推导当前执行进度
|
|
670
|
+
- 输出已完成任务、当前包、下一包、阻塞项和建议下一步命令
|
|
671
|
+
- 新增 `geo-ai-search-optimization-agent-progress-tracker` skill
|
|
672
|
+
|
|
616
673
|
## New in 1.2.11
|
|
617
674
|
|
|
618
675
|
- 新增 `agent-batch-executor` 命令
|
|
@@ -811,6 +868,8 @@ The installed package now includes a bundled GEO skill pack, including:
|
|
|
811
868
|
- `geo-ai-search-optimization-agent-runbook`
|
|
812
869
|
- `geo-ai-search-optimization-agent-executor`
|
|
813
870
|
- `geo-ai-search-optimization-agent-batch-executor`
|
|
871
|
+
- `geo-ai-search-optimization-agent-progress-tracker`
|
|
872
|
+
- `geo-ai-search-optimization-agent-status-board`
|
|
814
873
|
- `geo-ai-search-optimization-usage`
|
|
815
874
|
- `geo-ai-search-optimization-agent-handoff`
|
|
816
875
|
- `geo-ai-search-optimization-repair-loop`
|
package/package.json
CHANGED
|
@@ -72,6 +72,26 @@ Best for:
|
|
|
72
72
|
- making the next agent finish packet 1 before packet 2 starts
|
|
73
73
|
- giving the next agent a batch-level prompt, per-packet checklists, and final closeout commands
|
|
74
74
|
|
|
75
|
+
### `geo-ai-search-optimization-agent-progress-tracker`
|
|
76
|
+
|
|
77
|
+
Use this when the next agent should explain current execution status, not just produce the next queue.
|
|
78
|
+
|
|
79
|
+
Best for:
|
|
80
|
+
|
|
81
|
+
- showing which packet is already done
|
|
82
|
+
- clarifying the current active packet and the next packet
|
|
83
|
+
- surfacing blockers before the team moves into closeout or the next batch
|
|
84
|
+
|
|
85
|
+
### `geo-ai-search-optimization-agent-status-board`
|
|
86
|
+
|
|
87
|
+
Use this when the next agent should present execution state as a board instead of a plain progress summary.
|
|
88
|
+
|
|
89
|
+
Best for:
|
|
90
|
+
|
|
91
|
+
- giving PM and agent the same execution view
|
|
92
|
+
- showing done, in-progress, blocked, next, and queued packets in one artifact
|
|
93
|
+
- turning progress tracking into a more shareable coordination output
|
|
94
|
+
|
|
75
95
|
## Usage guide
|
|
76
96
|
|
|
77
97
|
### `geo-ai-search-optimization-usage`
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: geo-ai-search-optimization-agent-progress-tracker
|
|
3
|
+
description: Track GEO execution progress from apply-plan, agent-executor, agent-batch-executor, completion-report, or related artifacts. Use when an agent should explain which GEO packet is already done, which one is active, what is blocked, and what command should run next.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# GEO Agent Progress Tracker
|
|
7
|
+
|
|
8
|
+
Use this skill when the next agent should stop guessing current status and make the execution state explicit.
|
|
9
|
+
|
|
10
|
+
`GEO = Generative Engine Optimization`
|
|
11
|
+
|
|
12
|
+
## What it does
|
|
13
|
+
|
|
14
|
+
- reads GEO execution artifacts and infers the current packet state
|
|
15
|
+
- shows completed packets, the active packet, the next packet, and blockers
|
|
16
|
+
- recommends the next command for continuing or closing out the work
|
|
17
|
+
- gives the next agent a progress-tracking prompt instead of another open-ended plan
|
|
18
|
+
|
|
19
|
+
## Best use
|
|
20
|
+
|
|
21
|
+
- when a PM asks “现在做到哪了?”
|
|
22
|
+
- when the next agent should explain status before touching the next packet
|
|
23
|
+
- when batch execution is underway and the team needs a stable progress checkpoint
|
|
@@ -0,0 +1,4 @@
|
|
|
1
|
+
interface:
|
|
2
|
+
display_name: "GEO Agent Progress Tracker"
|
|
3
|
+
short_description: "Track which GEO packet is done, active, or blocked"
|
|
4
|
+
default_prompt: "Use $geo-ai-search-optimization-agent-progress-tracker to explain GEO execution progress, blockers, the current packet, and the next command."
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: geo-ai-search-optimization-agent-status-board
|
|
3
|
+
description: Turn GEO execution state into a board-style artifact for PM and agent coordination. Use when an agent should present done, in-progress, blocked, next, queued, and closeout states from apply-plan, agent-progress-tracker, agent-batch-executor, or related execution artifacts.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# GEO Agent Status Board
|
|
7
|
+
|
|
8
|
+
Use this skill when the next agent should explain execution state as a board, not just as a paragraph summary.
|
|
9
|
+
|
|
10
|
+
`GEO = Generative Engine Optimization`
|
|
11
|
+
|
|
12
|
+
## What it does
|
|
13
|
+
|
|
14
|
+
- turns current GEO execution state into board columns
|
|
15
|
+
- keeps PM and agent aligned on the same packet status
|
|
16
|
+
- shows done, in-progress, blocked, next, queued, and closeout views
|
|
17
|
+
- points to the next command and preserves the underlying progress tracker
|
|
18
|
+
|
|
19
|
+
## Best use
|
|
20
|
+
|
|
21
|
+
- when a PM asks for a coordination-friendly view
|
|
22
|
+
- when progress tracking exists but still feels too text-heavy
|
|
23
|
+
- when the next agent should continue from a board artifact instead of rebuilding context
|
|
@@ -0,0 +1,4 @@
|
|
|
1
|
+
interface:
|
|
2
|
+
display_name: "GEO Agent Status Board"
|
|
3
|
+
short_description: "Present GEO execution state as a board"
|
|
4
|
+
default_prompt: "Use $geo-ai-search-optimization-agent-status-board to turn this GEO execution state into a board with done, in-progress, blocked, next, queued, and closeout columns."
|
|
@@ -13,26 +13,28 @@ Treat this tool as a PM-friendly GEO workflow for websites.
|
|
|
13
13
|
|
|
14
14
|
`GEO = Generative Engine Optimization`
|
|
15
15
|
|
|
16
|
-
The package is best explained as
|
|
16
|
+
The package is best explained as twenty layers:
|
|
17
17
|
|
|
18
18
|
1. `auto-flow`: auto-select the next skill and command chain
|
|
19
19
|
2. `agent-session`: build a runnable session for the next agent
|
|
20
20
|
3. `agent-runbook`: execution manual and checklist for the next agent
|
|
21
21
|
4. `agent-executor`: choose one packet to execute right now
|
|
22
22
|
5. `agent-batch-executor`: queue the first few packets, but still advance one packet at a time
|
|
23
|
-
6. `
|
|
24
|
-
7. `
|
|
25
|
-
8. `
|
|
26
|
-
9. `
|
|
27
|
-
10. `
|
|
28
|
-
11. `
|
|
29
|
-
12. `
|
|
30
|
-
13. `
|
|
31
|
-
14. `
|
|
32
|
-
15. `
|
|
33
|
-
16. `
|
|
34
|
-
17. `
|
|
35
|
-
18. `
|
|
23
|
+
6. `agent-progress-tracker`: track which packet is done, which one is active, and what comes next
|
|
24
|
+
7. `agent-status-board`: turn the execution state into a board view for PM and agents
|
|
25
|
+
8. `skills`: inspect the bundled skill package
|
|
26
|
+
9. `onboard-url` / `onboard`: first look
|
|
27
|
+
10. `scan`: raw signal check
|
|
28
|
+
11. `audit` / `report`: diagnosis
|
|
29
|
+
12. `fix-plan` / `owner-board`: execution planning
|
|
30
|
+
13. `agent-handoff`: agent takeover package
|
|
31
|
+
14. `apply-plan`: execution loop
|
|
32
|
+
15. `completion-report`: closeout
|
|
33
|
+
16. `handoff-bundle`: all-in-one package
|
|
34
|
+
17. `share-pack`: audience-ready delivery
|
|
35
|
+
18. `export-pack`: folder export
|
|
36
|
+
19. `html-pack` / `publish-pack`: browsable and final delivery output
|
|
37
|
+
20. `pm-brief` / `roadmap`: stakeholder alignment
|
|
36
38
|
|
|
37
39
|
## Recommended command order
|
|
38
40
|
|
|
@@ -44,6 +46,8 @@ npx geo-ai-search-optimization agent-session https://example.com
|
|
|
44
46
|
npx geo-ai-search-optimization agent-runbook https://example.com
|
|
45
47
|
npx geo-ai-search-optimization agent-executor https://example.com
|
|
46
48
|
npx geo-ai-search-optimization agent-batch-executor https://example.com
|
|
49
|
+
npx geo-ai-search-optimization agent-progress-tracker https://example.com
|
|
50
|
+
npx geo-ai-search-optimization agent-status-board https://example.com
|
|
47
51
|
npx geo-ai-search-optimization onboard-url https://example.com
|
|
48
52
|
npx geo-ai-search-optimization pm-brief https://example.com
|
|
49
53
|
npx geo-ai-search-optimization roadmap https://example.com
|
|
@@ -57,6 +61,8 @@ npx geo-ai-search-optimization agent-session ./your-site
|
|
|
57
61
|
npx geo-ai-search-optimization agent-runbook ./your-site
|
|
58
62
|
npx geo-ai-search-optimization agent-executor ./your-site
|
|
59
63
|
npx geo-ai-search-optimization agent-batch-executor ./your-site
|
|
64
|
+
npx geo-ai-search-optimization agent-progress-tracker ./your-site
|
|
65
|
+
npx geo-ai-search-optimization agent-status-board ./your-site
|
|
60
66
|
npx geo-ai-search-optimization scan ./your-site
|
|
61
67
|
npx geo-ai-search-optimization audit ./your-site
|
|
62
68
|
npx geo-ai-search-optimization fix-plan ./your-site
|
|
@@ -79,6 +85,8 @@ npx geo-ai-search-optimization roadmap ./your-site
|
|
|
79
85
|
- `agent-runbook`: build a checklist-driven runbook with preflight, validation, and reporting rules
|
|
80
86
|
- `agent-executor`: select one packet to execute now and package it into a single-task entrypoint
|
|
81
87
|
- `agent-batch-executor`: line up the first few packets in execution order while preserving one-packet-at-a-time discipline
|
|
88
|
+
- `agent-progress-tracker`: show execution progress, current packet, blockers, and the next packet to advance
|
|
89
|
+
- `agent-status-board`: present the current execution state as a board with done, in-progress, blocked, next, and queued columns
|
|
82
90
|
- `onboard-url`: first-time website check from a live URL
|
|
83
91
|
- `onboard`: interactive first-time onboarding
|
|
84
92
|
- `skills`: list the bundled skills and decide which skill or command chain fits the task
|
|
@@ -108,6 +116,8 @@ When explaining the tool to a user:
|
|
|
108
116
|
- if the user wants the next agent to follow a checklist and execution manual, move them to `agent-runbook`
|
|
109
117
|
- if the user wants the next agent to start one concrete task now, move them to `agent-executor`
|
|
110
118
|
- if the user wants the next agent to continuously advance the first 2 to 3 packets in order, move them to `agent-batch-executor`
|
|
119
|
+
- if the user wants the next agent to explain current progress, blockers, and the next packet, move them to `agent-progress-tracker`
|
|
120
|
+
- if the user wants the next agent to present execution state as a board for PM and agent coordination, move them to `agent-status-board`
|
|
111
121
|
- explain the result in PM language, not implementation jargon
|
|
112
122
|
- if the user sounds new, start with `onboard-url` or `quick-start`
|
|
113
123
|
- if the user wants another agent to take over, move them to `agent-handoff`
|