3.4K skills · sorted by relevance
Accept screenshot baseline changes by running the project's dedicated script, then commit the updated version.json using the project's commit conventions. This provides an explicit command for recording changes to the screenshot comparison baseline.
Enhancement overlay — version the WHOLE deployable LLM-app artifact as one bundle: prompts + compiled programs + model snapshot pins + retrieval config + eval-set version, versioned together so a deploy is reproducible and rollback is atomic. Activate when preparing to deploy an LLM app, when asking "what exactly is running in prod right now?", when a deploy must be reproducible months later, or when an incident needs a clean rollback. The core reframe: an LLM app artifact is NOT an ML model — it is a manifest over many independently-mutable parts, not one weights file. Do NOT activate for one-off prompt edits with no deploy, for a single-component demo, or where a vendor owns the whole prompt lifecycle. For versioning ONE compiled prompt use [[agentsop-per-model-artifacts]]; for the CI comparison mechanism use [[agentsop-regression-gate]]. Search keywords: prompt versioning, reproducible deploy, what is running in prod, rollback LLM app, model pinning, prompt registry, version prompts and config.
The English summary is being prepared. Showing the original description.
Fix "backend exists on a draft version but isn't reachable from the new Compute deploy" bugs after `fastly compute publish`. Use when: (1) You ran `fastly service backend create --autoclone` (or any dashboard/CLI change that creates a draft version) but did not activate that draft, (2) You then ran `fastly compute publish` which appeared successful but your backend / ACL / header / dictionary change is missing from the active version, (3) Compute code returns backend-not-found errors or misroutes requests, (4) You're surprised to see your draft version number "skipped over" in the version chain. Root cause: `fastly compute publish` clones from the currently-active version, not from the latest draft, so dashboard changes made in an un-activated draft get stranded.
The English summary is being prepared. Showing the original description.
Automatically updates a codebase to a new language version, framework version, or library update while ensuring all tests still pass. Use this skill when migrating Python 2→3, upgrading framework versions (React, Django, Angular), updating dependencies, or performing any version migration where tests define correct behavior. The skill analyzes failing tests caused by migration, categorizes errors (import errors, API changes, type errors, behavior changes), proposes systematic fixes, and verifies that test-observable behavior remains unchanged. Triggers when users ask to migrate code versions, upgrade dependencies while keeping tests passing, update framework versions, or perform test-guided version migrations.
The English summary is being prepared. Showing the original description.
Apply semantic versioning (SemVer 2.0.0) to determine the correct version bump based on change analysis. Covers major/minor/patch classification, pre-release identifiers, build metadata, and breaking change detection. Use when preparing a new release to determine the correct version number, after merging changes before tagging, evaluating whether a change constitutes a breaking change, adding pre-release identifiers, or resolving disagreement about what version bump is appropriate.
The English summary is being prepared. Showing the original description.
View release versions claimed by open pull requests, proposed code changes, alongside work in related Conductor workspaces. Get a read-only snapshot showing queued work and the version slot that /ship would choose next.
Update release availability labels in Remotion documentation changed by a pull request. Read the version on main, increase its patch number by one, and update only the affected labels before committing and pushing.
Prepare a library release on GitHub by reviewing code changes, proposing a version number, drafting a changelog, and opening a release pull request. Version and changelog reviews let you confirm the details before proceeding.
Organize resume versions around one master document containing all experience and achievements. Track tailored copies by role or industry, apply consistent file names, and record which version was submitted to each employer.
Prepare software releases by detecting version files, reviewing changes, and writing changelogs in multiple languages. The workflow updates versions, creates annotated tags with release notes, and can publish GitHub Releases or fill in missing historical releases.
Helps developers send conversion and event data to Google Ads, Google Analytics, and Floodlight through the Data Manager API. It covers destination setup, data formatting, validation, migration from other APIs, and checking processing results.
Set up a CARLA driving evaluation environment for Leaderboard 1.0, 2.0, or 2.1. Match the simulator and scenario_runner versions, configure Python paths, and verify that the required components load correctly.
Prepare an isolated Python environment for SageMaker deployments and AWS automation. The skill selects a supported Python version, installs current AWS packages, and checks versions so installation and execution use the same environment.
Audit Reddit Ads tracking, campaign structure, community and interest targeting, creative fit, catalogs, and budgets. Receive prioritized findings grounded in account data, with missing inputs, unavailable features, and uncertainty clearly identified.
Check the Convex version installed in a project, then consult matching documentation and package type definitions to confirm API details, available exports, and command options before implementing changes or fixing version mismatch errors.
Prepare Bifrost releases by turning Git history into release summaries and module changelogs. Coordinate version updates across dependent modules, document database migration risks, and include closed issues and outside contributor credits.
Diagnose PDF conversion failures in pandoc by checking installed conversion engines, capturing full error logs, and investigating missing fonts or packages. Follow a structured sequence of retries and fallback methods to find a working conversion route.
Prepare and publish DeepChat releases through its project-specific workflow. Update versions and bilingual changelogs, run release checks, manage release branches and tags, and resume unfinished releases before publishing after release PR approval.
Explains how Squad CLI records its installed version and handles upgrades, including which files it replaces or preserves. It also covers checking npm release channels and using cached version information when assessing available updates.
Review GitHub security advisories, verify fixed versions, and update compatibility rules with narrowly scoped changes. Document upgrade steps and check that version blocking, warnings, and related configuration behave as intended.
DOCA version handling: detect the installed release and validate the four-way match across pkg-config doca-common, applications/VERSION, doca_caps --version, and bfver/mlnx-release on BlueField; reason about NGC tags; look up whether a capability exists on this release; diagnose build-vs-runtime drift. Load it alongside doca-debug when a symptom smells of version skew: "built but nothing on the wire", "undefined reference to a symbol the docs claim exists", "DOCA_ERROR_NOT_SUPPORTED at runtime", "what does latest mean for this tag", or "is my LTS still supported". Once all four sources match, the component's build / run workflow belongs to its own library, service or tool skill. Refuse install / package choice (doca-setup), per-library API questions (matching library skill), DOCA_ERROR_* taxonomy (doca-programming-guide), and the general debug ladder (doca-debug).
The English summary is being prepared. Showing the original description.
Use when the user asks to "set up conversion values so tROAS optimizes profit not orders", "map margin onto my purchase value", "build value rules for lead / phone / signup conversions", or "stop bidding to revenue when I care about profit"; defines and QAs the conversion VALUE model — per-conversion values, margin/net-value adjustment, static-vs-dynamic value rules, proxy values for non-revenue actions, and a value-vs-count sanity check — as a value-model spec plus a pre-launch value QA sheet. Not for whether the tag fires or UTMs are clean — use conversion-signal-qa; not for cross-platform double-count de-dup — use attribution-reconciler; not for scoring R1/R2 — that is a scored veto in ad-account-auditor. 付费广告转化价值建模/利润出价/价值规则QA
The English summary is being prepared. Showing the original description.
Check and compare software component versions on SageMaker HyperPod cluster nodes - NVIDIA drivers, CUDA toolkit, cuDNN, NCCL, EFA, AWS OFI NCCL, GDRCopy, MPI, Neuron SDK (Trainium/Inferentia), Python, and PyTorch. Use when checking component versions, verifying CUDA/driver compatibility, detecting version mismatches across nodes, planning upgrades, documenting cluster configuration, or troubleshooting version-related issues on HyperPod. Triggers on requests about versions, compatibility, component checks, or upgrade planning for HyperPod clusters.
The English summary is being prepared. Showing the original description.
Convert .NET projects and solutions (.sln, .slnx) to NuGet Central Package Management (CPM) using Directory.Packages.props. USE FOR: converting to CPM, centralizing or aligning NuGet package versions across multiple projects, inlining MSBuild version properties from Directory.Build.props into Directory.Packages.props, resolving version conflicts or mismatches across a solution or repository, updating or bumping or syncing package versions across projects. Also activate when packages are out of sync, drifting, or inconsistent -- even without the user mentioning CPM. Provides baseline build capture, version conflict resolution, build validation with binlog comparison, and a structured post-conversion report. DO NOT USE FOR: packages.config projects (must migrate to PackageReference first) or repositories that already have CPM fully enabled.
The English summary is being prepared. Showing the original description.