[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78C0YFPZ3RB970EY3365QHH":3,"skill-same:01M78C0YFPZ3RB970EY3365QHH":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M78C0YFPZ3RB970EY3365QHH","data-manager-api-event-ingestion",null,"Guides developers through implementing event and conversion ingestion to Google products using the Data Manager API \u002Fv1\u002Fevents\u002Fingest endpoint and its associated client libraries. Use this skill when the user wants to upload offline conversions, enhanced conversions for leads, click conversions, Google Analytics web or app events, or any other event ingestion use case supported by the Data Manager API. Don't use for uploading audience members (use the data-manager-api-audience-ingestion skill).","Solizardking\u002Fskillhub-main","Solizardking","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F108096810?v=4","01M786KDB10AYV042N0F9BD5B5","Clawd","01M786NYYXSZK1D05WM8JQPC48",0,"MIT","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle\u002Fads\u002Fdata-manager-api\u002Fdata-manager-api-event-ingestion\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: data-manager-api-event-ingestion\ndescription: >-\n  Guides developers through implementing event and conversion ingestion to\n  Google products using the Data Manager API \u002Fv1\u002Fevents\u002Fingest endpoint\n  and its associated client libraries. Use this skill when the user wants to upload\n  offline conversions, enhanced conversions for leads, click conversions, Google\n  Analytics web or app events, or any other event ingestion use case supported by\n  the Data Manager API. Don't use for uploading audience members (use the\n  data-manager-api-audience-ingestion skill).\nmetadata:\n  version: 1.1\n  category: GoogleAds\n---\n# Data Manager API Event Ingestion\n\n## Implementation Workflow\n\n### Prerequisites\n\n-   **Authentication & Library Installation**: If you need to set up access to\n    the Data Manager API or install the client and utility libraries, refer to\n    the `data-manager-api-setup` skill.\n\n### Step 1: Identify Use Case & Read Documentation\n\n-   **Determine Destination Account Type**: [CRITICAL] If it's not\n    explicitly stated, STOP and CLARIFY with the user where the data is being\n    sent (e.g., Google Ads, Floodlight, Google Analytics)\n    BEFORE generating any code. Do not assume Google Ads by default. This maps\n    to the `account_type` field of the `operating_account` in the `Destination`,\n    and also determines valid event identifiers and requirements.\n-   **Read Documentation**: [CRITICAL] Follow the\n    [Send events guide](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fsend-events.md.txt)\n    to implement the integration, as steps for configuring and sending the\n    request may vary between destinations.\n\n### Step 2: Retrieve Code Sample\n\n> [!IMPORTANT]\n> If writing or updating an ingestion script, ALWAYS retrieve the\n> relevant code sample to use as a reference:\n\n| Language | Sample |\n| :--- | :--- |\n| **Python** | [`ingest_events.py`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-python\u002Fblob\u002Fmain\u002Fsamples\u002Fevents\u002Fingest_events.py) |\n| **Java** | [`IngestEvents.java`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-java\u002Fblob\u002Fmain\u002Fdata-manager-samples\u002Fsrc\u002Fmain\u002Fjava\u002Fcom\u002Fgoogle\u002Fads\u002Fdatamanager\u002Fsamples\u002FIngestEvents.java) |\n| **PHP** | [`ingest_events.php`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-php\u002Fblob\u002Fmain\u002Fsamples\u002Fevents\u002Fingest_events.php) |\n| **Node** | [`ingest_events.ts`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-node\u002Fblob\u002Fmain\u002Fsamples\u002Fevents\u002Fingest_events.ts) |\n| **.NET**| [`IngestEvents.cs`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-dotnet\u002Fblob\u002Fmain\u002Fsamples\u002FIngestEvents.cs) |\n\n### Step 3: Retrieve Migration Guides\n\n> [!CRITICAL]\n> If refactoring code to upgrade from another Google API, ALWAYS\n> extract the full contents of the relevant field mapping guide.\n\n#### Google Ads\n\n*   **Google Ads API Offline Conversions**:\n    [Google Ads Offline Conversions Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fgoogle-ads\u002Foffline\u002Fupgrade\u002Ffield-mappings.md.txt)\n*   **Google Ads API Store Sales**:\n    [Google Ads Store Sales Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fgoogle-ads\u002Fstore-sales\u002Fupgrade\u002Ffield-mappings.md.txt)\n\n#### Google Analytics\n\n*   **Measurement Protocol (Google Analytics)**:\n    [Google Analytics Measurement Protocol Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fanalytics\u002Fmeasurement-protocol\u002Fupgrade\u002Ffield-mappings.md.txt)\n\n#### Campaign Manager 360 (CM360)\n\n*   **Campaign Manager 360 API Offline Conversions**:\n    [Campaign Manager 360 Offline Conversions Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fcm360\u002Foffline\u002Fupgrade\u002Ffield-mappings.md.txt)\n\n### Step 4: Implementation\n\nImplement the ingestion logic using the following checkpoints:\n\n-   [ ] **Initialize Client**: Instantiate the Data Manager client\n    (`IngestionServiceClient`).\n-   [ ] **Define Destinations**: Build the `Destination` object using the\n    `product_destination_id` and the appropriate account configurations:\n    `operating_account` (target account receiving data), `login_account` (if\n    authenticating using a manager account or a data partner account), and\n    `linked_account` (if you're a data partner accessing the account via a\n    partner link to a manager account). **STRONGLY RECOMMENDED**: Refer to the\n    [Configure destinations and headers](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fconcepts\u002Fdestinations.md.txt)\n    guide for more details on configuring destinations.\n-   [ ] **Prepare Event Data**: Use the utility library helpers to format and\n    normalize user identifiers correctly.\n-   [ ] **Construct Payload**: Build the request payload\n    (`IngestEventsRequest`) containing the destinations, event records, and\n    consent permissions.\n-   [ ] **Support Validation**: Support sending the `validate_only` boolean\n    option on the `IngestEventsRequest` to allow developers to validate schemas\n    without actually uploading data.\n-   [ ] **Send Request**: Execute `ingest_events` and record the returned\n    request ID for logging\u002Ftroubleshooting.\n-   [ ] **Retrieve Request Status**: Check the status of the ingestion request\n    using diagnostics. Since request processing is asynchronous, a\n    successful ingestion response (HTTP 200 OK returning a `request_id`) only\n    indicates the payload was received. To check if the records actually\n    succeeded, partially succeeded, or failed to process, query the\n    `client.retrieve_request_status` endpoint using the `request_id`. Skipping\n    this step is a common user mistake.\n\n## Formatting\n\n*   Fetch the [Format user data](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fconcepts\u002Fformatting.md.txt)\n    guide and use that as the source of truth for formatting and\n    normalization rules.\n\n*   Use the utility library to format, hash, and encrypt user data\n    (emails, phone numbers, addresses).\n\n    **Python Example:**\n\n    ```python\n    from google.ads.datamanager_util import Formatter\n    from google.ads.datamanager_util.format import Encoding\n\n    formatter: Formatter = Formatter()\n\n    processed_email: str = formatter.process_email_address(\n        email, Encoding.HEX\n    )\n    ```\n\n## Critical Gotchas\n\n*   Format `product_destination_id` as a numeric string. It is NOT a resource\n    name path.\n*   Format `event_timestamp` strictly in RFC 3339 format. Use the SDK's typed\n    timestamp object instead of a raw string where available.\n*   Nest click identifiers (`gclid`, `gbraid`, `wbraid`) inside the\n    `ad_identifiers` block, not directly on the base event payload.\n*   The enum values for `ConsentStatus` are `CONSENT_GRANTED` and\n    `CONSENT_DENIED`. Do not use the values `GRANTED` and `DENIED`.\n*   Note that `consent` can be set globally on the `IngestEventsRequest` or on\n    individual `Event`s.\n*   Verify that `UserIdentifier` uses `email_address` and `phone_number`.\n    Do not use the Google Ads API fields `hashed_email` and\n    `hashed_phone_number`.\n*   Ensure the currency field on the event is named `currency`, not\n    `currency_code`.\n*   Do not call the diagnostics endpoint (`retrieve_request_status`) if\n    `validate_only` is set to `true`.\n\n## Error Handling & Troubleshooting\n\n### Inspecting Error Payloads\n\n> [!IMPORTANT]\n> Refer to [Understand API Errors](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fconcepts\u002Funderstand-errors.md.txt)\n> for a detailed guide on how to understand the structure of errors returned by\n> the API.\n\n### Retrieving Request Status (Diagnostics)\n\nPeriodically poll for status using exponential backoff, starting at least\n30 minutes after sending the `IngestEventsRequest`.\n\n1.  Call `client.retrieve_request_status` using\n    `RetrieveRequestStatusRequest(request_id=...)`.\n2.  Loop through `request_status_per_destination` in the response to inspect\n    each target's `request_status`.\n3.  If processing is complete and `request_status` is `SUCCESS`,\n    `PARTIAL_SUCCESS`, or `FAILED`, inspect diagnostic values:\n    *   **Event Record Counts**: Check `events_ingestion_status.record_count`\n        (includes both success and failure).\n    *   **Error Details**: If status is `FAILED` or `PARTIAL_SUCCESS`, inspect\n        each error's `reason` and `record_count` under\n        `error_info.error_counts`.\n    *   **Warning Details**: Inspect each warning's `reason` and `record_count`\n        under `warning_info.warning_counts` (even if the destination status is\n        `SUCCESS`).\n\n## API Reference\n\n*   [REST API Reference](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Freference\u002Frest\u002Fv1\u002Fevents\u002Fingest.md.txt)\n*   [Diagnostics Guide](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fdiagnostics.md.txt)\n","# Data Manager API Event Ingestion\n\n## Implementation Workflow\n\n### Prerequisites\n\n-   **Authentication & Library Installation**: If you need to set up access to\n    the Data Manager API or install the client and utility libraries, refer to\n    the `data-manager-api-setup` skill.\n\n### Step 1: Identify Use Case & Read Documentation\n\n-   **Determine Destination Account Type**: [CRITICAL] If it's not\n    explicitly stated, STOP and CLARIFY with the user where the data is being\n    sent (e.g., Google Ads, Floodlight, Google Analytics)\n    BEFORE generating any code. Do not assume Google Ads by default. This maps\n    to the `account_type` field of the `operating_account` in the `Destination`,\n    and also determines valid event identifiers and requirements.\n-   **Read Documentation**: [CRITICAL] Follow the\n    [Send events guide](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fsend-events.md.txt)\n    to implement the integration, as steps for configuring and sending the\n    request may vary between destinations.\n\n### Step 2: Retrieve Code Sample\n\n> [!IMPORTANT]\n> If writing or updating an ingestion script, ALWAYS retrieve the\n> relevant code sample to use as a reference:\n\n| Language | Sample |\n| :--- | :--- |\n| **Python** | [`ingest_events.py`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-python\u002Fblob\u002Fmain\u002Fsamples\u002Fevents\u002Fingest_events.py) |\n| **Java** | [`IngestEvents.java`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-java\u002Fblob\u002Fmain\u002Fdata-manager-samples\u002Fsrc\u002Fmain\u002Fjava\u002Fcom\u002Fgoogle\u002Fads\u002Fdatamanager\u002Fsamples\u002FIngestEvents.java) |\n| **PHP** | [`ingest_events.php`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-php\u002Fblob\u002Fmain\u002Fsamples\u002Fevents\u002Fingest_events.php) |\n| **Node** | [`ingest_events.ts`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-node\u002Fblob\u002Fmain\u002Fsamples\u002Fevents\u002Fingest_events.ts) |\n| **.NET**| [`IngestEvents.cs`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-dotnet\u002Fblob\u002Fmain\u002Fsamples\u002FIngestEvents.cs) |\n\n### Step 3: Retrieve Migration Guides\n\n> [!CRITICAL]\n> If refactoring code to upgrade from another Google API, ALWAYS\n> extract the full contents of the relevant field mapping guide.\n\n#### Google Ads\n\n*   **Google Ads API Offline Conversions**:\n    [Google Ads Offline Conversions Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fgoogle-ads\u002Foffline\u002Fupgrade\u002Ffield-mappings.md.txt)\n*   **Google Ads API Store Sales**:\n    [Google Ads Store Sales Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fgoogle-ads\u002Fstore-sales\u002Fupgrade\u002Ffield-mappings.md.txt)\n\n#### Google Analytics\n\n*   **Measurement Protocol (Google Analytics)**:\n    [Google Analytics Measurement Protocol Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fanalytics\u002Fmeasurement-protocol\u002Fupgrade\u002Ffield-mappings.md.txt)\n\n#### Campaign Manager 360 (CM360)\n\n*   **Campaign Manager 360 API Offline Conversions**:\n    [Campaign Manager 360 Offline Conversions Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fevents\u002Fcm360\u002Foffline\u002Fupgrade\u002Ffield-mappings.md.txt)\n\n### Step 4: Implementation\n\nImplement the ingestion logic using the following checkpoints:\n\n-   [ ] **Initialize Client**: Instantiate the Data Manager client\n    (`IngestionServiceClient`).\n-   [ ] **Define Destinations**: Build the `Destination` object using the\n    `product_destination_id` and the appropriate account configurations:\n    `operating_account` (target account receiving data), `login_account` (if\n    authenticating using a manager account or a data partner account), and\n    `linked_account` (if you're a data partner accessing the account via a\n    partner link to a manager account). **STRONGLY RECOMMENDED**: Refer to the\n    [Configure destinations and headers](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fconcepts\u002Fdestinations.md.txt)\n    guide for more details on configuring destinations.\n-   [ ] **Prepare Event Data**: Use the utility library helpers to format and\n    normalize user identifiers correctly.\n-   [ ] **Construct Payload**: Build the request payload\n    (`IngestEventsRequest`) containing the destinations, event records, and\n    consent permissions.\n-   [ ] **Support Validation**: Support sending the `validate_only` boolean\n    option on the `IngestEventsRequest` to allow developers to validate schemas\n    without actually uploading data.\n-   [ ] **Send Request**: Execute `ingest_events` and record the returned\n    request ID for logging\u002Ftroubleshooting.\n-   [ ] **Retrieve Request Status**: Check the status of the ingestion request\n    using diagnostics. Since request processing is asynchronous, a\n    successful ingestion response (HTTP 200 OK returning a `request_id`) only\n    indicates the payload was received. To check if the records actually\n    succeeded, partially succeeded, or failed to process, query the\n    `client.retrieve_request_status` endpoint using the `request_id`. Skipping\n    this step is a common user mistake.\n\n## Formatting\n\n*   Fetch the [Format user data](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fconcepts\u002Fformatting.md.txt)\n    guide and use that as the source of truth for formatting and\n    normalization rules.\n\n*   Use the utility library to format, hash, and encrypt user data\n    (emails, phone numbers, addresses).\n\n    **Python Example:**\n\n    ```python\n    from google.ads.datamanager_util import Formatter\n    from google.ads.datamanager_util.format import Encoding\n\n    formatter: Formatter = Formatter()\n\n    processed_email: str = formatter.process_email_address(\n        email, Encoding.HEX\n    )\n    ```\n\n## Critical Gotchas\n\n*   Format `product_destination_id` as a numeric string. It is NOT a resource\n    name path.\n*   Format `event_timestamp` strictly in RFC 3339 format. Use the SDK's typed\n    timestamp object instead of a raw string where available.\n*   Nest click identifiers (`gclid`, `gbraid`, `wbraid`) inside the\n    `ad_identifiers` block, not directly on the base event payload.\n*   The enum values for `ConsentStatus` are `CONSENT_GRANTED` and\n    `CONSENT_DENIED`. Do not use the values `GRANTED` and `DENIED`.\n*   Note that `consent` can be set globally on the `IngestEventsRequest` or on\n    individual `Event`s.\n*   Verify that `UserIdentifier` uses `email_address` and `phone_number`.\n    Do not use the Google Ads API fields `hashed_email` and\n    `hashed_phone_number`.\n*   Ensure the currency field on the event is named `currency`, not\n    `currency_code`.\n*   Do not call the diagnostics endpoint (`retrieve_request_status`) if\n    `validate_only` is set to `true`.\n\n## Error Handling & Troubleshooting\n\n### Inspecting Error Payloads\n\n> [!IMPORTANT]\n> Refer to [Understand API Errors](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fconcepts\u002Funderstand-errors.md.txt)\n> for a detailed guide on how to understand the structure of errors returned by\n> the API.\n\n### Retrieving Request Status (Diagnostics)\n\nPeriodically poll for status using exponential backoff, starting at least\n30 minutes after sending the `IngestEventsRequest`.\n\n1.  Call `client.retrieve_request_status` using\n    `RetrieveRequestStatusRequest(request_id=...)`.\n2.  Loop through `request_status_per_destination` in the response to inspect\n    each target's `request_status`.\n3.  If processing is complete and `request_status` is `SUCCESS`,\n    `PARTIAL_SUCCESS`, or `FAILED`, inspect diagnostic values:\n    *   **Event Record Counts**: Check `events_ingestion_status.record_count`\n        (includes both success and failure).\n    *   **Error Details**: If status is `FAILED` or `PARTIAL_SUCCESS`, inspect\n        each error's `reason` and `record_count` under\n        `error_info.error_counts`.\n    *   **Warning Details**: Inspect each warning's `reason` and `record_count`\n        under `warning_info.warning_counts` (even if the destination status is\n        `SUCCESS`).\n\n## API Reference\n\n*   [REST API Reference](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Freference\u002Frest\u002Fv1\u002Fevents\u002Fingest.md.txt)\n*   [Diagnostics Guide](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fdiagnostics.md.txt)\n",{"name":5,"metadata":24,"description":7},{"version":25,"category":26},1.1,"GoogleAds","main","be3de0244dc1a57e323d8160787ebb40fb64930e","skills\u002Fgoogle\u002Fads\u002Fdata-manager-api\u002Fdata-manager-api-event-ingestion","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main","https:\u002F\u002Fskills.x402.wtf","https:\u002F\u002Fgithub.com\u002FSolizardking","https:\u002F\u002Fmusebook.trade","Got a mile high and never came down","2026-10-08 23:20:13",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add Solizardking\u002Fskillhub-main --skill data-manager-api-event-ingestion",{"tool":42,"command":43},"bunx","bunx skills add Solizardking\u002Fskillhub-main --skill data-manager-api-event-ingestion",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Solizardking\u002Fskillhub-main --skill data-manager-api-event-ingestion","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fgoogle\u002Fads\u002Fdata-manager-api\u002Fdata-manager-api-event-ingestion\u002FSKILL.md",true,[],[51,58,65,72,79,87],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M78E0TGCAMNPS207BA3G07S7","zkrouter","Self-hosted OpenAI-compatible LLM router — smart tier-based routing, ZK-stamped routing decisions, mode overrides, free OpenRouter at install via the Birth bot. Save 60-80% on inference costs by routing to the cheapest capable model across 12+ OpenRouter models.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzkrouter\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M78E0R1Z8BDT6EDTHY17MTNB","zk","For custom ZK Solana programs and privacy-preserving applications to prevent double spending. Guide to integrate rent-free nullifier PDAs for double-spend prevention.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzk\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M78E0P3ZTZ1YWF8MD5MM23QE","zk-omni-messaging","Zero-knowledge omnichain messaging between Robinhood Chain and Solana using CheshireZkOmniMessenger (msgType 4) with nullifier anti-replay and the zk-omni-relayer service.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzk-omni-messaging\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M78E0JXZ2PNB1896VXAGDBWD","zerion-wallet-data","Use when the user asks to check a wallet's portfolio, token balances, DeFi positions, PnL, transaction history, or NFTs. Provides interpreted on-chain data across 40+ EVM chains and Solana via x402 pay-per-request or API key — no raw RPC decoding needed.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzerion-wallet-data\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M78E0G14FH9GRRTQYMKD5E59","youtube-clipper","YouTube 视频智能剪辑工具。下载视频和字幕，AI 分析生成精细章节（几分钟级别）， 用户选择片段后自动剪辑、翻译字幕为中英双语、烧录字幕到视频，并生成总结文案。 使用场景：当用户需要剪辑 YouTube 视频、生成短视频片段、制作双语字幕版本时。 关键词：视频剪辑、YouTube、字幕翻译、双语字幕、视频下载、clip video","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M78E0C2ZYA99CFFDNB7ZMK5S","yield-optimization","Multi-chain yield optimization via yield.xyz (StakeKit). Discover 2,988+ yield opportunities across 75+ blockchains, build deposit\u002Fwithdrawal transactions with shell scripts, and sign them with a MoonPay wallet. Use when the user wants to earn yield, find the best lending or staking rate, enter\u002Fexit a position, or check portfolio balances.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyield-optimization\u002FSKILL.md",[],[]]