seo 0.2.0 → 0.2.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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "seo",
3
- "version": "0.2.0",
3
+ "version": "0.2.1",
4
4
  "description": "The only SEO skill your agent needs. 50+ SEO audit tools through a local CLI and MCP server, using your own crawl, Search Console, and GA4 data.",
5
5
  "type": "module",
6
6
  "license": "Apache-2.0",
package/skills/README.md CHANGED
@@ -11,23 +11,25 @@ what its evidence cannot support, and one verification step, is fetched at
11
11
  runtime with `describe`. This keeps the skill small and always in sync with the
12
12
  registry.
13
13
 
14
- ## Install
14
+ ## Install during setup
15
15
 
16
- The skill works best with the MCP server installed. This command is an
17
- interactive setup flow for a human:
16
+ Install the CLI and run the guided setup when you are starting from scratch:
18
17
 
19
18
  ```bash
20
- seo mcp install
19
+ npm i -g seo
20
+ seo start
21
21
  ```
22
22
 
23
- The skill also works by calling the CLI directly when MCP tools are not
24
- available. The npm package and repository contain the same skill. Install it
25
- with the standard agent skills installer:
23
+ Setup offers to install both the skill and local MCP server. If the CLI is
24
+ already set up, install or reinstall the skill directly:
26
25
 
27
26
  ```bash
28
- npx skills add iannuttall/seo
27
+ seo skill install
29
28
  ```
30
29
 
30
+ The skill can call the CLI directly when MCP tools are not available. The npm
31
+ package and repository contain the same skill.
32
+
31
33
  Use `seo skill list` or `seo skill path seo` to inspect the copy bundled with
32
34
  the npm package.
33
35