2.3K skills · sorted by relevance
Use when a carrier asks about autonomous trucks — current state of Level 4 development, major programs (Aurora, Kodiak, Plus, Waymo Via, Embark history), regulatory status, operational implications, hub-to-hub model, driver impact, insurance, and what carriers should be doing now (or not doing) to prepare.
The English summary is being prepared. Showing the original description.
Use this skill when the user asks about FMCSA Compliance Safety Accountability (CSA) program scoring — the seven BASIC categories, BASIC Severity Indicator (BSI), peer percentiles, intervention thresholds, how violations age out, SMS Methodology, ISS (Inspection Selection System), what "alert" status means, Safety Measurement System mechanics, or DataQ disputes. Cite SMS Methodology v3.20.
The English summary is being prepared. Showing the original description.
Design dashboards for migrations and runtimes. Use for authority drift, verifier status, burn-down, runtime health, or pain panels. NOT for vanity analytics, ad hoc charts, or duplicate reporting.
The English summary is being prepared. Showing the original description.
Use when applying Cloudflare D1 migrations, fighting Supabase migration history vs SQL execution, choosing direct psql over CLI, designing idempotent migrations, debugging schema drift between local and remote, or recovering after a half-applied migration. Triggers: supabase migration repair instructions appearing, table missing after "applied" status, "Tenant or user not found" when running psql, --remote vs --local D1 confusion, NOT NULL on a populated column, foreign key constraint failures, drift between staging and prod schemas. NOT for Mongo/document migrations, ORM-managed migrations specifically (Prisma/Drizzle have their own conventions), or pure data backfills.
The English summary is being prepared. Showing the original description.
Audit whether an enforced-coordination MCP has actually shrunk its ~19 legacy etiquette verbs into the 5 enforced tools — work/act/ask/recall/status — each carrying one denial shape and one transcript event, migrated through a real retirement path (intake-metadata, alias, or doc-history — never a parallel runtime), with zero legacy-verb calls once a body reaches compliance mode C4+. Use when reviewing a broker-collapse migration plan, gating a body's move from advisory (C0-C3) to enforced (C4+) coordination, or verifying IT-018 Broker Collapse compliance. NOT for the inbound trigger→spawn boundary that decides whether an event may spawn an agent at all (use fleet-event-spawn-trust), the capability-token cryptographic mechanism behind a denial (use agentic-zero-trust-security), designing how a swarm of agents invokes and shards work (use swarm-invocation-designer), or auditing an individual PR's mergeability (use agent-pr-authoring).
The English summary is being prepared. Showing the original description.
Monitor a Coval run's progress with live updates. Use when user wants to check run status or wait for completion.
The English summary is being prepared. Showing the original description.
Google SEO APIs: Search Console (Search Analytics, URL Inspection, Sitemaps), PageSpeed Insights v5, CrUX field data with 25-week history, Indexing API v3, and GA4 organic traffic. Provides real Google field data for Core Web Vitals, indexation status, search performance, and organic traffic trends. Use when user says "search console", "GSC", "PageSpeed", "CrUX", "field data", "indexing API", "GA4 organic", "URL inspection", or "real CWV data".
The English summary is being prepared. Showing the original description.
Follow-up sweep for pending third-party provider access campaigns. Use when the recurring 30-minute Provider Access Launch dispatcher wakes, or for a manual status check of due email threads, developer portals, support cases, or review deadlines.
The English summary is being prepared. Showing the original description.
Delegating work down to subagents: briefs, report statuses, independent review. Use when writing an implementer or verifier brief, dispatching a subagent to build, fix, or verify work you own, or a subagent reports DONE, blocked, or concerns. NOT for campaign-scale doctrine (use campaign-pattern).
The English summary is being prepared. Showing the original description.
Custom-entry fix for pickers with no way to add a choice (Select, Popover list, DropdownMenu). Use when building or touching any choice control (tier, category, tag, status, owner), `pnpm check:picker-add` names a file, running Pattern Patrol P13, or the user says 'no way to add my own' or 'why can't I type a new one'.
The English summary is being prepared. Showing the original description.
Context and scope-tagging UI. Use when adding a context picker to a surface, tagging an entity to scopes, setting or filtering by the active (working) context, showing per-entity context status, prompting for context on upload, or editing context-assignment/**, active-context/**, or appContextSlice.
The English summary is being prepared. Showing the original description.
A set of resources for writing internal communications in company-preferred formats. Use when asked to draft status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, or project updates.
The English summary is being prepared. Showing the original description.
Access Google Search Console for SEO data such as queries, clicks, impressions, rankings, and indexing status across sites. Use when diagnosing search performance or indexing issues.
The English summary is being prepared. Showing the original description.
Gives coding agents temporal awareness by reading the session transcript the host already writes, so the agent stops guessing about time and stops repeating commands that just failed. Activates whenever an agent reasons about recency, elapsed time, retry windows, deploy cooldowns, memory or file staleness, idle detection, or any "when / how long ago / how long did that take" question. Required for autonomous, parallel, or long-running agents.
The English summary is being prepared. Showing the original description.
Fast, concise sprint snapshot — burndown and emerging risks for situational awareness. 'How is the sprint going?'
The English summary is being prepared. Showing the original description.
Closes a finished story: verifies each acceptance criterion, checks for design or ADR deviations and updates its status. Use when the user says a story is done, finished or ready to close.
The English summary is being prepared. Showing the original description.
Expert knowledge of vilkår / vilkårsvurdering (requirements evaluation) in melosys-api. Use when: (1) Understanding inngangsvilkår structure for FTRL bestemmelser (VilkårForBestemmelse), (2) Debugging Vilkaarsresultat / oppfylt status or begrunnelser, (3) Understanding avklarte fakta (AvklarteFaktaForBestemmelse) collection, (4) Investigating why a vilkår fails or which vilkår a bestemmelse requires. Triggers: vilkår, vilkaar, vilkaarsresultat, vilkårsvurdering, oppfylt, begrunnelse, inngangsvilkår, avklarte fakta, FTRL_2_5, FTRL_2_8, VilkårForBestemmelse.
The English summary is being prepared. Showing the original description.
Expert knowledge of REST endpoint patterns in melosys-api's frontend-api module. Use when: (1) Creating new REST endpoints for melosys-web, (2) Understanding controller patterns and Swagger documentation, (3) Working with DTOs and request/response objects, (4) Understanding exception handling and HTTP status codes, (5) Adding access control to endpoints. Triggers: "new endpoint", "REST controller", "@RestController", "add a DTO", "ResponseEntity", "Aksesskontroll", "access control on endpoint", "Swagger/@Operation", "return 404/403/401/400", "@Protected", "frontend-api", "search endpoint", "/sok".
The English summary is being prepared. Showing the original description.
Expert knowledge of Fagsak (case) domain in melosys-api. Use when: (1) Understanding the fagsak lifecycle and status transitions, (2) Working with actors (aktører) - citizens, employers, authorities, (3) Debugging case creation, closure, or type/theme changes, (4) Understanding relationship between fagsak and behandling, (5) Working with EU/EEA authorities or bilateral treaty authorities. Triggers: "fagsak", "saksnummer", "MEL-", "aktør", "sakstype", "sakstema", "avslutt sak".
The English summary is being prepared. Showing the original description.
Expert knowledge of membership (medlemskap) domain in melosys-api. Use when: (1) Understanding pliktig vs frivillig membership determination, (2) Debugging medlemskapsperiode creation and updates, (3) Understanding trygdedekning combinations and rules, (4) Investigating MEDL synchronization issues, (5) Understanding membership status transitions and innvilgelsesresultat, (6) Working with UtledMedlemskapsperioder for proposal generation, (7) Understanding the relationship between bestemmelse, medlemskapstype, and trygdedekning. Triggers: medlemskapsperiode, pliktig, frivillig, trygdedekning, MEDL, innvilgelsesresultat, medlPeriodeID, bestemmelse.
The English summary is being prepared. Showing the original description.
Expert knowledge of MEDL (Medlemskapsregister) integration in melosys-api. Use when: (1) Debugging MEDL period creation/update failures, (2) Understanding data mapping between domain entities and MEDL API, (3) Working with saga steps that write to MEDL (LagreMedlemsperiodeMedl, LagreLovvalgsperiodeMedl), (4) Understanding MEDL enums (PeriodestatusMedl, LovvalgMedl, DekningMedl, GrunnlagMedl), (5) Troubleshooting Article 13 provisional vs final period logic.
The English summary is being prepared. Showing the original description.
Expert knowledge of lovvalg (law determination/applicable legislation) domain in melosys-api. Use when: (1) Understanding which EU/EEA article applies (11, 12, 13, 16), (2) Debugging LA_BUC processing and SED sending/receiving, (3) Understanding A1 attestation generation, (4) Investigating lovvalgsperiode and unntaksperiode management, (5) Understanding automatic vs manual lovvalg determination, (6) Debugging lovvalgsbeslutning status transitions, (7) Understanding the mapping between regulations and kodeverk.
The English summary is being prepared. Showing the original description.
Hands work to a local model served by LM Studio and verifies what comes back. Trigger to offload, delegate or batch work to a local, offline or on-device model; to queue unattended runs that keep only what passes; to ask which installed model fits a job or whether to switch; to size a task before delegating; when a local model returns nothing, repeats itself or drifts on a long list; when LM Studio shares the GPU with an image tool, or to free its hold; or say lmstudiorunner (audit, size, queue, run, status). Reads models from the live LM Studio API. Cloud model picks and prompt text are promptwright's; a schedule's guardrails agentwright's.
The English summary is being prepared. Showing the original description.
Runs image, video and audio generation on a local ComfyUI server and guards the GPU before long renders. Trigger to generate an image, video, audio or music locally; to run, test or check a ComfyUI workflow before a long or queued render; when a video render crashed the machine, ran out of memory or hung in VAE decode; to render while LM Studio holds the GPU; to run a pixelsmith brief locally; or say comfyrunner (audit, check, test, run, status). Refuses an untiled video decode and scores resolution times frames. Briefs and judging art are pixelsmith's; sound briefs soundsmith's; freeing LM Studio lmstudiorunner's; schedules agentwright's.
The English summary is being prepared. Showing the original description.