{"id":41329,"plugin_id":"plugin_asdk_app_6a999c9511808191affcabcf3962c9d1","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T12:58:42.715Z","digest":"8cc38306b79b68900ce5b55acc1cc798f6763c09b0018d1d5cd79b53e854da45","against":null,"payload":{"description":"Turn a plain-language description of an audience into a beehiiv subscriber segment and report how many readers it matches. Use when someone wants to find, group, target, or count subscribers by engagement, tier, signup source, location, custom fields, or behaviour.","included_files":[],"name":"build-segment","skill_md_contents":"---\nname: build-segment\ndescription: Turn a plain-language description of an audience into a beehiiv subscriber segment and report how many readers it matches. Use when someone wants to find, group, target, or count subscribers by engagement, tier, signup source, location, custom fields, or behaviour.\n---\n\n# Build a segment\n\nThese are instructions for you to carry out now, in this conversation, using the beehiiv tools. Nothing runs in the background.\n\nGive the publisher a segment that matches what they meant, and proof that it does.\n\n1. **Check what exists.** List the publication's segments. If one already matches, offer it instead of making a duplicate.\n2. **Map each criterion.** Read the segment reference. When the request mentions something only the publisher would track, such as an interest, plan type, or company size, list the custom fields, because conditions on them need the field's ID. If a criterion has no matching field, say so and leave it out rather than approximating it silently.\n3. **Resolve vague words.** Terms like \"engaged\" or \"recent\" need a number. Pick a sensible default and say which one you chose.\n4. **Save and check the size.** Save a dynamic segment with a name that says who is in it, then recalculate it and read the member count. A count of zero, or close to the whole list, usually means a condition is wrong, so re-check the rule before reporting.\n5. **Report back.** Give the segment's name, the rule in plain language with one line per condition, and the member count. Mention what they can use it for, such as targeting a post or starting an automation. Creating a segment emails no one.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}