[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M74HZ1PVCYMENG1M35EY7D3S":3,"skill-same:01M74HZ1PVCYMENG1M35EY7D3S":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M74HZ1PVCYMENG1M35EY7D3S","cli-creator",null,"Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read\u002Fwrite commands, return stable JSON, manage auth, and pair with a companion skill.","ziyabicilecommerce-hub\u002Fai-cash-machine","ziyabicilecommerce-hub","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F285820068?v=4","01M74H526DGBPF10MA7T706NT1","01M74H5273WRZRFEWH3TPDJK4T",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcli-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcli-creator\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: cli-creator\ndescription: Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read\u002Fwrite commands, return stable JSON, manage auth, and pair with a companion skill.\n---\n\n# CLI Creator\n\nCreate a real CLI that future Codex threads can run by command name from any working directory.\n\nThis skill is for durable tools, not one-off scripts. If a short script in the current repo solves the task, write the script there instead.\n\n## Start\n\nName the target tool, its source, and the first real jobs it should do:\n\n- Source: API docs, OpenAPI JSON, SDK docs, curl examples, browser app, existing internal script, article, or working shell history.\n- Jobs: literal reads\u002Fwrites such as `list drafts`, `download failed job logs`, `search messages`, `upload media`, `read queue schedule`.\n- Install name: a short binary name such as `ci-logs`, `slack-cli`, `sentry-cli`, or `buildkite-logs`.\n\nPrefer a new folder under `~\u002Fcode\u002Fclis\u002F\u003Ctool-name>` when the user wants a personal tool and has not named a repo.\n\nBefore scaffolding, check whether the proposed command already exists:\n\n```bash\ncommand -v \u003Ctool-name> || true\n```\n\nIf it exists, choose a clearer install name or ask the user.\n\n## Choose the Runtime\n\nBefore choosing, inspect the user's machine and source material:\n\n```bash\ncommand -v cargo rustc node pnpm npm python3 uv || true\n```\n\nThen choose the least surprising toolchain:\n\n- Default to **Rust** for a durable CLI Codex should run from any repo: one fast binary, strong argument parsing, good JSON handling, easy copy\u002Finstall into `~\u002F.local\u002Fbin`.\n- Use **TypeScript\u002FNode** when the official SDK, auth helper, browser automation library, or existing repo tooling is the reason the CLI can be better.\n- Use **Python** when the source is data science, local file transforms, notebooks, SQLite\u002FCSV\u002FJSON analysis, or Python-heavy admin tooling that can still be installed as a durable command.\n\nDo not pick a language that adds setup friction unless it materially improves the CLI. If the best language is not installed, either install the missing toolchain with the user's approval or choose the next-best installed option.\n\nState the choice in one sentence before scaffolding, including the reason and the installed toolchain you found.\n\n## Command Contract\n\nSketch the command surface in chat before coding. Include the binary name, discovery commands, resolve or ID-lookup commands, read commands, write commands, raw escape hatch, auth\u002Fconfig choice, and PATH\u002Finstall command.\n\nWhen designing the command surface, read [references\u002Fagent-cli-patterns.md](references\u002Fagent-cli-patterns.md) for the expected composable CLI shape.\n\nBuild toward this surface:\n\n- `tool-name --help` shows every major capability.\n- `tool-name --json doctor` verifies config, auth, version, endpoint reachability, and missing setup.\n- `tool-name init ...` stores local config when env-only auth is painful.\n- Discovery commands find accounts, projects, workspaces, teams, queues, channels, repos, dashboards, or other top-level containers.\n- Resolve commands turn names, URLs, slugs, permalinks, customer input, or build links into stable IDs so future commands do not repeat broad searches.\n- Read commands fetch exact objects and list\u002Fsearch collections. Paginated lists support a bounded `--limit`, cursor, offset, or clearly documented default.\n- Write commands do one named action each: create, update, delete, upload, schedule, retry, comment, draft. They accept the narrowest stable resource ID, support `--dry-run`, `draft`, or `preview` first when the service allows it, and do not hide writes inside broad commands such as `fix`, `debug`, or `auto`.\n- `--json` returns stable machine-readable output.\n- A raw escape hatch exists: `request`, `tool-call`, `api`, or the nearest honest name.\n\nDo not expose only a generic `request` command. Give Codex high-level verbs for the repeated jobs.\n\nDocument the JSON policy in the CLI README or equivalent: API pass-through versus CLI envelope, success shape, error shape, and one example for each command family. Under `--json`, errors must be machine-readable and must not contain credentials.\n\n## Auth and Config\n\nSupport the boring paths first, in this precedence order:\n\n1. Environment variable using the service's standard name, such as `GITHUB_TOKEN`.\n2. User config under `~\u002F.\u003Ctool-name>\u002Fconfig.toml` or another simple documented path.\n3. `--api-key` or a tool-specific token flag only for explicit one-off tests. Prefer env\u002Fconfig for normal use because flags can leak into shell history or process listings.\n\nNever print full tokens. `doctor --json` should say whether a token is available, the auth source category (`flag`, `env`, `config`, provider default, or missing), and what setup step is missing.\n\nIf the CLI can run without network or auth, make that explicit in `doctor --json`: report fixture\u002Foffline mode, whether fixture data was found, and whether auth is not required for that mode.\n\nFor internal web apps sourced from DevTools curls, create sanitized endpoint notes before implementing: resource name, method\u002Fpath, required headers, auth mechanism, CSRF behavior, request body, response ID fields, pagination, errors, and one redacted sample response. Never commit copied cookies, bearer tokens, customer secrets, or full production payloads.\n\nUse screenshots to infer workflow, UI vocabulary, fields, and confirmation points. Do not treat screenshots as API evidence unless they are paired with a network request, export, docs page, or fixture.\n\n## Build Workflow\n\n1. Read the source just enough to inventory resources, auth, pagination, IDs, media\u002Ffile flows, rate limits, and dangerous write actions. If the docs expose OpenAPI, download or inspect it before naming commands.\n2. Sketch the command list in chat. Keep names short and shell-friendly.\n3. Scaffold the CLI with a README or equivalent repo-facing instructions.\n4. Implement `doctor`, discovery, resolve, read commands, one narrow draft or dry-run write path if requested, and the raw escape hatch.\n5. Install the CLI on PATH so `tool-name ...` works outside the source folder.\n6. Smoke test from another repo or `\u002Ftmp`, not only with `cargo run` or package-manager wrappers. Run `command -v \u003Ctool-name>`, `\u003Ctool-name> --help`, and `\u003Ctool-name> --json doctor`.\n7. Run format, typecheck\u002Fbuild, unit tests for request builders, pagination\u002Frequest-body builders, no-auth `doctor`, help output, and at least one fixture, dry-run, or live read-only API call.\n\nIf a live write is needed for confidence, ask first and make it reversible or draft-only.\n\nWhen the source is an existing script or shell history, split the working invocation into real phases: setup, discovery, download\u002Fexport, transform\u002Findex, draft, upload, poll, live write. Preserve the flags, paths, and environment variables the user already relies on, then wrap the repeatable phases with stable IDs, bounded JSON, and file outputs.\n\nFor raw escape hatches, support read-only calls first. Do not run raw non-GET\u002FHEAD requests against a live service unless the user asked for that specific write.\n\nFor media, artifact, or presigned upload flows, test each phase separately: create upload, transfer bytes, poll\u002Fread processing status, then attach or reference the resulting ID.\n\nFor fixture-backed prototypes, keep fixtures in a predictable project path and make the CLI locate them after installation. Smoke-test from `\u002Ftmp` to catch binaries that only work inside the source folder.\n\nFor log-oriented CLIs, keep deterministic snippet extraction separate from model interpretation. Prefer a command that emits filenames, line numbers or byte ranges, matched rules, and short excerpts.\n\n## Rust Defaults\n\nWhen building in Rust, use established crates instead of custom parsers:\n\n- `clap` for commands and help\n- `reqwest` for HTTP\n- `serde` \u002F `serde_json` for payloads\n- `toml` for small config files\n- `anyhow` for CLI-shaped error context\n\nAdd a `Makefile` target such as `make install-local` that builds release and installs the binary into `~\u002F.local\u002Fbin`.\n\n## TypeScript\u002FNode Defaults\n\nWhen building in TypeScript\u002FNode, keep the CLI installable as a normal command:\n\n- `commander` or `cac` for commands and help\n- native `fetch`, the official SDK, or the user's existing HTTP helper for API calls\n- `zod` only where external payload validation prevents real breakage\n- `package.json` `bin` entry for the installed command\n- `tsup`, `tsx`, or `tsc` using the repo's existing convention\n\nAdd an install path such as `pnpm install`, `pnpm build`, and `pnpm link --global`, or a `Makefile` target that installs a small wrapper into `~\u002F.local\u002Fbin`.\n\n## Python Defaults\n\nWhen building in Python, prefer boring standard-library pieces unless the workflow needs more:\n\n- `argparse` for commands and help, or `typer` when subcommands would otherwise get messy\n- `urllib.request` \u002F `urllib.parse`, `requests`, or `httpx` for HTTP, matching what is already installed or already used nearby\n- `json`, `csv`, `sqlite3`, `pathlib`, and `subprocess` for local files, exports, databases, and existing scripts\n- `pyproject.toml` console script or a small executable wrapper for the installed command\n- `uv` or a virtualenv only when dependencies are actually needed\n\nAdd a `Makefile` target such as `make install-local` that installs the command on PATH and document whether it depends on `uv`, a virtualenv, or only system Python.\n\n## Companion Skill\n\nAfter the CLI works, create or update a small skill for it. Use `$skill-creator` when it is available. Use `$CODEX_HOME\u002Fskills\u002F\u003Ctool-name>\u002FSKILL.md` for a personal companion skill unless the user names a repo-local `.codex\u002Fskills\u002F...` path or another skill repo.\n\nWrite the companion skill in the order a future Codex thread should use the CLI, not as a tour of every feature. Explain:\n\n- How to verify the installed command exists.\n- Which command to run first.\n- How auth is configured.\n- Which discovery command finds the common ID.\n- The safe read path.\n- The intended draft\u002Fwrite path.\n- The raw escape hatch.\n- What not to do without explicit user approval.\n- Three copy-pasteable command examples.\n\nKeep API reference details in the CLI docs or a skill reference file. Keep the skill focused on ordering, safety, and examples future Codex threads should actually run.\n","# CLI Creator\n\nCreate a real CLI that future Codex threads can run by command name from any working directory.\n\nThis skill is for durable tools, not one-off scripts. If a short script in the current repo solves the task, write the script there instead.\n\n## Start\n\nName the target tool, its source, and the first real jobs it should do:\n\n- Source: API docs, OpenAPI JSON, SDK docs, curl examples, browser app, existing internal script, article, or working shell history.\n- Jobs: literal reads\u002Fwrites such as `list drafts`, `download failed job logs`, `search messages`, `upload media`, `read queue schedule`.\n- Install name: a short binary name such as `ci-logs`, `slack-cli`, `sentry-cli`, or `buildkite-logs`.\n\nPrefer a new folder under `~\u002Fcode\u002Fclis\u002F\u003Ctool-name>` when the user wants a personal tool and has not named a repo.\n\nBefore scaffolding, check whether the proposed command already exists:\n\n```bash\ncommand -v \u003Ctool-name> || true\n```\n\nIf it exists, choose a clearer install name or ask the user.\n\n## Choose the Runtime\n\nBefore choosing, inspect the user's machine and source material:\n\n```bash\ncommand -v cargo rustc node pnpm npm python3 uv || true\n```\n\nThen choose the least surprising toolchain:\n\n- Default to **Rust** for a durable CLI Codex should run from any repo: one fast binary, strong argument parsing, good JSON handling, easy copy\u002Finstall into `~\u002F.local\u002Fbin`.\n- Use **TypeScript\u002FNode** when the official SDK, auth helper, browser automation library, or existing repo tooling is the reason the CLI can be better.\n- Use **Python** when the source is data science, local file transforms, notebooks, SQLite\u002FCSV\u002FJSON analysis, or Python-heavy admin tooling that can still be installed as a durable command.\n\nDo not pick a language that adds setup friction unless it materially improves the CLI. If the best language is not installed, either install the missing toolchain with the user's approval or choose the next-best installed option.\n\nState the choice in one sentence before scaffolding, including the reason and the installed toolchain you found.\n\n## Command Contract\n\nSketch the command surface in chat before coding. Include the binary name, discovery commands, resolve or ID-lookup commands, read commands, write commands, raw escape hatch, auth\u002Fconfig choice, and PATH\u002Finstall command.\n\nWhen designing the command surface, read [references\u002Fagent-cli-patterns.md](references\u002Fagent-cli-patterns.md) for the expected composable CLI shape.\n\nBuild toward this surface:\n\n- `tool-name --help` shows every major capability.\n- `tool-name --json doctor` verifies config, auth, version, endpoint reachability, and missing setup.\n- `tool-name init ...` stores local config when env-only auth is painful.\n- Discovery commands find accounts, projects, workspaces, teams, queues, channels, repos, dashboards, or other top-level containers.\n- Resolve commands turn names, URLs, slugs, permalinks, customer input, or build links into stable IDs so future commands do not repeat broad searches.\n- Read commands fetch exact objects and list\u002Fsearch collections. Paginated lists support a bounded `--limit`, cursor, offset, or clearly documented default.\n- Write commands do one named action each: create, update, delete, upload, schedule, retry, comment, draft. They accept the narrowest stable resource ID, support `--dry-run`, `draft`, or `preview` first when the service allows it, and do not hide writes inside broad commands such as `fix`, `debug`, or `auto`.\n- `--json` returns stable machine-readable output.\n- A raw escape hatch exists: `request`, `tool-call`, `api`, or the nearest honest name.\n\nDo not expose only a generic `request` command. Give Codex high-level verbs for the repeated jobs.\n\nDocument the JSON policy in the CLI README or equivalent: API pass-through versus CLI envelope, success shape, error shape, and one example for each command family. Under `--json`, errors must be machine-readable and must not contain credentials.\n\n## Auth and Config\n\nSupport the boring paths first, in this precedence order:\n\n1. Environment variable using the service's standard name, such as `GITHUB_TOKEN`.\n2. User config under `~\u002F.\u003Ctool-name>\u002Fconfig.toml` or another simple documented path.\n3. `--api-key` or a tool-specific token flag only for explicit one-off tests. Prefer env\u002Fconfig for normal use because flags can leak into shell history or process listings.\n\nNever print full tokens. `doctor --json` should say whether a token is available, the auth source category (`flag`, `env`, `config`, provider default, or missing), and what setup step is missing.\n\nIf the CLI can run without network or auth, make that explicit in `doctor --json`: report fixture\u002Foffline mode, whether fixture data was found, and whether auth is not required for that mode.\n\nFor internal web apps sourced from DevTools curls, create sanitized endpoint notes before implementing: resource name, method\u002Fpath, required headers, auth mechanism, CSRF behavior, request body, response ID fields, pagination, errors, and one redacted sample response. Never commit copied cookies, bearer tokens, customer secrets, or full production payloads.\n\nUse screenshots to infer workflow, UI vocabulary, fields, and confirmation points. Do not treat screenshots as API evidence unless they are paired with a network request, export, docs page, or fixture.\n\n## Build Workflow\n\n1. Read the source just enough to inventory resources, auth, pagination, IDs, media\u002Ffile flows, rate limits, and dangerous write actions. If the docs expose OpenAPI, download or inspect it before naming commands.\n2. Sketch the command list in chat. Keep names short and shell-friendly.\n3. Scaffold the CLI with a README or equivalent repo-facing instructions.\n4. Implement `doctor`, discovery, resolve, read commands, one narrow draft or dry-run write path if requested, and the raw escape hatch.\n5. Install the CLI on PATH so `tool-name ...` works outside the source folder.\n6. Smoke test from another repo or `\u002Ftmp`, not only with `cargo run` or package-manager wrappers. Run `command -v \u003Ctool-name>`, `\u003Ctool-name> --help`, and `\u003Ctool-name> --json doctor`.\n7. Run format, typecheck\u002Fbuild, unit tests for request builders, pagination\u002Frequest-body builders, no-auth `doctor`, help output, and at least one fixture, dry-run, or live read-only API call.\n\nIf a live write is needed for confidence, ask first and make it reversible or draft-only.\n\nWhen the source is an existing script or shell history, split the working invocation into real phases: setup, discovery, download\u002Fexport, transform\u002Findex, draft, upload, poll, live write. Preserve the flags, paths, and environment variables the user already relies on, then wrap the repeatable phases with stable IDs, bounded JSON, and file outputs.\n\nFor raw escape hatches, support read-only calls first. Do not run raw non-GET\u002FHEAD requests against a live service unless the user asked for that specific write.\n\nFor media, artifact, or presigned upload flows, test each phase separately: create upload, transfer bytes, poll\u002Fread processing status, then attach or reference the resulting ID.\n\nFor fixture-backed prototypes, keep fixtures in a predictable project path and make the CLI locate them after installation. Smoke-test from `\u002Ftmp` to catch binaries that only work inside the source folder.\n\nFor log-oriented CLIs, keep deterministic snippet extraction separate from model interpretation. Prefer a command that emits filenames, line numbers or byte ranges, matched rules, and short excerpts.\n\n## Rust Defaults\n\nWhen building in Rust, use established crates instead of custom parsers:\n\n- `clap` for commands and help\n- `reqwest` for HTTP\n- `serde` \u002F `serde_json` for payloads\n- `toml` for small config files\n- `anyhow` for CLI-shaped error context\n\nAdd a `Makefile` target such as `make install-local` that builds release and installs the binary into `~\u002F.local\u002Fbin`.\n\n## TypeScript\u002FNode Defaults\n\nWhen building in TypeScript\u002FNode, keep the CLI installable as a normal command:\n\n- `commander` or `cac` for commands and help\n- native `fetch`, the official SDK, or the user's existing HTTP helper for API calls\n- `zod` only where external payload validation prevents real breakage\n- `package.json` `bin` entry for the installed command\n- `tsup`, `tsx`, or `tsc` using the repo's existing convention\n\nAdd an install path such as `pnpm install`, `pnpm build`, and `pnpm link --global`, or a `Makefile` target that installs a small wrapper into `~\u002F.local\u002Fbin`.\n\n## Python Defaults\n\nWhen building in Python, prefer boring standard-library pieces unless the workflow needs more:\n\n- `argparse` for commands and help, or `typer` when subcommands would otherwise get messy\n- `urllib.request` \u002F `urllib.parse`, `requests`, or `httpx` for HTTP, matching what is already installed or already used nearby\n- `json`, `csv`, `sqlite3`, `pathlib`, and `subprocess` for local files, exports, databases, and existing scripts\n- `pyproject.toml` console script or a small executable wrapper for the installed command\n- `uv` or a virtualenv only when dependencies are actually needed\n\nAdd a `Makefile` target such as `make install-local` that installs the command on PATH and document whether it depends on `uv`, a virtualenv, or only system Python.\n\n## Companion Skill\n\nAfter the CLI works, create or update a small skill for it. Use `$skill-creator` when it is available. Use `$CODEX_HOME\u002Fskills\u002F\u003Ctool-name>\u002FSKILL.md` for a personal companion skill unless the user names a repo-local `.codex\u002Fskills\u002F...` path or another skill repo.\n\nWrite the companion skill in the order a future Codex thread should use the CLI, not as a tour of every feature. Explain:\n\n- How to verify the installed command exists.\n- Which command to run first.\n- How auth is configured.\n- Which discovery command finds the common ID.\n- The safe read path.\n- The intended draft\u002Fwrite path.\n- The raw escape hatch.\n- What not to do without explicit user approval.\n- Three copy-pasteable command examples.\n\nKeep API reference details in the CLI docs or a skill reference file. Keep the skill focused on ordering, safety, and examples future Codex threads should actually run.\n",{"name":5,"description":7},"main","ba099ce4bf0c0c705380fc823059cefc2f70facc",".agents\u002Fskills\u002Fcli-creator","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine","https:\u002F\u002Fai-cash-machine.vercel.app","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub","2026-11-15 04:53:17",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add ziyabicilecommerce-hub\u002Fai-cash-machine --skill cli-creator",{"tool":37,"command":38},"bunx","bunx skills add ziyabicilecommerce-hub\u002Fai-cash-machine --skill cli-creator",{"tool":40,"command":41},"pnpm","pnpm dlx skills add ziyabicilecommerce-hub\u002Fai-cash-machine --skill cli-creator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcli-creator\u002FSKILL.md",true,[45,51,56],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",280,"https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcli-creator\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",10776,{"path":57,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fagent-cli-patterns.md",5244,"https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcli-creator\u002Freferences\u002Fagent-cli-patterns.md",[61,70,77,84,91,98],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":69},"01M74WRQ932DK7689ZN1Z2N6M5","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","MIT","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":69},"01M74WRJG0WC6345TK70T5RGGK","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":69},"01M74WRFPSRFD04HM7QH930775","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":69},"01M74WRC2HG0YAYTNWVWEBQHR9","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":69},"01M74WR6MJEHCAAFBSYG1N3YSX","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":69},"01M74WR0JXWJQTVJ8JQQ2M8H8M","webinar-marketing","When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar\u002Fevent motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).","https:\u002F\u002Fgithub.com\u002Fziyabicilecommerce-hub\u002Fai-cash-machine\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fwebinar-marketing\u002FSKILL.md",[],[]]