{"id":76295,"plugin_id":"plugin_asdk_app_6aceb5dd73948191a7f5c72dfb502ec8","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-02T18:11:54.799Z","digest":"0b296dd5bffd8291a8ff2bf74aad49d5eafcdaba889380a2ee5af2fe1cbade5d","against":null,"payload":{"description":"Use when choosing metros for field events using contacts at open opportunities.","included_files":[],"name":"centralize-spend-by-density","skill_md_contents":"---\nname: centralize-spend-by-density\ndescription: \"Use when choosing metros for field events using contacts at open opportunities.\"\n---\n\n# Spend by density\n\nUse when choosing metros for field events using contacts at open opportunities.\n\n## Run the play\n\nResolve the open-opportunity account set and group relevant contacts by metro using location radius filters on contacts and warm connections. State the radius, scope, location gaps, and deduplication basis. Compare contact density and available relationship owners by city. Return a ranked metro list with contact counts and named warm paths that could support invitations. This is a planning workflow, not an automatic event campaign. Verify opportunity-level buying-role filter behavior before relying on it; do not treat omitted roles as no buyer coverage.\n\n## Example prompt\n\nRank metros for a field event using contacts at our open opportunities. State the radius and data gaps, and show warm connections in each city.\n\nUse current Centralize tool schemas and returned IDs. Cite sources and mark uncertainty. Draft outreach and tasks unless requested.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}