Advertiser New Customer Hunter

Problem Being Addressed

The current documentation only confirms that @user_c660debd/ad-hunter is a large-model skill. Its name and category suggest it is aimed at advertiser new-customer scenarios, but it does not specify inputs, outputs, or external system integration. For engineers, the immediate issue is not to treat it as a finished customer-acquisition tool, but to establish its scope boundary: it is classified as business-ops (business operations), published by user_c660debd, and any support for leads, customer records, or advertiser data must be verified against more detailed docs.

What Is Currently Visible

• Skill identifier: the canonical name is @user_c660debd/ad-hunter, displayed as “Advertiser New Customer Hunter.”
• Category: business-ops, indicating business-operations tasks rather than general text processing or low-level model tooling.
• Source: the original publisher/source is user_c660debd, which can be used to verify version and notes on the source page.
• Verifiable capability: the available material confirms the display name, canonical name, category, and source; concrete workflow steps, fields, and automation are missing.

Boundaries

Without detailed workflow documentation, do not assume it can directly run advertiser filtering, new-customer lead generation, CRM writes, or ad-delivery strategy changes. For production use, the SKILL.md should first specify task inputs, output formats, data sources, permissions, and failure handling.