yarkr-cli 0.1.0 → 1.0.0

package/README.md

@@ -4,8 +4,8 @@ Install skills, agents and MCP toolsets from [Yarkr](https://yarkr.com) into the
 Claude Code, Codex, opencode, Cursor and more.
 
 ```sh
-npx yarkr-cli add anthropic/pdf                      # a public package, no account needed
-npx yarkr-cli add github/github-mcp --harness codex  # pick the harnesses to write
+npx yarkr-cli add posterus-ltd/code-review-checklist     # a public package, no account needed
+npx yarkr-cli add posterus-ltd/github --harness codex   # pick the harnesses to write
 ```
 
 In a project, `yarkr init` creates `yarkr.json`; `yarkr add` and `yarkr sync` then pin every package in `yarkr.lock`:
@@ -13,11 +13,20 @@ In a project, `yarkr init` creates `yarkr.json`; `yarkr add` and `yarkr sync` th
 ```sh
 npm install -g yarkr-cli
 yarkr init
-yarkr add anthropic/frontend-design
+yarkr add posterus-ltd/playwright-test-authoring
 yarkr sync --check   # in CI: exit 1 when anything is out of date
 ```
 
+Publishing from a repo? Yarkr finds `SKILL.md` folders, `agents/*.md` and `.mcp.json` on its own. Anything else
+(a skill that's a single markdown file, or a folder with a README instead of SKILL.md) goes in one `yarkr.index.yaml`
+at the root, and nothing has to move:
+
+```sh
+yarkr guide index-repo -o ~/.claude/skills/index-repo/   # a skill your agent uses to write the index
+yarkr lint                                               # what will be published, and what's wrong
+```
+
 `yarkr` uses the public hub at `https://yarkr.com` unless you point it at your own instance with
 `yarkr login --registry <url>`. Node 22 or newer.
 
-Docs: [docs/cli.md](https://github.com/valado/yarkr/blob/main/docs/cli.md) · Source: [github.com/valado/yarkr](https://github.com/valado/yarkr) · MIT
+Docs: [docs/cli.md](https://github.com/posterus-ltd/yarkr-public/blob/main/docs/cli.md) · Source: [github.com/posterus-ltd/yarkr-public](https://github.com/posterus-ltd/yarkr-public) · MIT