/**
 * Where this CLI tells a coding agent that the skill bundles exist.
 *
 * WHY THIS IS ITS OWN MODULE. The pointer used to live as a const inside
 * `index.ts`, reachable only from `--help` and from the footer of an
 * unknown-subcommand error. Both are paths an agent takes while it is still
 * *exploring*. The moment someone has decided to use Cargo, and the only moment
 * we know for certain a human or agent is watching, is the line right after
 * sign-in succeeds, and that line said nothing.
 *
 * That gap is measurable and it is large: `@cargo-ai/cli` runs at roughly 1,900
 * npm downloads a week while `getcargohq/cargo-skills` gains on the order of 35
 * installs a week. People are already running this binary and almost none of
 * them install the skills that make it usable by an agent.
 *
 * Keep the strings here rather than at each call site, so a change to how the
 * bundles are named or installed cannot land in `--help` and miss sign-in.
 */
/** One line, for a footer where vertical space is somebody else's error. */
export declare const AGENT_SKILLS_HINT = "Coding agents: install the Cargo skills with `npx skills add getcargohq/cargo-skills`";
/**
 * Printed after a successful sign-in.
 *
 * Deliberately two lines and no more. A sign-in banner that scrolls is a banner
 * people configure away, and this fires at most a handful of times per machine
 * because signing in is rare, so it does not need a suppression flag to be
 * polite.
 *
 * No skill count. The help epilogue carried "sixteen skills" while the bundle
 * held seventeen: a hand-maintained number in prose goes stale the next time
 * somebody adds one, and nothing in CI was ever going to catch it here.
 */
export declare const AGENT_SKILLS_NEXT_STEP: string;
//# sourceMappingURL=agentSkills.d.ts.map