Results for “miles”

Produce a ready-to-run onboarding plan — pre-boarding checklist, day-1 agenda, first-week plan, and 30/60/90 ramp milestones with owners.

Takes an approved plan from docs/plans/ and drives it to an open PR. Implements it by milestones, commits per milestone in the repo's style, and opens the PR against the repo's base branch. Use whenever the user approves a plan, says "ship it", "go", "start", "implement it", "do it", or asks to open a PR for already-planned work — or in Spanish "dale", "arrancá", "implementalo", "hacelo".

Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Use at the end of sprints, projects, or milestones to reflect and improve team practices.

Creates professional GitHub issues—bug reports, feature requests, and technical tasks—with clear context, acceptance criteria, and labels for immediate action.

Consulte métricas de uso de recursos para serviços Railway. Use quando o usuário perguntar sobre uso de recursos, CPU, memória, rede, disco ou desempenho do serviço, como "quanto de memória meu serviço está usando" ou "meu serviço está lento".

Lint and format Python code for Megatron-LM using ruff, black, isort, pylint, and mypy, with commands for autoformatting and import ordering.

Multi-tiered memory management (HOT/WARM/COLD) for context compaction. Invoke ONLY for explicit compaction events: post-`/compact` cleanup, MEMORY.md tier promotion, archive batch, or "trim my context". NOT for general recall (use deep-recall) or routine memory writes (use storage-router). Triggers: "compact memory", "promote to durable", "archive old context", "tier this".

Query resource usage metrics for Railway services. Use when user asks about resource usage, CPU, memory, network, disk, or service performance like "how much memory is my service using" or "is my service slow".

Query resource usage metrics for Railway services. Use when user asks about resource usage, CPU, memory, network, disk, or service performance like "how much memory is my service using" or "is my service slow".

Use when a carrier asks about tire program design, when to retread vs replace, position management (steer vs drive vs trailer), inflation pressure standards, casing management, scrub rates, road-call prevention, or vendor program selection (Bridgestone, Michelin, Continental, Goodyear). Covers 49 CFR 393.75 and DOT roadside out-of-service criteria.

Write an implementation plan from an approved architecture and MVP scope. Use when the team needs milestones, workstreams, dependency ordering, acceptance criteria, and execution sequencing that connect product intent to shippable engineering work.

Manage issues, projects & team workflows in Linear. Use when the user wants to read, create or updates tickets in Linear.

Gemini: A Family of Highly Capable Multimodal Models

SKILL — Mobile UX

Python interface to OpenMS for mass spectrometry data analysis. Use for LC-MS/MS proteomics and metabolomics workflows including file handling (mzML, mzXML, mzTab, FASTA, pepXML, protXML, mzIdentML), signal processing, feature detection, peptide identification, and quantitative analysis. Apply when working with mass spectrometry data, analyzing proteomics experiments, or processing metabolomics datasets.

Geocode, POIs, routes, timezones via OpenStreetMap/OSRM.

Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials that stay internally consistent across multiple assets.

Turn a new rep's start date into a ramp that ends in quota, not confusion. Builds a 30/60/90 onboarding plan with milestones at each gate, a certification bar they have to clear before they carry full load, and the manager touchpoints that catch a slow ramp early. Built for B2B sales managers and enablement, customizable to your role and motion. Trigger on "build an onboarding plan", "30/60/90 for a new AE", "how do I ramp this rep", "certification checklist", "onboarding milestones", or any new-hire ramp.

Use this skill when the user asks about team driving — two-driver OTR operations, how teams maximize miles, HOS rules with sleeper berth swap, pay structures, equipment requirements (sleeper berth specs), team retention, and common challenges. Reference 49 CFR 395.1(g).

Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.