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/README.md CHANGED
@@ -1,5 +1,8 @@
1
1
  <p align="center">
2
- <img src="apps/web/public/favicon.svg" alt="SEO Skill" width="72" height="72">
2
+ <picture>
3
+ <source media="(prefers-color-scheme: dark)" srcset="assets/brand/s-dark.svg">
4
+ <img src="assets/brand/s.svg" alt="SEO Skill" width="144">
5
+ </picture>
3
6
  </p>
4
7
 
5
8
  <h1 align="center">SEO Skill</h1>
@@ -74,7 +77,7 @@ technical report before connecting Google.
74
77
  Running `seo help` shows the shape of the tool:
75
78
 
76
79
  ```txt
77
- seo v0.2.0
80
+ seo v0.2.1
78
81
 
79
82
  Human-friendly SEO reports first, power tools when you need them.
80
83
 
@@ -248,15 +251,15 @@ report tools at runtime, and the agent asks the CLI for the detail on each
248
251
  tool only when it is about to run it. You get the whole toolkit without fifty
249
252
  skill files sitting in the context window on every session.
250
253
 
251
- `seo start` offers to install the SEO skill during setup. In an agent-managed
252
- environment, add it yourself with the standard installer:
254
+ `seo start` offers to install the SEO skill during setup. If you skipped that
255
+ step or need to reinstall it later, run the packaged installer:
253
256
 
254
257
  ```sh
255
- npm i -g seo
256
- npx skills add iannuttall/seo
258
+ seo skill install
257
259
  ```
258
260
 
259
- Then install the local stdio MCP server into a supported client:
261
+ If you also skipped the MCP step, install the local server into a supported
262
+ client:
260
263
 
261
264
  ```sh
262
265
  seo mcp install
@@ -345,7 +348,7 @@ console.log(crawl.summary, crawl.issueGroups)
345
348
  The main `seo` export contains the report, provider, crawler, storage, and
346
349
  rendering APIs. `seo/mcp` exposes report discovery, report execution, and the
347
350
  embeddable MCP server. See the [TypeScript library
348
- guide](https://seoskill.dev/docs/library) for structured error handling,
351
+ guide](https://seoskill.dev/docs/typescript) for structured error handling,
349
352
  local Google access, and more examples.
350
353
 
351
354
  ## Local data and Google access