[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79DNWF8ACRBP93DVG0SDG9S":3,"skill-same:01M79DNWF8ACRBP93DVG0SDG9S":51},{"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":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M79DNWF8ACRBP93DVG0SDG9S","data-manager-api-audience-ingestion",null,"Guides developers through uploading audience members to Google products using the Data Manager API \u002Fv1\u002FaudienceMembers\u002Fingest endpoint and its associated client libraries. Use this skill when the user wants to upload audience members for Customer Match, mobile device ID audiences, or any other audience use case supported by the Data Manager API. Don't use for uploading events or conversions (use the data-manager-api-event-ingestion skill).","hamzabellouch\u002Fagent-skills","hamzabellouch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F237856042?v=4","01M79BRYW7XAMK3YDWQEMTWGWS","Hamza Bellouch","01M79BRYWXQV3JK2TGVTX8GN2A",8,"MIT","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FProgramming\u002FAI_Engineering_and_Platforms\u002FAgents_and_LLM_Platforms\u002Fdata-manager-api-audience-ingestion\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: data-manager-api-audience-ingestion\ndescription: >-\n  Guides developers through uploading audience members to Google products using\n  the Data Manager API \u002Fv1\u002FaudienceMembers\u002Fingest endpoint and its associated\n  client libraries. Use this skill when the user wants to upload audience\n  members for Customer Match, mobile device ID audiences, or any other audience\n  use case supported by the Data Manager API. Don't use for uploading events or\n  conversions (use the data-manager-api-event-ingestion skill).\nmetadata:\n  version: 1.1\n  category: GoogleAds\n---\n# Data Manager API Audience 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, Display & Video 360, etc.) BEFORE generating any\n    code. Do not assume Google Ads by default. This maps to the `account_type`\n    field of the `operating_account` in the `Destination`.\n-   **Read Documentation**: [CRITICAL] Follow the upload guide for\n    your destination to implement the integration, as steps for configuring\n    and sending the request may vary between destinations:\n    *   **Google Ads Customer Match**: [Upload members to an audience](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fgoogle-ads\u002Fcustomer-match\u002Fupload-data.md.txt)\n    *   **DV360 Customer Match**: [Upload members to an audience](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fdisplay-video\u002Fcustomer-match\u002Fupload-data.md.txt)\n\n### Step 2: Retrieve Code Sample\n\n> [!IMPORTANT]\n> If writing or updating an ingestion script, ALWAYS retrieve the relevant code\n> sample to use as a reference:\n\n| Language | Sample |\n| :--- | :--- |\n| **Python** | [`ingest_audience_members.py`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-python\u002Fblob\u002Fmain\u002Fsamples\u002Faudiences\u002Fingest_audience_members.py) |\n| **Java** | [`IngestAudienceMembers.java`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-java\u002Fblob\u002Fmain\u002Fdata-manager-samples\u002Fsrc\u002Fmain\u002Fjava\u002Fcom\u002Fgoogle\u002Fads\u002Fdatamanager\u002Fsamples\u002FIngestAudienceMembers.java) |\n| **PHP** | [`ingest_audience_members.php`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-php\u002Fblob\u002Fmain\u002Fsamples\u002Faudiences\u002Fingest_audience_members.php) |\n| **Node** | [`ingest_audience_members.ts`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-node\u002Fblob\u002Fmain\u002Fsamples\u002Faudiences\u002Fingest_audience_members.ts) |\n| **.NET**| [`IngestAudienceMembers.cs`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-dotnet\u002Fblob\u002Fmain\u002Fsamples\u002FIngestAudienceMembers.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 Customer Match**:\n    [Google Ads API to Customer Match Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fgoogle-ads\u002Fcustomer-match\u002Fupgrade\u002Ffield-mappings.md.txt)\n\n#### Display & Video 360\n\n*   **Display & Video 360 API Customer Match**:\n    [Display & Video 360 API to Customer Match Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fdisplay-video\u002Fcustomer-match\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\n    the [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-   [ ] **Format User Data**: Use the utility library helpers to normalize and\n    hash user identifiers correctly.\n-   [ ] **Construct Payload**: Build the request payload\n    (`IngestAudienceMembersRequest`) containing the destinations, formatted\n    members, and consent permissions.\n-   [ ] **Support Validation**: Support sending the `validate_only` boolean\n    option on the `IngestAudienceMembersRequest` to allow developers to validate\n    schemas without actually uploading data.\n-   [ ] **Send Request**: Execute `ingest_audience_members` and record the\n    returned 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\n    `client.retrieve_request_status` using the `request_id`. Skipping this\n    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*   Only set the `address` field on `UserIdentifier` if all required fields\n    (`postal_code`, `family_name`, `given_name`, `region_code`) are present;\n    incomplete `address` fields will cause the API request to fail.\n*  `product_destination_id` must be a numeric string. It is NOT a resource\n    name.\n*   The enum values for `ConsentStatus` are `CONSENT_GRANTED` and\n    `CONSENT_DENIED`. Do not use the values `GRANTED` and `DENIED`.\n*   Field names on `UserIdentifier` are `email_address` and `phone_number`. Do\n    not use the Google Ads API field names `hashed_email` and\n    `hashed_phone_number`.\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 `IngestAudienceMembersRequest`.\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    *   **Audience Ingestion Status**: Check the data-type-specific status\n        nested under `audience_members_ingestion_status` (for example,\n        `composite_data_ingestion_status`).\n        *   **Record Count**: Check `record_count` (includes both success and\n            failure).\n        *   **Identifier Counts**: Check the data-type-specific count field\n            (e.g., `data_type_counts` for `composite_data_ingestion_status` or\n            `user_identifier_count` for `user_data_ingestion_status`; see the\n            [Diagnostics Guide](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fdiagnostics.md.txt)\n            for other status types).\n        *   **Match Rate Range**: For `user_data` and `composite_data` uploads,\n            check `upload_match_rate_range`.\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*   [Send audience members guide](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fsend-audience-members.md.txt)\n*   [REST API Reference](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Freference\u002Frest\u002Fv1\u002FaudienceMembers\u002Fingest.md.txt)\n","# Data Manager API Audience 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, Display & Video 360, etc.) BEFORE generating any\n    code. Do not assume Google Ads by default. This maps to the `account_type`\n    field of the `operating_account` in the `Destination`.\n-   **Read Documentation**: [CRITICAL] Follow the upload guide for\n    your destination to implement the integration, as steps for configuring\n    and sending the request may vary between destinations:\n    *   **Google Ads Customer Match**: [Upload members to an audience](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fgoogle-ads\u002Fcustomer-match\u002Fupload-data.md.txt)\n    *   **DV360 Customer Match**: [Upload members to an audience](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fdisplay-video\u002Fcustomer-match\u002Fupload-data.md.txt)\n\n### Step 2: Retrieve Code Sample\n\n> [!IMPORTANT]\n> If writing or updating an ingestion script, ALWAYS retrieve the relevant code\n> sample to use as a reference:\n\n| Language | Sample |\n| :--- | :--- |\n| **Python** | [`ingest_audience_members.py`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-python\u002Fblob\u002Fmain\u002Fsamples\u002Faudiences\u002Fingest_audience_members.py) |\n| **Java** | [`IngestAudienceMembers.java`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-java\u002Fblob\u002Fmain\u002Fdata-manager-samples\u002Fsrc\u002Fmain\u002Fjava\u002Fcom\u002Fgoogle\u002Fads\u002Fdatamanager\u002Fsamples\u002FIngestAudienceMembers.java) |\n| **PHP** | [`ingest_audience_members.php`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-php\u002Fblob\u002Fmain\u002Fsamples\u002Faudiences\u002Fingest_audience_members.php) |\n| **Node** | [`ingest_audience_members.ts`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-node\u002Fblob\u002Fmain\u002Fsamples\u002Faudiences\u002Fingest_audience_members.ts) |\n| **.NET**| [`IngestAudienceMembers.cs`](https:\u002F\u002Fgithub.com\u002Fgoogleads\u002Fdata-manager-dotnet\u002Fblob\u002Fmain\u002Fsamples\u002FIngestAudienceMembers.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 Customer Match**:\n    [Google Ads API to Customer Match Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fgoogle-ads\u002Fcustomer-match\u002Fupgrade\u002Ffield-mappings.md.txt)\n\n#### Display & Video 360\n\n*   **Display & Video 360 API Customer Match**:\n    [Display & Video 360 API to Customer Match Migration Field Mappings](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fdisplay-video\u002Fcustomer-match\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\n    the [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-   [ ] **Format User Data**: Use the utility library helpers to normalize and\n    hash user identifiers correctly.\n-   [ ] **Construct Payload**: Build the request payload\n    (`IngestAudienceMembersRequest`) containing the destinations, formatted\n    members, and consent permissions.\n-   [ ] **Support Validation**: Support sending the `validate_only` boolean\n    option on the `IngestAudienceMembersRequest` to allow developers to validate\n    schemas without actually uploading data.\n-   [ ] **Send Request**: Execute `ingest_audience_members` and record the\n    returned 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\n    `client.retrieve_request_status` using the `request_id`. Skipping this\n    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*   Only set the `address` field on `UserIdentifier` if all required fields\n    (`postal_code`, `family_name`, `given_name`, `region_code`) are present;\n    incomplete `address` fields will cause the API request to fail.\n*  `product_destination_id` must be a numeric string. It is NOT a resource\n    name.\n*   The enum values for `ConsentStatus` are `CONSENT_GRANTED` and\n    `CONSENT_DENIED`. Do not use the values `GRANTED` and `DENIED`.\n*   Field names on `UserIdentifier` are `email_address` and `phone_number`. Do\n    not use the Google Ads API field names `hashed_email` and\n    `hashed_phone_number`.\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 `IngestAudienceMembersRequest`.\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    *   **Audience Ingestion Status**: Check the data-type-specific status\n        nested under `audience_members_ingestion_status` (for example,\n        `composite_data_ingestion_status`).\n        *   **Record Count**: Check `record_count` (includes both success and\n            failure).\n        *   **Identifier Counts**: Check the data-type-specific count field\n            (e.g., `data_type_counts` for `composite_data_ingestion_status` or\n            `user_identifier_count` for `user_data_ingestion_status`; see the\n            [Diagnostics Guide](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Fdiagnostics.md.txt)\n            for other status types).\n        *   **Match Rate Range**: For `user_data` and `composite_data` uploads,\n            check `upload_match_rate_range`.\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*   [Send audience members guide](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Fdevguides\u002Faudiences\u002Fsend-audience-members.md.txt)\n*   [REST API Reference](https:\u002F\u002Fdevelopers.google.com\u002Fdata-manager\u002Fapi\u002Freference\u002Frest\u002Fv1\u002FaudienceMembers\u002Fingest.md.txt)\n",{"name":5,"metadata":24,"description":7},{"version":25,"category":26},1.1,"GoogleAds","main","e905af21e5f1e1c3ca605e9656c3a7930360a84e","Programming\u002FAI_Engineering_and_Platforms\u002FAgents_and_LLM_Platforms\u002Fdata-manager-api-audience-ingestion",1,"https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills","https:\u002F\u002Fhamzabellouch.github.io\u002F","https:\u002F\u002Fgithub.com\u002Fhamzabellouch","hamzabellouch.github.io","CEO & Founder of @tknoglobal | Researcher in Technology & Applied Sciences.","2026-10-17 03:20:19",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add hamzabellouch\u002Fagent-skills --skill data-manager-api-audience-ingestion",{"tool":43,"command":44},"bunx","bunx skills add hamzabellouch\u002Fagent-skills --skill data-manager-api-audience-ingestion",{"tool":46,"command":47},"pnpm","pnpm dlx skills add hamzabellouch\u002Fagent-skills --skill data-manager-api-audience-ingestion","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FProgramming\u002FAI_Engineering_and_Platforms\u002FAgents_and_LLM_Platforms\u002Fdata-manager-api-audience-ingestion\u002FSKILL.md",true,[],[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M79FHH2H815A9TAP6WNKH4Q8","security-audit","Comprehensive security guidance, source code audit, vulnerability assessment, and penetration test review for codebases, APIs, microservices, CLI tools, libraries, and LLM-backed applications. Triggers on requests to audit a codebase, conduct security reviews, find vulnerabilities or flaws, pen-test source code, or when the user asks in Arabic (فحص أمني، تدقيق الكود أمنياً، مراجعة الثغرات، فحص أمان المشروع). Supports Guidance mode (focused review) and Full Audit mode (deterministic 6-phase harness).","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FSecurity_Audit_and_Code_Review\u002Fsecurity-audit\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79FHBGXVBY6VQ1X7ETAZMF1","malware-analysis-reversing","Production malware analysis workflows, reverse engineering methodologies, isolated sandbox triage, static\u002Fdynamic binary analysis, memory forensics, and YARA detection rule authoring.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FOffensive_Security_and_Pentesting\u002Fmalware-analysis-reversing\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79FH6EACDR801TZCE4R8SAC","application-security-pentesting","Production Application Security (AppSec) standards, OWASP Top 10 vulnerability remediation, SAST\u002FDAST pipeline integration, secure code review, threat modeling, and defensive security posture.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FOffensive_Security_and_Pentesting\u002Fapplication-security-pentesting\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79FH0VKVT44FK923K520ZQA","oauth2-oidc-security-flows","Implement enterprise OAuth 2.1 and OpenID Connect (OIDC) authorization code flow with Proof Key for Code Exchange (PKCE), state and nonce verification, refresh token rotation, token revocation, and centralized IdP federation (Keycloak, Auth0, Okta). Trigger when building secure authentication, single sign-on (SSO), or third-party delegated authorization.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FIdentity_and_Access_Management_IAM\u002Foauth2-oidc-security-flows\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M79FGVVB3R4T88XXD8FRSV5B","jwt-session-management-hardening","Harden JWT-based authentication and session lifecycles using asymmetric signing (RS256\u002FEdDSA), JWKS rotation, strict claims validation, Redis-backed sliding window sessions, revocation lists, and secure HttpOnly cookie storage. Trigger when implementing token validation, session revocation, or hardening API authentication.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FIdentity_and_Access_Management_IAM\u002Fjwt-session-management-hardening\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},"01M79FGNCPZ85CVEY0B3NE4H3B","soc2-compliance-automation","Best practices for implementing SOC 2 Type II compliance controls, continuous evidence collection, infrastructure policy-as-code, and automated security monitoring. Use when automating Trust Services Criteria (Security, Availability, Confidentiality, Processing Integrity, Privacy), audit logging, IAM least privilege, or CI\u002FCD security gates.","https:\u002F\u002Fgithub.com\u002Fhamzabellouch\u002Fagent-skills\u002Fblob\u002Fmain\u002FSecurity\u002FGovernance_Compliance_and_Legal_Tech\u002Fsoc2-compliance-automation\u002FSKILL.md",[],[]]