cg

name	cg
description	Use when a local agent needs to dispatch work to CommonGround, inspect turn or agent state, wait for a turn to close, or resume a suspended turn through the `cg` CLI instead of calling the CG HTTP API directly.
metadata	{"nanobot":{"requires":{"bins":"[Truncated]"}}}

CG Skill

Use the local cg CLI as the stable CommonGround interaction surface.

If cg is not available on PATH, stop and fix the local CLI setup. Do not fall back to direct HTTP calls.

The host should provide CommonGround auth through CLI-managed profiles. Legacy direct Agent credential env/config may exist for operators, but prompt-level skills should prefer --profile and must not read credential tokens. Do not write credential tokens into request payloads, prompts, semantic records, or skill notes.

For open-source local demos, assume the operator has already prepared the default project cg-demo. If cg profile ensure-agent returns project_not_seeded, project_bootstrap_conflict, admin_service_credential_required, or profile_auth_required, stop and report the setup error. Do not try to repair project setup from the skill.

If the local CLI config or profile is missing, do not inspect token files or run setup commands. Ask the user/operator for the non-secret client connection facts needed to run cg: project id, agent id/profile, CommonGround service URL, Admin Service URL, and either an already prepared Admin Service bearer token file path or confirmation that the operator has written those values into CLI config. Never ask for a bearer token value in chat.