WeKnora

Operate a user's WeKnora knowledge base. Choose the independent environment path or optional managed arks path; WeKnora is a connection, not a Web search Provider.

Readiness and execution path

Check whether each environment variable is supplied without printing its value:

Both WEKNORA_BASE_URL and WEKNORA_API_KEY supplied: use the independent REST/script path; arks is not required. Empty or invalid values are a configuration error. The URL is already the /api/v1 root, for example https://weknora.example.com/api/v1; preserve deployment prefixes and legitimate private HTTP, and never append /api/v1 again.
Neither supplied: for connection verification, knowledge-base list/detail, or single-base search, read managed execution. Use arks only when it is available and the connection is configured. For other operations, explain that independent environment credentials are needed; a stored key is not exported to complete them.
Only one supplied: stop and ask the human to complete the pair in their own terminal. Never fill the missing half from managed storage or switch paths after a request fails.

Never request a key in chat, pass its literal value as a command argument, or write ad-hoc key files/shell profiles. Managed storage is allowed only through human-controlled arks setup weknora. The Skill never reads private ArkSpace configuration or credential files. Missing CLI does not authorize installation; offer manual environment configuration instead.

Obtain consent before probing the independent key once with GET /auth/me. A 403 may mean capability/scope denial or a route with no API-key policy; it is not proof that the key is missing or invalid. Follow errors, with no automatic connection fallback.

Independent requests refer to the key only as an environment expansion, never as a literal: