Results for “rule”

Knowledge base from "Oversubscribed: How to Get People Lining Up to Do Business with You" by Daniel Priestley. Use when applying Priestley's frameworks for demand generation, the Campaign Driven Enterprise (CDE) method, signalling, the 7-Hour Rule, products-for-prospects, becoming oversubscribed, or building a Key Person of Influence brand — or when studying or referencing the book.

Use to find where support can drive adoption, referral and retention without turning into a sales channel, and to measure whether it worked. Trigger for "can support drive growth", "support-led growth programme", "should agents mention other features", advocacy and referral from support, adoption nudges in support conversations, or a support team being given a revenue target.

Plan, execute, document, and retest authorized security assessments of AI agents and multi-agent workflows using safe adversarial cases, synthetic identities, canaries, and evidence-based findings. Use when defining red-team rules of engagement, assessing prompt injection or excessive agency, testing tool and identity boundaries, evaluating memory or cross-agent attacks, scoring a campaign, or verifying remediation in an approved environment.

Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, all blog sub-skills auto-load these files before writing or reviewing. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog".

Turn "we should run some ads" into a paid-ads plan you can hand to a buyer. Audiences, the offer per audience, the creative angles, the budget split, the metric that calls it a win, and a kill rule so you stop feeding losers. Built for B2B marketing teams, customizable to your channels and your funnel. Trigger on "build a paid ads plan", "how should we split budget", "what should the ads say", "what's our target CPL", "when do we kill a campaign", or any paid-media planning question.

Understand GitHub well enough to run a GTM context repo, no CS degree required. The mental model (repo, commit, branch, push, pull, clone), the operator's GUI-first workflow (GitHub Desktop, or let Claude Code handle the git), how to organize the repo, and the hard rules on what to never commit (CRM data, API keys, transcripts, pricing). The prerequisite to building a context repo. Fire on "what is a repo", "how does GitHub work", "learn git", "GitHub for GTM", "do I need to know GitHub", "clone the starter kit", "commit and push", "how do I organize my repo", or the start of building a GTM context repo.

Strip AI-generated tells from a draft and rewrite it in Heath's personal voice (GTM Juice). Fire whenever the user asks to "humanize", "de-AI", "clean up", "rewrite in my voice", "make this sound like me", "kill the AI tells", or "polish this draft". Also fires as the mandatory final pass inside juice-content-dispatch — every LinkedIn post, newsletter, and video script drafted there must run through this skill before the Notion write. Applies the 29-pattern Wikipedia "Signs of AI writing" catalog (em dashes, significance inflation, promotional language, rule of three, synonym cycling, inline-header lists, sycophantic tone, hyphenated word pairs, persuasive-authority tropes, signposting, etc.), then applies a hardcoded Heath-voice calibration: self-implicating first, failure-derived, plain declaratives over bumper-sticker aphorisms, no bow-tied endings, never Mixmax corporate brand voice. Forked from blader/humanizer (MIT).