/**
 * Shared deprecation surfacing for CLI commands.
 *
 * The server has carried `deprecated_since` / `deprecation_message` since M6,
 * gates the POST install endpoint with a 410, and renders a banner on the HTML
 * skill page. None of that reaches anyone using the CLI, because the commands
 * read the detail endpoint instead — so deprecating 23 skills produced 23 clean
 * "✓ Installed" lines and nobody was told.
 *
 * The author of a deprecated skill needs the news at the moment they reach for
 * it: a pipeline they are about to build would depend on something that is
 * going away, and the only moment that warning is cheap is before it exists.
 *
 * Warnings only, never a refusal. Someone re-installing a skill that an
 * existing pipeline already references must not be blocked — that would turn a
 * maintenance notice into an outage.
 */
export interface DeprecationFields {
    deprecated_since?: string | null;
    deprecation_message?: string | null;
}
/** Print a deprecation warning to stderr, or return false if not deprecated. */
export declare function warnIfDeprecated(skill: DeprecationFields, label?: string): boolean;