Results for “how-to”

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 set concurrency and work-in-progress limits for support teams — chat concurrency, personal WIP on async work, and limits as quality protection rather than arbitrary caps. Trigger for "how many chats per agent", "concurrency settings", "WIP limits", "agents juggling too many tickets", async backlog per person, or quality dropping as concurrent load rises.

You are a data triager that answers data questions by routing them across a network of skills and agents. These questions may involve pulling data from a Snowflake warehouse, computing metrics, locating relevant tables or fields, diagnosing a metric change, or performing exploratory analysis. Your job is to determine how to answer a question and which skills and subagents to invoke.

You are a data triager that answers data questions by routing them across a network of skills and agents. These questions may involve pulling data from a Snowflake warehouse, computing metrics, locating relevant tables or fields, diagnosing a metric change, or performing exploratory analysis. Your job is to determine how to answer a question and which skills and subagents to invoke.

Use to quantify the revenue exposed by unresolved support failures, complaints and escalations without inflating the number. Trigger for "how much revenue is at risk", "what are these support failures costing us", "revenue behind our open escalations", building a business case for fixing a support problem, or a revenue-at-risk figure that looks too large to believe.

Researches an open-ended question — options, possible solutions, prior art, trade-offs, or how something works — and produces a durable, evidence-backed, adversarially-validated report that recommends an option without committing the team to any artifact. Use when you want to research approaches, weigh options, survey prior art or the state of the art, or understand how something works before committing to a direction. Does not diagnose a bug, failure, or root cause — use investigate. Does not specify a feature — use plan-a-feature. Does not create or update a coding standard — use coding-standard. Does not compare two concrete artifacts for gaps — use gap-analysis. Does not assess an existing module's architecture — use architectural-analysis. Does not capture feedback on Han's own skills — use han-feedback.

Expert PCI DSS compliance advisor covering PCI DSS v4.0.1 (current) and v4.0. Use this skill whenever a user asks about PCI DSS, payment card security, cardholder data protection, CDE scoping, SAQ types (A, A-EP, B, B-IP, C, C-VT, P2PE, D), ROC, AOC, QSA assessments, ASV scans, merchant levels, service provider levels, network segmentation, penetration testing, tokenisation, encryption of PAN data, or any of the 12 PCI DSS requirements. Also trigger for questions like "are we PCI compliant?", "how do I scope my CDE?", "which SAQ applies to us?", "what changed in PCI DSS v4.0?", "how do I prepare for a QSA audit?", or any request involving payment data security, cardholder data environment, or PCI certification readiness.

Use this skill when the user asks about trucking insurance — types of coverage (commercial auto, cargo, occupational accident, workers comp, bobtail/non-trucking, MCS-90 endorsement), federal minimums (49 CFR 387), what each covers, owner-operator vs company-driver implications, and how to read a Certificate of Insurance (COI). Cite 49 CFR 387.

This skill guides clinicians in sharing decision‑making when selecting an antiepileptic drug (AED) by providing quantitative estimates of each drug’s expected weight effect. It is triggered when a clinician asks how to discuss weight‑change risks when choosing an AED or what information to provide on weight effects of specific agents such as valproate versus lamotrigine.

Use to design support queues and the skill taxonomy routing rules depend on — not as an org chart mirror, but as staffable combinations of skill, priority and channel. Trigger for "how should we structure our queues", "too many queues", "queue design", "routing taxonomy", "catch-all queue growing", overflow rules, or redesigning queue structure before changing routing rules.

Scan a GitHub repository's contribution conventions and write them to a replaceable local instructions block. Use when joining, forking, or cloning a repository, when the user asks how issues, pull requests, base branches, or work branches should be handled, or when `AGENTS.local.md` / `CLAUDE.local.md` should reflect the repository's actual contribution rules.

Recommends a shared decision‑making process that provides patients with quantitative estimates of the expected weight effect of antidepressants to inform drug choice, also considering expected treatment length. Triggers include clinician questions such as ‘How should I discuss weight‑change risks with this patient starting an antidepressant?’ or ‘What tool can I use to show expected weight impact of sertraline vs bupropion?’.

Use when support or CS is being asked to claim a share of net revenue retention, expansion or churn reduction, to work out what can honestly be attributed and what cannot. Trigger for "how much NRR can support claim", "prove support's revenue impact", "attribute retention to CS", support ROI for a board deck, or two teams claiming the same expansion.

Use to review how call recordings are notified, stored, accessed, redacted and deleted, including the parts that differ from text conversations. Trigger for "review our call recording practices", "do we need to tell customers we're recording", "who can listen to our calls", recording retention, card details spoken on a call, or a request for a customer's own recording.

Complete bedside prescribing reference for Mirago (mirabegron, beta-3 adrenoceptor agonist) for overactive bladder — covering contraindications, safety screening, drug interactions, dose selection in special populations, titration, and administration. Use when a clinician asks how to start mirabegron, what dose to use in renal or hepatic impairment, is mirabegron safe in this patient, mirabegron drug interactions, or Mirago for OAB.

Expert in Expo for React Native development. Covers Expo Router, EAS Build and Submit, development builds, native module integration, and production deployment. Knows how to build cross-platform mobile apps efficiently while maintaining access to native capabilities. Use when "expo, react native, mobile app, eas build, expo router, ios android, expo, react-native, mobile, ios, android, eas, cross-platform" mentioned.

Recommends using weight‑neutral antipsychotic alternatives when possible and employing shared decision‑making that provides quantitative estimates of expected weight effect to guide drug choice. Triggered when a clinician asks, “How do I involve this patient in choosing an antipsychotic with minimal weight gain?” or “What resources show weight‑change projections for risperidone vs aripiprazole?”.

Use to forecast support contact volume and calculate staffing requirements for voice, chat, or async channels. Trigger for "how many agents do we need", "forecast our ticket volume", "Erlang C", workforce management or WFM planning, service level and occupancy targets, shrinkage, headcount planning for support, or when a staffing model keeps missing its service level.

Use to staff and schedule QA reviewers for sustainable throughput without grading quality collapsing — fatigue, drift, and false precision from treating reviewers like production agents. Trigger for "how many QA reviewers do we need", reviewer capacity planning, grader fatigue, throughput per reviewer, calibration after long shifts, or scores drifting over the course of a day.

Use to analyse average handle time, resolution time or time-in-queue without being misled by the skew, and to find where time actually goes. Trigger for "why is our AHT increasing", "our call handling times are up", "which contact reasons take longest", "how long do tickets take", handle time by agent or team, or an AHT target being set.

Use this skill when the user asks about Motor Vehicle Records (MVRs), 49 CFR 391.25 annual MVR review, continuous MVR monitoring services (SambaSafety, Foley, etc.), state MVR fees, what to look for on an MVR, CDLIS (Commercial Driver License Information System), or how often MVRs must be pulled. Cite 49 CFR 391.25 and 391.27.

Use this skill when the user asks about carrier-driver relationships — Independent Contractor (IC / 1099) vs Employee (W-2), Owner-Operator lease agreements, the AB5 California law, the DOL 2024 IC test, lease-purchase programs from the carrier side, settlement statements, deductions, and how to structure a compliant IC arrangement. Cite 49 CFR 376 + 1099 IRS rules.

Use to quantify what support quality failures cost — rework, credits, escalation handling, complaints and churn — with the causal limits stated. Trigger for "what do our quality failures cost", "cost of rework in support", "business case for improving quality", "how much is bad support costing us", or a quality investment that needs a number attached.

Use to compare a support data retention policy against what is actually still stored, and find both over-retention and premature deletion. Trigger for "are we deleting support data on time", "retention audit", "how long do we keep transcripts", "we still have data from 2018", conflicting retention obligations, or preparing for a data protection review.

Use this skill when the user asks about the FMCSA Drug & Alcohol Clearinghouse — full vs limited query, pre-employment vs annual query, query credit purchasing, who has access (employers, drivers, MROs, SAPs, state licensing agencies), reporting violations to the Clearinghouse, the "prohibited" status workflow, consent forms, or how to register/use the clearinghouse.fmcsa.dot.gov portal. Cite 49 CFR 382.701-727.

Use this skill when the user asks about driver fitness-for-duty programs — pre-trip readiness assessment, recognizing impairment from drugs/alcohol/medication/fatigue/mental health, refusing assignments when unfit, supervisor training on fitness assessment, FMCSA recommendations on duty status determination, and how to handle a driver who appears unfit. Reference 49 CFR 392.3 + 392.4.

Use to check whether a conversation export, dataset or AI pipeline is leaking personal data that should have been redacted, and to measure how well the redaction actually works. Trigger for "is this export safe to share", "check our redaction", "can we use support transcripts for training", sending transcripts to a vendor or model, "is there PII in this dataset", or before opening support data to a wider audience.

Guided first-run that produces a real verified win in under five minutes using the skill library on a seeded offline fixture. Load when a new user asks how to start, run the demo, try agent-loom, or get a quick win. Also triggers on "quickstart", "first run", "demo agent-loom", "try the skills", or onboarding to the library. Zero external credentials required. Idempotent — safe to run multiple times.

Use this skill when the user asks specifically about preparing for the New Entrant Safety Audit (NESA) under 49 CFR 385 Subpart D — different from a Compliance Review. Covers what auditors look at, the 18-month window, automatic failure conditions, the 60-day fix window, what to NOT do, and how to convert from "new entrant" to permanent authority. Cite 49 CFR 385.301-321.

Design execution structure for decomposed processes: single agent or multi-agent topology. Load when user says "design an agent for this", "what agent structure do I need", "architect this", "should this be multi-agent", "what's the right execution structure", "agent topology", "how should agents be organized". Takes process-decomposer output as primary input. If triggered directly without a process entry, calls process-decomposer first.

Use this skill when the user asks about the agricultural exemption from Hours of Service (HOS) rules under 49 CFR 395.1(k) — what qualifies as agricultural commodity, the 150-air-mile radius rule, state-declared planting/harvest seasons, livestock hauling specifics, and how to document operations under the exemption. Cite 49 CFR 395.1(k) and 49 USC 5117.

Use this skill when the user asks about Americans with Disabilities Act (ADA) accommodation for CDL drivers — interaction between ADA + FMCSA medical certification, when DOT-disqualifying conditions trigger ADA analysis, reasonable accommodation case examples, employer obligations, and how to handle a driver with a condition that may affect CDL status. Cite Title I ADA + 49 CFR 391.41.

When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' 'partner program,' 'referral incentive,' 'how to get referrals,' 'customers referring customers,' or 'affiliate payout.' Use this whenever someone wants existing users or partners to bring in new customers. For launch-specific virality, see launch.

A complete tour of the intelli-verse-x 5-layer stack — Leantime/GitHub at the top, Beads/Bernstein/Claude-Squad in the middle, Gas Town as the multi-project fabric, and LiteLLM/Infisical/Langfuse/n8n/GH-Actions underneath. Use whenever the user asks "what does X service do", "where does Y data live", "how do I get to Z", or you need to understand which tool to reach for. This is the architecture map.

Use to draw a defensible sample of support conversations for QA review, an audit or a manual analysis, so the results generalise to the population rather than to whatever was easy to pull. Trigger for "which tickets should we review", "how do we pick a sample", "is our QA sampling representative", stratified or risk-based sampling, review coverage design, or a finding based on a handful of hand-picked tickets.

Codebase-wide Retrieval-Augmented Generation for deep code understanding. Use when: (1) Answering questions about large codebases by searching across all files, (2) Finding related code patterns, implementations, or dependencies across a project, (3) Building context from multiple files before making changes, (4) Understanding how a feature works end-to-end across the codebase, (5) Tracing data flow through multiple modules