2.2K skills · sorted by relevance
Manage NuGet packages, the libraries used by .NET projects, through consistent add, remove, and update procedures. Check that requested versions exist, locate their configuration, and run dependency restoration to check for errors after updates.
Guide changes to the published @kortix/sdk package with rules for preserving public APIs, writing failing tests before behavior changes, keeping the core independent of frameworks, and checking package installation. It also covers exports, streaming transport, and release version handling.
View and interact with an iOS Simulator inside the Codex browser. Display SwiftUI previews from importable Swift packages, see source edits update the running preview, and capture screenshots to document the visible results.
MUST use for ANY query mentioning packages, monorepo, workspace, catalog, turbo, turborepo, or pnpm in a multi-package context. MUST use when sharing config (ESLint, tsconfig, prettier) across packages, fixing build order between packages, adding new packages, scoping CI installs/caching to changed packages, or debugging pnpm catalog version resolution. This skill OWNS all cross-package coordination problems — even when they look like build, CI, config, or dependency issues. If two or more packages interact in the query, this skill applies. Takes priority over other skills when the problem spans package boundaries.
The English summary is being prepared. Showing the original description.
Find Laravel packages for specific features through LaraPlugins.io MCP, a connection to its package search tools. Check maintenance indicators, release history, and Laravel/PHP compatibility to compare candidates before adding a package to a project.
Manage multiple apps and shared packages in one repository. Analyze dependencies and change impacts, limit builds and tests to affected packages, configure caching, and plan repository consolidation while preserving Git history.
Manage FrontendExtension resources in frontend-forge, from creation and package generation to downloading, publishing, and unpublishing. Inspect generated files, Kubernetes jobs, and status information to diagnose packaging or publishing failures.
Prepare a pull request to main in the specified pnpm monorepo, where multiple packages share one repository. Identify affected packages, ensure Changesets release records are appropriate, run checks and builds, and write an English review submission.
List packages installed in a Unity project with their names, versions, sources, and descriptions. Filter by source or keyword, or show only direct dependencies—the packages explicitly listed in the project manifest.
Get guidance on using APM, a package manager for AI agents, to install and share reusable instructions, skills, and server configurations. Covers dependencies, package creation, authentication, policy checks, CLI commands, and troubleshooting.
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.
Use when an admin or partner needs to package an Experience Cloud (Community) site as a reusable Lightning Bolt Solution for distribution — covers the export workflow from Experience Builder, what gets bundled (ExperienceBundle, custom apps, flow categories, theme, layouts, navigation menus) versus what does NOT (data, CMS content, files), choosing Bolt vs managed package vs unlocked package vs cloning a site, sandbox-to-production promotion, multi-org distribution, AppExchange listing as a Bolt, and template versioning via the LightningBolt metadata `versionNumber`. Triggers: 'turn this community into a reusable template', 'package an Experience Cloud site to ship to multiple orgs', 'export Experience Builder template for AppExchange', 'should we use a Bolt or a managed package for this community', 'create an industry-specific community starter', 'how do we version our partner portal template', 'distribute branded Experience site across business units'. NOT for general Experience Cloud site build, content, or member setup (use admin/experience-cloud-site-setup, admin/experience-cloud-cms-content, admin/experience-cloud-member-management). NOT for shipping Apex / LWC / data-model functionality as a product (use devops/managed-package-development, devops/second-generation-managed-packages, devops/unlocked-package-development). NOT for moving a single Experience site between sandbox and prod as a one-off (use devops/experience-cloud-deployment-admin, devops/cicd-for-experience-cloud).
The English summary is being prepared. Showing the original description.
Test the Senpi adapter and task engine against the real senpi binary in an isolated environment. Check task and team behavior, record evidence in a consistent location, and verify that the existing agent directory remains untouched.
Inspect public repositories, build artifacts, and container images for software supply chain risks. The skill identifies exposed internal package names, unsafe workflow configurations, and leaked secrets, while requiring build evidence before treating unclaimed package names as exploitable.
Cooks and packages CarlaUE4 into distributable tarballs under Dist/ — either the full simulator or a standalone asset package of selected maps and props for later import. ROS2=1 keeps the native ROS 2 interface in the cooked package (a plain cook silently drops it). Use when the user asks to "package CARLA", "make a Dist build", "cook the project", "export a map as a package", "package CARLA with ROS2", or needs a build with working camera and lidar sensors.
The English summary is being prepared. Showing the original description.
Prepare and publish standalone @cline/ui releases to npm, the package registry. Covers version updates, quality checks, production and preview channels, release verification, and the initial setup that lets GitHub Actions publish the package.
Update the caniuse-lite version override in Remotion to the latest release on npm. The workflow checks the branch and working tree, updates package.json, reinstalls dependencies with Bun, then commits and pushes the change.
Set up Python projects with uv, manage required packages, and create isolated environments for each project. Covers Python versions, dependency updates, migration from existing tools, and lockfiles that record package versions for repeatable installations.
Screen dependency names on npm, PyPI, and crates.io before installation to find lookalikes of legitimate packages. This skill compares spelling patterns and registry metadata, helping review AI-generated lists, lockfile changes, and new dependencies in CI/CD.
Implement, update, test, or document TypeScript provider packages, the adapters connecting supported services and frameworks. This skill focuses on work under ts/packages/providers and directs the agent to read the provider workflow before making changes.
Create Vitest tests for Mastra playground features using MSW to simulate network responses. Exercise the real client SDK, React Query cache, and components with typed sample data to check loading, access conditions, redirects, and errors.
Guides custom map imports into CARLA on UE 5.8, from FBX geometry and OpenDRIVE road data to packaging or temporary road generation. Helps choose a supported route and verify map files and loading.
Package a CARLA Leaderboard agent into a Docker image for submission. It checks required directories and Python package files, supports ROS variants, and verifies that dependencies import and the agent loads inside the image.
Assess weaknesses in the software supply chain, from dependency packages to build pipelines and distributed artifacts. Covers authorized proof-of-concept testing, package confusion, container image risks, signing abuse, and defensive checks for tampering.