/**
 * `agentsmarket skill publish <file>` — wraps the existing publishCommand.
 *
 * Flags:
 *   --bump-version=patch|minor|major  Force version bump on content-hash conflict
 *
 * ## Flags that used to be here and are not any more
 *
 *   --metadata-only  Accepted and ignored. It printed "current publishCommand
 *     ignores this flag" and then published as a full publish. A flag that
 *     announces it does nothing is worse than an absent flag, so it is gone.
 *     Metadata-only updates already happen automatically on an unchanged
 *     version+hash, which is the only thing it was ever asking for.
 *
 *   --deprecate / --message / --un-deprecate  Accepted and ignored: they logged
 *     "[M6] Note: deprecation wiring is staged" and published the file anyway.
 *     Deprecating is not publishing — `publish` decides for itself whether the
 *     run creates a new row, and a deprecation has to land on the row the
 *     author already published. It is now its own verb:
 *     `agentsmarket skill deprecate <slug>` / `un-deprecate`.
 *
 * Default behavior (no flags): auto-detect by content hash
 *   - Same version + same hash → metadata-only update
 *   - Same version + different hash → error (suggest --bump-version)
 *   - New version → new row
 */
interface PublishFlags {
    /** #12 — now actually applied; see lib/semver-bump.ts. */
    bumpVersion?: 'patch' | 'minor' | 'major';
}
export declare function skillPublishCommand(filePath: string, flags: PublishFlags): Promise<void>;
export {};