{"found":true,"collection":"patterns","library_url":"https://www.grokbotdb.com/library/pat.steal-a-published-pack","generated":"2026-09-06T05:32:11Z","citation":["Quote the record id and its source_url (or provenance if there is no URL).","Include last_verified or observed_at when present. Do not present an old date as current.","If tier is community and confidence is low, say so. Do not launder it into a fact.","If the database does not hold the answer, say that. Do not invent Grok Bot product claims.","Contradictions are data: when conflicts_with is present, report both records rather than picking a favourite.","Deprecated and removed records stay visible. They are history, not current guidance."],"record":{"id":"pat.steal-a-published-pack","name":"Steal a published pack instead of authoring the next specialist","category":"onboarding","problem":"Authoring a specialist from a blank description is slower and worse than starting from a working one.","technique":"Start from a published pack (engineering, sales, success, outbound) or an installable template, then rescope it to your red lines.","why_it_works":"A published pack is closer to a working roster than a blank description, and the templates feature is designed for exactly this.","when_to_use":"Before spending a weekend building a specialist.","when_not_to":"Without vetting; a template carries someone else's memories and someone else's boundaries.","manual_ref":"6.2","evidence":"documented","source_url":"https://github.com/mergisi/awesome-grokbot","related":["pat.vet-an-installed-template","pat.grill-me-interview-skill"],"confidence":"high","first_seen":"2026-09-03","last_verified":"2026-09-03"}}