Results for “som”

Install, configure, and run Hermes Agent locally on a laptop/workstation with the full intelli-verse-x wiring — LiteLLM gateway, admin-mcp, self-hosted Firecrawl, org skills, and the IX Agency desktop app. Use when someone asks "how do I get Hermes on my machine", when bootstrapping a new employee system, or when a local install is missing MCPs/tools/skills that the org supports.

Use to surface fraud, scam and financial-crime signals that customers describe to support before detection systems see them, and to check whether agents recognised and routed them. Trigger for "are customers reporting scams", "new scam pattern targeting our customers", "did we spot the fraud signals", authorised push payment scams, "customer was coached by someone on the phone", or fraud reports arriving through support.

Use to turn a one-off support search into a standing monitor or alert that stays useful instead of being muted within a fortnight. Trigger for "alert me when a customer mentions X", "notify the team when complaints spike", "keep watching for this", "set up a daily monitor for", turning an ad-hoc sweep into something recurring, or an existing alert nobody reads any more.

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.

Expert email writing skill for professionals and individuals. Use this skill whenever the user wants to write, draft, improve, or get help with ANY email — including cold outreach, follow-ups, complaints, negotiations, thank-you notes, difficult conversations, reconnection emails, or any other professional or personal email. Also trigger for email marketing requests: promotional offers, newsletters, welcome emails, re-engagement campaigns, or clickbait-style emails. Trigger for: "help me write an email", "draft an email", "how should I phrase this email", "I need to reach out to someone", "I need to follow up", "I want to send a thank you", "I have a complaint to write", "write a newsletter", "create a welcome email", "write a promotional email", "re-engage my subscribers", or any situation where someone needs to communicate via email. Do NOT limit this to obvious requests — if the user describes a situation where an email would be the right output, use this skill proactively.

Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug directly) when the user reports errors, 500 errors, stack traces, unexpected behavior, "it was working yesterday", or is troubleshooting why something stopped working. (gstack)

Use to compare CX performance to a published or vendor benchmark without fooling yourself — scope mismatch, survivor bias, and definition mismatch usually make external benchmarks incomparable, and internal baselines often beat them. Trigger for "how do we compare to industry", "is our CSAT good", benchmark slide for the board, vendor benchmark report, "are we above average", outsourcing RFP benchmarks, or when someone cites a round-number industry standard.

A catalog of pollers worth building — the underused half of being a long-running agent. Use when something you care about could change without anyone telling you (a CI pipeline, a competitor's release, a friend's status, a config drift, a dependency CVE) and you want to be the first to notice. Companion to the `pollers` skill, which covers mechanics. This file is the menu of *what's worth polling.*

Fixa o valor da causa civel conforme os criterios do CPC (arts. 291-293) e trata a impugnacao ao valor da causa. Cobre os criterios por tipo de pedido (cobranca, ato juridico, alimentos, divisao, indenizacao com pedido liquido), a soma de pedidos cumulados, e a impugnacao na contestacao. Use quando o operador disser valor da causa, quanto colocar de valor, impugnar valor da causa, custas, ou ao redigir a inicial/contestacao.

Manage your Radarr (movies) and Sonarr (TV series) media library from the terminal. Search and browse movies/series, add new content, check calendars, view queue and download history, inspect quality profiles, and trigger searches. Use when the user mentions Radarr, Sonarr, the *arr stack, adding a movie or series, checking the library, finding something to watch, what's in the queue, download history, upcoming releases, media server setup, or movie/TV automation.

Helps users report issues with GTM skills — incorrect advice, broken activation, missing context, or unexpected behavior. Guides through gathering the right details (skill name, prompt used, actual vs expected output, context files present) and generates a properly formatted GitHub issue. Use when users say: 'this skill gave wrong advice', 'report a bug', 'file an issue', 'skill isn't working', 'wrong output', 'skill didn't activate', 'bad recommendation', 'incorrect behavior', or 'something is broken'.

Design a lead routing and SLA model someone can actually implement. The assignment rules, the round-robin or account-based logic, the SLA timers, and the fallbacks when a rep is out or a lead has no owner. Built for B2B RevOps teams, customizable to your CRM and your team shape. Trigger on "design lead routing", "who should get this lead", "build our SLA", "round robin rules", "leads are falling through", or any routing diagnostic.

Build the operator knowledge base future-you and any AI can actually search. Capture facts, playbooks, stakeholders, and how-tos as plain greppable markdown, organized so the answer is a search away instead of a memory or a Slack scroll. Trigger on "start a knowledge base", "write this down somewhere findable", "document how we do this", "who owns what again", "capture this for later", or any fact you have now looked up more than once.

YAGNI-first code-minimalism ladder — before writing code, check in order: does this need to exist? already in the codebase? stdlib? native platform feature? installed dependency? one line? Cuts unnecessary code/tokens while never trading away validation, error handling, security, or accessibility. Triggers on: 'ponytail mode', 'write minimal code', 'don't over-engineer this', 'yagni', 'is there already something for this', 'use native instead of a library', 'keep this simple', 'fewest lines possible', 'lazy senior dev mode'.

For a repository in the babysitter-users catalog, locate its babysitter processes and any committed runs (.a5c/runs/<runId>/) and perform a retrospective on a chosen run -- what went well, what failed, process suggestions, quality of effect design, breakpoint patterns -- mirroring the /babysitter:retrospect workflow but applied to an external repo. Invoke when asked to "retrospect on repo X's run", "analyze how someone else used babysitter", or "review an external babysitter run".

Verify an artifact that is about to leave the building — a partnership brief, pitch page, press release, customer email, RFP response, or any document sent to someone outside the org. Runs six checks before send — premise, confidentiality forward-test, evidence class, cold read by recipient personas, AI read, and tone metrics — and returns what to change with replacement copy. Use before sending anything outward-facing that carries customer detail, factual claims about a counterparty, or an ask.

Complete meeting lifecycle skill — preparation before and follow-up after any professional or personal meeting. Use this skill whenever the user mentions an upcoming meeting, wants to prepare for a meeting, needs an agenda, wants to brief themselves before talking to someone, needs to write up meeting notes, wants to send a follow-up email after a meeting, needs to capture action items, or says anything like "I have a meeting with...", "I just got out of a meeting", "help me prepare for...", "I need to follow up on...", or "what should I ask in this meeting." Also trigger for specific meeting types: job interviews, performance reviews, 1:1s, sales or client calls, and difficult conversations. Both modes are covered: PRE-meeting preparation and POST-meeting follow-up. Trigger proactively even when the user doesn't use the word "meeting" — if they describe a situation where they're about to talk to someone important, or just finished such a conversation and need to capture it, this skill applies.

Build an animation from scratch, making the decisions in the order that determines whether it feels right — should it animate at all, what purpose, which tool, which properties, which curve and duration, how it interrupts, how it exits. Writes the implementation. Use when asked to animate something, add motion, make a component feel alive, or build a transition. For critiquing existing motion use `review-animations`; for auditing a whole codebase use `improve-animations`. Source: github.com/emilkowalski/skills.

Comprehensive market research and analysis skill. Use when sizing markets, conducting competitive analysis, generating professional market research reports, analyzing consumer behavior, or identifying market opportunities. Activates for: market research, market analysis, market report, TAM SAM SOM, market sizing, industry analysis, market landscape, competitive landscape, market trends, consumer research, Porter's Five Forces, PESTLE, SWOT, BCG Matrix, McKinsey-style report, consulting report, market opportunity, industry report, due diligence, M&A analysis, GTM market analysis, product-market fit validation.

Diagnose your own behavior by reading the structured logs you leave behind — turns.jsonl, events.jsonl, chat_history.jsonl, scheduler.yaml. Use when something has gone wrong (a message didn't land, a scheduled job isn't firing, a communication pattern feels off), when you need to understand a pattern over many turns, or when cost / token usage needs auditing. Covers jq query recipes and points at the debugging-jobs / debugging-communication / debugging-drift companion guides for specific failure modes.

When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see seo-audit. For AI search optimization, see ai-seo.

Access ClinPGx pharmacogenomics data (the successor to PharmGKB) to query gene-drug interactions, CPIC/DPWG dosing guidelines, drug labels, and pharmacogene records. Use when interpreting pharmacogenes (CYP2D6, CYP2C19, TPMT, DPYD, SLCO1B1), looking up genotype-guided drug dosing, checking PGx drug-safety associations (e.g. HLA-B*57:01 and abacavir), or supporting precision medicine and clinical pharmacogenomics decisions. For star-allele definitions/frequencies see PharmVar; for germline/somatic variant pathogenicity see alterlab-clinvar. Part of the AlterLab Academic Skills suite.

Simulator.Company digital-twin & actor-agent specialist — talk to an agent AS an agent and delegate work to it. An agent is ANY actor whose `description` holds an "# Agent" competency profile (what it does, what it knows, whether it fits a task). The common case is a person: every workspace user has a 1:1 twin actor (`systemObjType="user"`) carrying that profile. But any actor can be an agent — a service/bot twin, a team or department, an organization, a process. This skill discovers the agent (`findAgent`), loads its profile (`getAgent`), adopts it as the persona, then either does the task, finds a better-suited agent, or hands the decision to the user (for a person: a task or a p2p message; for a non-person: propose another executor or run/trigger it as an actor). It is the actor-analog of `simulator-skills` (the `Skills`-form registry), but the registry is the workspace's agent actors. Use when the user wants to "delegate", "assign this to <someone/something>", "can <X> do this", "who/what should do this",

When the user wants to implement, audit, or validate structured data (schema markup) on their website. Use when the user mentions 'structured data,' 'schema.org,' 'JSON-LD,' 'rich results,' 'rich snippets,' 'schema markup,' 'FAQ schema,' 'Product schema,' 'HowTo schema,' or 'structured data errors in Search Console.' Also use when someone asks why their content isn't showing rich results or wants to improve AI search visibility. NOT for general SEO audits (use seo-audit) or technical SEO crawl issues (use site-architecture).

The YC meta-game distilled from 4000+ funded companies. Demo day prep, batch dynamics, investor updates, "launch now" mentality, talking to users obsessively. This is the playbook that turned $125K checks into trillion-dollar companies. Use when "yc, y combinator, demo day, batch, investor update, office hours, launch now, talk to users, do things that don't scale, make something people want, startup school, yc application, series a prep, post-yc, yc, startup, accelerator, demo-day, fundraising, launch, users, growth" mentioned.

Map symbol dependencies, callers, and blast radius before editing code. Load when the user asks what depends on a symbol, what breaks if they change something, blast radius of a change, reverse dependencies, or which tests cover a function. Also triggers on "who calls this", "impact of changing", "dependency map", "what uses this", "find callers", or before any non-trivial edit when safe-change is not yet active. Pairs with codebase-understanding for broad architecture; this skill is symbol-scoped and edit-gated.

Turn a buying signal into a timely, relevant touch. Read the trigger (funding, a new hire, a product launch, a job posting, a tech change), pick the angle it earns, and write the outreach while it is still fresh. Built for B2B outbound teams, customizable to your signals and your voice. Trigger on "someone just raised, what do I send", "they posted a job, draft outreach", "new VP started, reach out", "write a touch off this news", or any signal-to-message task.

Structured troubleshooting for Sage/Acorn/Lando projects — diagnoses PHP errors, Blade rendering failures, Livewire mount errors, Eloquent query issues, Acorn boot failures, queue job failures, WP hook conflicts; uses lando logs, Query Monitor, Xdebug, WP_DEBUG. Invoke for: "/debugging", "something is broken and I can't figure out why", "lando logs show an error", "acorn boot error", "blade is rendering wrong", "livewire component not mounting", "500 error", "debug this issue". Skip when: you are building or implementing features — that is /building, not debugging.

Audits and enforces web interface standards covering accessibility, performance, UX, and code quality from Vercel Engineering's Web Interface Guidelines. Use this skill when reviewing UI code, checking accessibility compliance, auditing design implementations, running pre-merge frontend checks, or when someone asks to "review my UI", "check accessibility", "check my site", "audit design", or "is this component correct". Apply proactively when writing form elements, interactive components, images, animations, or anything that users directly touch — these guidelines prevent common mistakes before they reach production.

When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.

Turn a cold start into a warm one. Build a single orientation document for a project, account, or workspace, what it is, where things live, the decisions made so far, the open items, and the next move, so a new session or a new teammate is productive in minutes instead of days. Trigger on "get me up to speed", "onboard someone to this", "what's the context here", "brief a new session", "orient me on this account", or any cold-start on work already in motion.

User-Mode Driver Framework v2 (UMDF). User-mode driver model that uses the same WDF object model as KMDF but runs in a host process (WUDFHost.exe) protected by the reflector. Required for some categories (Indirect Display Drivers, many sensor and camera drivers) and recommended for any driver that doesn't strictly need kernel mode. USE WHEN: user mentions "UMDF", "WUDFHost", "user-mode driver", "reflector", "IDD", "ISensor", "WDFHOST", "UMDF v2", "FX2" DO NOT USE FOR: KMDF (use `wdf-kmdf`), classic UMDF v1 (deprecated, COM-based)

Query NCBI ClinVar via the E-utilities API or FTP for the clinical significance (pathogenicity) of human germline genetic variants, searching by gene, variant, condition, or genomic position and interpreting ACMG/AMP classifications and review-status star ratings. Use when assessing whether a variant is pathogenic, likely pathogenic, VUS, likely benign, or benign, resolving conflicting interpretations, or annotating a VCF with ClinVar clinical significance. For population allele frequencies by ancestry use alterlab-gnomad; for somatic cancer mutation frequencies use alterlab-cosmic. Part of the AlterLab Academic Skills suite.

When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' 'ideas to grow,' 'what else can I try,' 'I don't know how to market this,' 'brainstorm marketing,' or 'what marketing should I do.' Use this as a starting point whenever someone is stuck or looking for inspiration on how to grow. For specific channel execution, see the relevant skill (ads, social, emails, etc.).

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.

Score the experience a new customer actually has, not just whether they activated. Grades the first 90 days on the moments that make someone feel taken care of, finds where the welcome goes cold, and hands back a scored audit with the specific fixes. Built for any post-sale team, customizable to your product and lifecycle. Trigger on "audit my onboarding", "score our onboarding experience", "why do new customers churn early", "grade our first 90 days", "where does onboarding go cold", "is our welcome any good", or any onboarding-quality question.