Common questions, direct answers
The product model is simple once the boundaries are explicit. These are the questions most users ask first.
What is Naar?
Naar is a repo-aware CLI for discovering, reviewing, and installing AI-agent skills from provider catalogs.
Is Naar a skill marketplace?
No. Naar is an installer and review layer that works with external providers. It does not operate its own hosted marketplace.
Does Naar send my source code anywhere?
Not by default for recommendation. Naar scans repository files locally and providers receive structured repo facts rather than the full codebase.
What is the difference between `naar search` and `naar go`?
`naar search` is direct catalog discovery. `naar go` is the guided repo-aware flow that scans, ranks, and then leads into install review.
Does search install anything?
No. Search is discovery-only and never writes files by itself.
Can I review before installing?
Yes. Naar builds an install plan, supports dry runs, and requires confirmation before writes.
Which providers are supported?
Anthropic and ClawHub are supported today, with fallback behavior where the provider integration supports it.
Which AI coding tools does Naar support?
The stable target set includes Claude, Cursor, Copilot, Codex, Gemini context, AGENTS.md, and generic agent-skill conventions. Additional targets exist behind opt-in flags.
What files can Naar write?
Managed target files plus `.naar/installed.json`, `naar.lock.json`, and a local `.naar/skills/` copy for provenance and uninstall support.
Can I uninstall skills?
Yes. `naar uninstall` removes Naar-managed files and updates project state and local lifecycle history.
Does Naar work without global install?
Yes. You can run it through `npx -y naar-cli@latest ...` if you do not want a global install.
Is Naar safe for private repositories?
It is safer than blind installation, but it is not a guarantee. Review plans, inspect `git diff`, and treat heuristic scores as advisory.
How do I report an issue?
Open a GitHub issue with the exact command, output, and context that produced the problem.
Can I contribute a provider?
Yes. The repo is open-source and provider work belongs in the contributor workflow, not in a hosted control panel.