757 skills · sorted by relevance
Find npm packages that help implement or check a frontend rule, verify download counts and publishing dates, and add up to three qualifying package names to the rule file's metadata.
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.
Find npm and PyPI packages that imitate trusted package names to exploit typing mistakes. Compare spelling similarity, publication dates, downloads, and maintainer details, then rank suspicious candidates and produce reports or blocklists for further review.
Move NuGet package versions from individual .NET projects into a shared management file. The skill audits version conflicts, preserves project conditions, validates builds before and after conversion, and produces comparison files and a migration report.
Manage MATLAB packages with the in-product MATLAB Package Manager (mpm) on MATLAB R2026b or later: install, uninstall, update, search, or inspect packages; declare package dependencies in a matlab.toml project; install a shareable .mltbx package; or manage repositories. Covers dependency-resolution errors and anything involving mpminstall / mpmuninstall / mpmupdate / mpmlist / mpmsearch / mpmAddRepository / matlab.mpm.*. MATLAB *packages* are distinct from MathWorks products, toolboxes, and support packages: a bare "what packages are installed?" means MPM packages (mpmlist / matlab.mpm.Package) — this skill — unless the user explicitly says products, toolboxes, or support packages. NOT for installing MATLAB, Simulink, or toolboxes from a shell via the standalone mpm executable (the OS-level product installer), nor for listing installed products / toolboxes (ver, installedAddons) — use matlab-install-products for those.
The English summary is being prepared. Showing the original description.
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.
Guide substantial Swift changes in cmux with rules for package boundaries, dependency direction, state management, concurrency, and API documentation. Structure code so public package types can be tested without launching the app.
npm package maintenance and lifecycle management for monorepo extensions. Covers health audits, dependency sync, version bumping, changelog updates, pre-publish checks, coordinated publishing, and post-publish verification. **Triggers — use this skill when:** - User asks to "publish", "release", or "version bump" extensions/packages - User says "audit packages", "check package health", "dependency sync" - User asks to "update changelogs", "prepare release", "pre-publish check" - User mentions "npm publish", "version management", "package lifecycle" - User wants to "sync dependencies" or "align versions" across packages - User asks "what needs publishing" or "which packages changed" **Covers:** Monorepo with multiple npm packages under `extensions/`. Each package has its own package.json, CHANGELOG.md, README.md, and version. Packages are scoped (e.g. `@e9n/pi-*`) and published individually.
The English summary is being prepared. Showing the original description.
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.
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 .NET projects from templates and align them with neighboring projects and centralized package versions. Validate options, connect projects in a solution, and build the result to check that the generated structure works.
Migrate legacy .NET project files to SDK-style format, reducing repetitive XML and explicit file lists. Convert package references, move assembly metadata into project settings, and consolidate shared build and package settings across multiple projects.
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.
Prepare Remotion Studio and Canvas Capture for a product demo recorded by the user. Import the original capture into packages/brand as an editable composition, preserve cursor metadata, and upload the verified recording to remotion.media.
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.
Create and improve Playwright end-to-end tests for Studio changes. Check complete user actions, including whether settings affect requests, data survives reloads, tools return expected results, and workflows pass data correctly.
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.
Choose and run checks that cover a Verdaccio change, including affected packages, dependent packages, API tests, and relevant client or UI flows. Rebuild first and report coverage limits so passing results reflect the edited code.
Review tRPC API changes against released desktop, mobile, CLI, and SDK clients. Use release history and usage data to choose compatible changes, assess whether deprecated features can be removed, and plan recovery when deployed changes break clients.
Install PuerTS in a Unity project by selecting a version, identifying required packages and dependencies, and choosing downloads or Git URLs. The guide also covers Editor Assistant installation, verification, and Windows troubleshooting.
Use when a notebook run fails on a missing package (ImportError, ModuleNotFoundError, "there is no package called"), when you need to inspect an installed package version, or when you need to install, add, or manage Python or R packages for the notebook runtime. Covers inspect_packages, routing Python vs R through manage_packages, why in-cell %pip/!pip/install.packages() and OS installers are forbidden, restarting the kernel after an install, and when to stop and ask the user.
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.
Manual QA harness for the senpi coding agent itself. MUST USE after changing packages/ai, packages/agent, packages/coding-agent, or packages/tui — a green typecheck and `npm test` are NOT QA. Drives the real CLI from source in an isolated sandbox (never touches ~/.senpi or real credentials) across four channels: remote RPC (--mode rpc JSONL stdio), TUI smoke (node-pty on Windows, tmux on POSIX), mock loop (a local fake model server for deterministic, zero-token agent-loop runs), and CLI smoke (--help/--print/--list-models). Every helper ships a --self-test. Use whenever someone says qa senpi, test the agent, verify my change, rpc qa, tui qa, mock-loop qa, smoke the cli, or needs evidence that an agent-loop, tool, keybinding, or provider change works end to end. Capture evidence to local-ignore/qa-evidence/.
The English summary is being prepared. Showing the original description.
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
The English summary is being prepared. Showing the original description.