Loading...
Loading...
Found 10,799 Skills
Event prospecting skill. Takes a conference / event speakers URL, extracts the people, filters their companies against the user's ICP, then deep-researches only the speakers at ICP-fit companies. Outputs a person-first HTML report where each card answers "why should the AE talk to this person?" with all public links and a one-click DM opener. Use when the user wants to: (1) find leads at a specific conference, (2) prep for an event, (3) research event speakers, (4) build a target list from a sponsor/exhibitor page, (5) scrape conference speakers and rank by ICP fit. Triggers: "find leads at {event}", "research speakers at", "prospect this conference", "stripe sessions leads", "ai engineer summit prospects", "event prospecting", "scrape conference speakers", "who should I meet at".
Java coding standards for Spring Boot and Quarkus services: naming, immutability, Optional usage, streams, exceptions, generics, CDI, reactive patterns, and project layout. Automatically applies framework-specific conventions.
L2 AI-driven web UI testing for a React/Vite dashboard app. Originally authored against the Onsager Dashboard (the body's route table + file paths are Onsager-shaped); other React dashboards fork the procedure and substitute their own routes / test paths. Use when testing UI on PRs, triaging L1 test failures, or verifying UI behavior at desktop + mobile viewports. Triggers include "test the UI", "check the dashboard", "triage L1 failure", "run L2 tests", "validate this PR", "exploratory test the web app".
Publish Rust binaries to npm using the optionalDependencies platform package pattern. Covers the full publish pipeline, version sync, workspace:* protocol, and platform package architecture. Use when: (1) publishing Rust binaries to npm, (2) setting up the platform package pattern (main + per-OS packages), (3) debugging publish failures, (4) managing version sync across pnpm + Cargo workspaces, (5) working with workspace:* protocol. Triggers on "publish", "platform packages", "optionalDependencies", "bin.js", "version sync", "workspace protocol", "npm tag", or "prepare-publish".
Guides hands-on actuarial analyst work for insurance, reinsurance, and pension—reserving and loss development (IBNR, triangles, chain-ladder diagnostics), pricing and rate indication support (experience, trend, credibility, basic GLM at spec level), data validation and model I/O review, reporting packs and workpapers, assumption application under actuary direction, and statutory tie-outs at analyst depth. Use when the user mentions actuarial analyst, loss development, IBNR, reserve analysis, rate indication, pricing support, actuarial workpaper, triangle analysis, credibility, experience study, actuarial reporting, or reserve roll-forward—not actuary sign-off (actuary), consulting engagements (actuarial-consulting), assumption governance (assumption-setting), ALM strategy (asset-liability-management), P&C legal depth (property-casualty-insurance), charts only (data-visualization), or ETL-only pipelines (data-scrubbing).
Guides senior system and solution architecture—cross-service boundaries, integration patterns, non-functional requirements (scale, reliability, security, cost), ADRs, C4-style modeling, architecture review, build-vs-buy, and phased migration (strangler, dual-write). Use when designing multi-service systems, evaluating platform or vendor choices, writing or reviewing architecture decision records, defining standards and principles, or assessing technical risk across domains—not for single-service RFCs and module design (senior-software-engineer), data platform or mesh decisions (data-architect), cloud landing zone, Well-Architected, and migration architecture (cloud-architect), cloud/IaC implementation (infrastructure-engineer, cloud-engineer), internal developer platform product (platform-engineer), or program tracking (technical-program-manager). For business strategy and cases, use business-consultant; for applied AI (RAG, agents, copilots), use applied-ai-architect-commercial-enterprise.
Guides security assessment of embedded and cyber-physical systems on hardware-in-the-loop (HIL) test benches—bench setup, ECU/ECM or PLC targets, bus interfaces (CAN/CAN-FD, LIN, automotive Ethernet, Modbus at high level), fault injection and stimulus design, simulated plant/environment integration, attack-surface monitoring on real hardware, reproducible test cases, lab safety interlocks, and evidence capture for firmware and vehicle security teams. Use for HIL security testing, ECU security assessment, CAN bus security, PLC HIL test, fault injection lab, embedded hardware security—not web/API pentest (web-pentester), network-only pentest (network-pentester), malware/binary RE only (reverse-engineer), SOC operations (soc-analyst), AI red team (ai-redteam), classified ISSO paperwork (information-systems-security-officer-classified-specialist), or pure software CI without hardware (build-validator).
Guides actuarial consulting engagements—client scoping and SOW design, stakeholder communication (CFO, risk, boards, regulators at overview level), due diligence and M&A actuarial support, reserving/pricing/capital review programs, model validation and opinion support, regulatory interaction prep, and deliverable governance (memos, exhibits, management presentations). Use when the user mentions actuarial consulting, actuarial engagement, reserve opinion, due diligence actuarial, model validation engagement, actuarial memo, SOW actuarial, regulatory actuarial, M&A reserves, or actuarial review—not deep technical modeling execution (actuary), P&C line education only (property-casualty-insurance), legal advice (commercial-counsel), or generic management consulting without actuarial lens (business-consultant).
Guides property and casualty (P&C) insurance—commercial and personal lines, major LOBs (property, GL, workers comp, commercial auto, umbrella, specialty), underwriting and risk selection, policy triggers (occurrence vs claims-made), limits and exclusions, claims (FNOL, reserving, litigation), reinsurance and catastrophe, distribution (agents, brokers, MGAs), metrics (loss ratio, combined ratio, cat load), and state DOI/rate filing overview—not legal advice. Use for P&C insurance, property and casualty, commercial lines, workers comp, general liability, combined ratio, loss ratio, underwriting, claims-made, occurrence policy, reinsurance, catastrophe, MGA, rate filing, or FNOL—not actuarial modeling (actuary), life/health depth, legal interpretation (commercial-counsel), or GRC controls without insurance context (compliance-engineer).
Start here. Introduces what NemoClaw is, what agent skills are available, and which skill to use for a given task. Use when discovering NemoClaw capabilities, choosing the right skill, or orienting in the project. Trigger keywords - skills, capabilities, what can I do, help, guide, index, overview, start here.
For post-market review, focusing on daily review / market research / transaction summary. This Skill is mainly used in scenarios such as answering user questions, writing reports, and creating financial articles. This report generates a large amount of output and is not suitable for simple conversation scenarios. For obtaining various information and data, you can use the wind.financial.data tool with appropriate keywords or keyword combinations. After the market closes, you need to quickly review the entire day's market to understand what happened, which signals are worthy of attention, and how to respond tomorrow.
Use when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication — a re-org announcement, a tool rollout, a policy change, a benefit change, a leadership transition, a layoff, an acquisition close, or an internal product launch — and the audience is employees (not customers). Triggers on "all-hands announcement", "town-hall script", "change comms", "internal newsletter", "rollout comms", "policy change announcement", "re-org announcement", "internal FAQ", "manager talking points", "Prosci ADKAR", "Kotter 8-step", "layoff comms", "RIF comms", "internal memo". Pairs Prosci ADKAR (Awareness / Desire / Knowledge / Ability / Reinforcement) and Kotter's 8-step change model with deterministic stdlib-only Python tools to produce a sequenced touchpoint calendar, a Kotter-compliant primary announcement, an audience-segmented FAQ, and manager cascade talking points. Industry-tuned via --profile {tech-startup, scaleup, enterprise, public-company, non-profit}. Distinct from marketing-skill/* (external/customer-facing), c-level-advisor/internal-narrative (strategic framing, not tactical drafts), and c-level-advisor/change-management (executive change strategy, not the comms package itself).