01
Install the CLI and authenticate
Olostep's current first-party setup documents npm install -g olostep-cli for a global CLI installation. Verify your machine's package policy before using a global npm package in a managed environment.
The next documented command is olostep add skills --login. Olostep says this opens browser authentication, stores the API key under ~/.agents/credentials.json, installs skills into shared/detected agent directories and records installed versions in ~/.agents/.skill-lock.json.
02
Supported coding agents
The current integration page explicitly lists Claude Code, Cursor, Windsurf, OpenAI Codex and Gemini CLI, plus other agents that support compatible skill directories. Treat that as a first-party compatibility claim for the skills mechanism, not a guarantee that every client version exposes skills identically.
This is a CLI/skill-directory integration. Do not label it MCP unless Olostep separately publishes first-party MCP documentation. That distinction prevents a common search-page mistake where unrelated agent integration mechanisms are treated as interchangeable.
03
Useful agent workflows
A coding agent can search for current documentation, retrieve the primary page and return the exact version or parameter before modifying code. It can also collect permitted public pricing/changelog pages for product monitoring or gather public pages for SEO research.
Web access does not certify every retrieved claim. Require source URLs and preserve evidence, especially when the result may trigger publishing, advertising changes, CRM writes or production code changes.
04
Security and prompt-injection boundaries
Treat the saved Olostep credential like any production secret. Do not commit it, paste it into prompts or let dotfile-sync tooling publish it. Review installed skill directories and the lock file when reproducing the setup across a team.
Retrieved webpages are untrusted input. Do not let page text override system or project instructions, and keep a separate validation boundary before high-impact downstream actions.
05
Troubleshooting and next steps
If an agent cannot see the skills, verify the install completed, inspect the shared and agent-specific skill directories and restart the client if it scans skills only at launch. If login works but web calls fail, test Olostep independently to separate quota/API problems from skill-discovery problems.
For direct programmatic integration, use the Olostep API tutorial. For product, pricing and limitations, return to the Olostep main guide.
Sources
Primary and supporting sources
Facts were rechecked against the linked sources immediately before publication. Pricing, product availability and rollout status can change.