Loading...
Loading...
Found 1,248 Skills
Design a professional logo with full branding package — primary logo, variations (dark/light/icon-only), color palette, and real-world application mockups.
Implement a conformance-test runner script (Bash on macOS/Linux, PowerShell on Windows) for an arbitrary programming language, in one of two variants: install-inline (when no prepare_environment_<lang> script exists) or activate-only (when one does). Use when the user wants to add a conformance-test runner for a new language (Node.js, Go, Rust, Flutter, etc.) to a ***plain project, or wants to regenerate / adapt one of the existing runners.
Mid-conversation reflection skill that pauses execution and zooms out from detail-mode to honestly reassess direction, assumptions, and bias. Use when the user says 'reflect', 'take a step back', 'step back', 'zoom out', 'are we missing something', 'bigger picture', 'sanity check this', 'are we on track', 'are we overthinking this', 'forest for the trees', or any variation signaling intent to break out of detail-mode and reassess. Also trigger when the conversation has gone deep on implementation details without strategic check-in, or when the user shows signs of being stuck — that's often a signal the framing needs a reset, not more detail work. Intentionally low-intake: runs the 5-dimension analysis immediately when prior context is rich enough; asks one forcing clarifier only when invocation context is too thin to reassess from.
Configures the analytics side of a PostHog experiment — exposure criteria (default `$feature_flag_called` vs custom exposure events), primary and secondary metrics, the supported metric types (count, sum, ratio with `math` and `math_property`, retention with `retention_window_start` and `start_handling`), multivariate user handling ("Exclude" vs "First seen variant"), and how to read results once the experiment is live. Use when the user adds or edits a primary or secondary metric (e.g. "add a secondary metric tracking 'downloaded_file' per user"), sets up a ratio metric (e.g. "revenue from purchase_completed / pageviews"), sets up a retention metric (e.g. "$pageview → uploaded_file, 7-day window"), configures custom exposure (e.g. "only count users who hit /checkout"), changes multivariate handling, or asks "who is in the analysis?", "how do I measure impact?", "is this winning?", "what's the confidence level?", or "should I ship?".
Generate new screens from text prompts or images, edit existing screens with prompts and design system tokens, and generate design variants using Stitch MCP. Includes prompt enhancement pipeline, design mappings, professional UI/UX terminology, design tokens and theme system capabilities.
J-Link download and online debugging tool, used for device detection, firmware flashing, memory read/write, register viewing, target reset, RTT/SWO log reading, and online debugging (pause/resume/step execution/breakpoint running/call stack/variable inspection). This skill is automatically triggered when users mention J-Link, JLink, RTT, firmware flashing, memory writing, memory reading, register viewing, target reset, probe connectivity check, online debugging, step execution, breakpoint, or call stack. It also supports explicit invocation via /jlink. Even if users only say "flash the firmware", "check RTT output", or "debug", this skill should be triggered as long as the context involves a J-Link probe.
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).
Guides organizational and business storytelling—narrative structure (setup, tension, resolution), audience-tailored stories for executives, customers, boards, and teams, honest data and metrics framing, product and strategy narratives, incident and postmortem storytelling, and actuarial or insurance risk narratives for non-technical audiences. Covers story spine, key messages, and visual or slide narrative outlines. Use when the user says "tell the story", "storytelling", "narrative for executives", "data story", "board presentation narrative", "explain with a story", "story arc", "key message", "compelling narrative", "pitch story", or "incident story"—not cross-department reframing only (cross-department-translation), company-wide comms cadence and crisis wording packs (communication-lead), long-form creative fiction or screenwriting, brand copy without strategy context, or technical documentation and API reference (tech-writer-researcher).
Use when planning, running, comparing, or recording computational experiments, benchmarks, ablations, autonomous research loops, overnight runs, training runs, or exploratory variants.
Optional skill. Reconstruct a human-review-preparation file from an existing pull request, merge request, branch diff, or commit range in a repository the user trusts. Use when the user wants retrospective understanding of already-implemented changes, AI-side assessment and recommendations, and an optional provider-specific sharing variant written to a local file when needed.
Guide for migrating OCaml projects, libraries, modules, and test suites to idiomatic MoonBit. Use when translating OCaml code to MoonBit, planning a large OCaml-to-MoonBit port, preserving byte/string-heavy behavior, replacing OCaml variants/records/exceptions/refs/arrays, mapping OCaml APIs to MoonBit packages, or building verification and test strategy for a migration.
External verl end-to-end validation workflow for Megatron-Bridge model/provider changes. Covers running a small verl Megatron backend job from a Bridge checkout, choosing LoRA/DDP plus optional save/resume and parallelism variants, setting PYTHONPATH so verl imports the local Bridge tree, and reporting pass/fail evidence.