/**
 * `agentsmarket skill deprecate` / `un-deprecate`.
 *
 * ## Why this is a separate command and not `skill publish --deprecate`
 *
 * The flag existed and did nothing. It printed "[M6] Note: publishCommand
 * deprecation wiring is staged for Q28" and published the file as usual, so an
 * author who asked to retire a skill was told the request was seen and then
 * found the skill still live and still listed. Same failure mode as
 * `pipeline publish --deprecate`, which is why pipelines got their own verb
 * too — see `commands/pipeline/deprecate.ts` for the full argument against
 * carrying deprecation in a publish body.
 *
 * The flags are removed rather than wired: deprecating is not publishing, and
 * `publish` decides for itself whether the run produces a new row. A
 * deprecation has to land on the row the author already published.
 *
 * ## Semantics it relies on (server side, migration 009)
 *
 *   deprecated → hidden from GET /v1/skills by default; existing buyers can
 *                 still invoke it and get the reason back.
 *   NOT the same as is_private — private hides a skill from people who already
 *   paid for it. Deprecating never takes a skill away.
 *
 * ## Resolution
 *
 * Accepts either the `skill_<uuid>` id or the display name, using the same
 * by-slug-then-id order as `skill install`. Name lookup goes through
 * `GET /v1/skills/by-slug/:slug`, which is name-only, so the id path stays.
 */
export declare function skillDeprecateCommand(slug: string, message: string | undefined): Promise<void>;
export declare function skillUnDeprecateCommand(slug: string): Promise<void>;