g1geo

Official G1GEO CLI entry skill for AI agents. Always invoke this skill before running any g1geo command. Use when a user mentions G1GEO or g1geo, provides or asks to run a g1geo CLI command, or wants to work with G1GEO product and company knowledge, documents and materials, writing requirements, question sets, articles, AI writing assistance, article fission, GEO brand visibility and detection, reports and exports, analysis and tracking, desktop publishing devices and accounts, GEO media discovery and publishing, direct publishing jobs, asynchronous jobs, authentication, products, capabilities, installation, updates, or diagnostics. Load the installed CLI's version-matched guide before acting, and use the official g1geo CLI rather than legacy Python scripts, internal APIs, curl, or guessed commands.

Use the official @g1geo/cli as the execution surface for G1GEO content operations, brand visibility detection, analysis, and automation. The installed CLI owns its current commands, authentication flow, output contracts, and workflows.

Features

• Brand visibility and GEO detection — start one Knowledge-aware web/app check, poll bounded question-platform progress, retrieve the final conclusion, retry failed cells, and share or export reports.
• Company knowledge and materials — manage products, company information, reference documents, image assets, image-text materials, writing instructions, and writing configuration.
• Questions and article production — generate and curate question sets, inspect trends and recent GEO detection summaries, generate articles directly from one topic, a question set, or an article group, manage manual groups and recovery tasks, and create, read, or update articles.
• Article inspection and rewrites — detect or fix AI markers, and preview or apply natural-expression rewrites.
• Article fission — generate up to ten text-only variants from one existing article, public URL, or local Markdown file, optionally using the product's reference documents.
• Analysis and monitoring — create company brand reports, inspect overall GEO analysis, and track visibility trends.
• Desktop publishing — inspect authorized teams, online desktop devices, publisher-account login state, submit article or image-text publishing jobs, and inspect, cancel, retry, or audit them without accessing platform credentials.
• GEO media publishing — page through active type-3 GEO media, optionally restrict discovery to the current high-inclusion set, use compact selection remarks and credit/RMB pricing, and submit confirmed article or image-text media jobs without exposing upstream IDs or costs.
• Agent and CI automation — authenticate securely, pass product and publishing context explicitly, discover live capabilities, monitor or cancel asynchronous jobs, and consume stable machine-readable results.

These features describe the G1GEO product surface so the Agent can choose the right workflow. Business routing, safe defaults, and result handling come from the installed CLI Guide; use the installed CLI's help for exact syntax after choosing a workflow, and use authenticated server capabilities for live availability.

Start here

If g1geo is unavailable, or the installed version does not provide g1geo guide, install or update it immediately:

bash

npm install --global @g1geo/cli@latest

Do not ask for separate conversational confirmation solely because the CLI is missing. Attempt the installation directly. If the host environment itself requires an approval step, use its normal approval mechanism and continue after approval.

Before running any operational command, load the installed version's instructions:

bash

g1geo guide

Read the complete output before acting. Do not truncate it or substitute cached instructions from another CLI version. Run it again after the installed CLI version changes.

Use the CLI

• Follow the Guide as the authoritative contract for the installed version. If this skill and the Guide differ, the Guide wins.
• Treat the Guide as a business router. Translate the user's desired outcome into the appropriate workflow, resolve safe context with read commands, and do not require the user to know G1GEO command names or IDs.
• Invoke commands without adding --output json or choosing an output format. Each command declares the format best suited to its result. Use an output override only when the user or an integration adapter explicitly requires it.
• After authentication, use g1geo capabilities to discover what the current server, credential, and product permit. Do not infer SaaS capabilities from command names alone.
• Do not invent unavailable commands or fall back to the historical Python CLI, old jike naming, browser cookies, frontend-internal endpoints, or direct API calls.
• Treat stdout, stderr, JSON envelopes, exit codes, error.retryable, and request_id exactly as the Guide specifies. Do not blindly retry failures.
• Keep product context explicit when the task could affect or inspect more than one product. Never substitute an internal numeric ID for a public prd_... ID.
• Keep publishing team and desktop device context explicit when required. Use only public IDs returned by the CLI.
• Execute the requested workflow instead of stopping after setup. Inspect the full result even on a non-zero domain exit code and report the meaningful outcome.
• Browser login grants the standard account-level CLI permission bundle across all products currently or subsequently visible to that identity. Whole-product deletion is intentionally unavailable to Agents; do not invent or bypass that boundary.