co-branding
Use to enforce visual, messaging, and legal standards across partner campaigns.
Discover Documentation skills, compare source repositories and read the instructions for each workflow.
Use to enforce visual, messaging, and legal standards across partner campaigns.
Use when crafting tiered ABM messaging, offers, and creative variants.
Use to track pursuit risks, owners, mitigation steps, and escalation triggers.
Use when designing copy experiments to optimize hooks, offers, and CTAs.
Use to define incident tiers, response protocols, and stakeholder communications.
Use to facilitate cross-functional journey mapping with data-backed insights.
Toolkit for coordinating system integrators, OEM partners, and service vendors in manufacturing pursuits.
Use when spacing, sequencing, and pacing multi-touch email programs.
Governance + tooling pattern for storing research artifacts, tagging, and discovery.
Use when defining data contracts, consent policies, and monitoring for automation programs.
Processes for routing community insights/actions and communicating outcomes back to members.
Method for translating product telemetry into ROI narratives and expansion triggers.
Repository blueprint for managing clinical studies, testimonials, and citations.
Use to summarize persona goals, pains, proof points, and questions for call prep.
Use to codify sales rules of engagement, escalation paths, and exception workflows.
Governance system for routing VoC insights to owners and tracking follow-through.
Best-practice kit for BI dashboard layout, storytelling, and adoption.
Library of reusable solution briefs, architecture, and pricing frames per industry.
Use when researching, segmenting, and maintaining journalist/analyst contact lists.
Step-by-step checklist for routing healthcare marketing assets through legal, medical, and privacy approvals.
Use to run pricing councils, track decisions, and enforce approval workflows.
Use when writing database access code, creating schemas, or managing transactions with PostgreSQL - enforces transaction safety with TX_ naming, read-write separation, type safety for UUIDs/JSONB, and snake_cas...
Use when starting any conversation - establishes mandatory workflows for finding and using skills, including using Read tool before announcing usage, following brainstorming before coding, and creating TodoWrit...
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.