/**
 * `gsk init-genspark-code-skills` — client-side writer for the backend
 * `/api/tool_cli/genspark-code-skills` bundle.
 *
 * Why client-side: an HTTP/JSON response can't materialise a file tree on the
 * user's machine, so the server ships the genspark-code (code sandbox) skill
 * docs as `{ name, files: [{ path, content }] }` rows and this helper writes
 * them under `--out`. Server-served rather than baked into the npm package so
 * newly edited skill docs reach released CLIs without a republish.
 *
 * Path handling re-uses `safeJoin` / `SLUG_RE` from the `skills pull` writer:
 * both the skill name and each file path come from the server, so they are
 * validated before any file is written (a crafted payload must not escape
 * `--out`, and a malformed one must not leave a half-written tree).
 */
import type { CodeSkill } from '../types.js';
/**
 * Write a genspark-code skill bundle under `destDir/<skill-name>/...`.
 * Returns the number of files written. Throws on an unsafe name/path or an
 * empty bundle; nothing is written before the whole payload validates.
 */
export declare function writeCodeSkills(skills: CodeSkill[] | null | undefined, destDir: string): number;
//# sourceMappingURL=genspark-code-skills.d.ts.map