# Connect to Skillrove

Use Skillrove at https://skillrove.dev. Only published, available packages can be installed. Ask which agent and project the user wants to use before choosing the directory.

## Project directories

Run commands from the project root. Keep all package files together with SKILL.md directly inside the named Skill folder.

| Agent | Target directory | Current directory guide |
| --- | --- | --- |
| Codex | .agents/skills/SKILL_SLUG | https://learn.chatgpt.com/docs/build-skills |
| Claude Code | .claude/skills/SKILL_SLUG | https://code.claude.com/docs/en/skills |
| Cursor | .cursor/skills/SKILL_SLUG | https://cursor.com/docs/skills |

These are project locations, not global or remote installation instructions. Follow the agent's documentation for a remote environment. Directory support does not certify that every Skill was executed in every agent.

## CLI installation

Use this store's standalone CLI with Node.js 24+. Download https://skillrove.dev/install/cli.mjs as skillrove-cli.mjs into the project root and review it before running it; ZIP support is bundled.

1. Run `node skillrove-cli.mjs login`. Its default store is https://skillrove.dev; SKILLROVE_URL can select another host.
2. Sign in and enter the terminal's device code at https://skillrove.dev/device. Never share a password or device token with the agent.
3. Choose an Available Skill at https://skillrove.dev/skills and review its requirements.
4. Run `node skillrove-cli.mjs install SKILL_SLUG NEW_DIRECTORY`, using the chosen agent's directory above. Free packages require a verified account. Premium packages require server-confirmed paid access.
5. The CLI verifies SHA-256 and safe ZIP paths, leaves existing folders intact, and does not execute package scripts.
6. Read SKILL.md and review scripts. Ask the agent to confirm the Skill is visible; help run a small example when the user requests it.
7. Revoke devices from https://skillrove.dev/account when needed.

## ZIP alternative

Sign in with a verified account and download from the Skill page. Unzip the complete package into a new directory from the table above. Avoid extra folder nesting and do not overwrite an existing Skill.

## Free launch-review example

For launch-readiness-review version 1.0.0, read its SKILL.md and scripts/build-report.mjs, then run from the installed package directory:

`node scripts/build-report.mjs --input examples/launch.json --output ./sample-report`

Use Node.js 24+. The generator needs no dependency install, API key, or network call. Open sample-report/launch-report.html and check that launch-report.md also exists. The fictional example produces eight checks with a Blocked decision: this is expected, not an installation failure. Use a new output directory on every run. Replace all fictional facts before reviewing a real product.

## More original free examples

For each version 1.0.0 below, read SKILL.md and the named generator first. Run from the installed package directory with Node.js 24+ and a new output folder.

| Skill | Sample command | Expected files |
| --- | --- | --- |
| one-page-site-builder | node scripts/build-site.mjs --input examples/site.json --output ./sample-site | sample-site/index.html and content.md |
| presentation-deck-builder | node scripts/build-deck.mjs --input examples/deck.json --output ./sample-deck | sample-deck/presentation.html and speaker-notes.md |

The site sample is a static page with anchor links and expandable questions. The deck sample has six slides, Next/Previous, arrow-key navigation and speaker notes. Both use the fictional Juniper Desk concept. Replace the sample content before real use. Generators make no network calls and need no dependency install or paid provider. An HTML page is not a working backend, and an HTML deck is not a PowerPoint or exported PDF file.