27.1K skills · sorted by relevance
Rebuild modified packages in the Storybook monorepo and restart its internal UI after code changes. The workflow provides the running URL and can optionally create a UI review of stories related to the changes.
Add Storybook to a project that has no existing setup. Check the stable release to choose the installation tag, use the appropriate package manager, and hand off project-specific configuration to the separate /storybook-setup skill.
Build and review Kubernetes Operators, controllers that keep custom resources in their desired state. Included tools check resource definitions and Go reconciliation code, then assess operational capabilities and suggest improvements.
Use when configuring or troubleshooting Salesforce Enterprise Territory Management (ETM): territory models, territory types, territory hierarchies, account assignment rules, opportunity territory assignment, and forecast by territory. Trigger keywords: territory model, territory hierarchy, ETM, assign accounts to territories, territory forecast, territory activation. NOT for choosing the coverage model first — use admin/territory-design-requirements. NOT for role hierarchy — use admin/sharing-and-visibility. NOT for Field Service ServiceTerritory — use admin/fsl-service-territory-setup. Trigger keywords: Territory2, Territory2Model, Territory2Rule, territory2Model-meta.xml, ObjectTerritory2Association, UserTerritory2Association, territory assignment rule, run assignment rules, territory access level, Manage Territories permission.
The English summary is being prepared. Showing the original description.
Set up a working preview file and stories, examples showing real components, in an existing Storybook project. Check the installed version first, then follow the setup instructions produced by Storybook’s command.
Set up an existing Storybook installation with a working preview file and stories that display real components. The skill checks prerequisites, then uses Storybook’s setup command and the instructions it provides.
Launch and supervise gator agents for specific GitHub issues or pull requests in OpenShell. Check isolated execution environments, inspect logs, restart stalled agents, and test model or image overrides without changing default settings.
Add Storybook to a project that does not have it configured, choosing the installation tag based on the latest stable version. Then use the separate setup skill to configure Storybook for the project.
Helps configure persistent storage for GKE applications, including disk selection, storage requests, shared files through Filestore, and volume expansion. It also explains how disk compatibility and zone placement affect workload scheduling.
Requirements for a Salesforce Enterprise Territory Management (ETM) territory design: alignment criteria, coverage model selection, assignment rule logic, hierarchy depth and breadth, and user-to-territory ratios. Trigger keywords: territory design, territory alignment, territory model requirements, sales coverage model, territory criteria, geographic territory, named account territory, overlay territory. NOT for ETM setup steps — use admin/enterprise-territory-management. NOT for loading territory assignment data — use data/territory-data-alignment. Trigger keywords: territory design questionnaire, territory requirements document, assignment rule matrix, territory type priority, realignment plan, territory access level decision, accountAccessLevel, opportunityAccessLevel, ObjectTerritory2Association, UserTerritory2Association, Planning state model, territory acceptance tests.
The English summary is being prepared. Showing the original description.
Manage files in Google Cloud's Cloud Storage buckets, the containers that hold stored data. Upload, download, and organize content, configure access and time-limited sharing links, and manage storage lifecycle, costs, and data protection.
Upgrade an existing Storybook installation to version 11.0 or later using the official upgrade guide. If the latest stable release is below 11.0, the skill uses the 11.0 alpha, a prerelease version.
Find reusable UI components in Storybook, create or update stories that show their states, run story tests, and publish a curated review so others can inspect the results of UI changes.
Measure Storybook startup from launching the process to displaying the first story. Separate server readiness from browser rendering, summarize repeated runs, and compare versions or feature flags to investigate slower startup.
Upgrade an existing Storybook installation to version 11.0 or later using the official upgrade instructions. When the latest stable release is below 11.0, the skill directs the agent to use the 11.0 alpha release.
Set up ruvector@0.3.3 with supporting packages, register its MCP server for agent access, and verify installation with diagnostic commands and smoke tests. Helps prepare the dependencies needed for initial use of /vector subcommands.
Connect json-render interfaces to XState Store for state management. The skill shows how to adapt an atom, a container holding application state, so json-render reads and writes through it.
Identify repeated NuGet package restores across .NET build, test, and publish steps. Check whether earlier restores cover each later step, apply targeted changes, and validate the pipeline without removing required dependency restoration.
Design local data storage in Swift using actors, which control concurrent access to shared data. Combine an in-memory cache with JSON file storage, implement save and lookup operations, and connect the repository to an observable ViewModel.
Research competitors from their website URLs and turn findings into consistent Markdown profiles. Compare features, pricing, positioning, and available SEO data, with dated sources and a summary that brings multiple competitors together.
Create output schemas, definitions of result fields and display settings, for an Apify Actor by inspecting its source code. Generate dataset and output files, add key-value storage definitions when needed, and update actor.json to reference them.
Prepare and publish Windows apps to the Microsoft Store using msstore. Covers account credentials, application packaging, submission tracking, beta testing groups, gradual releases, and automated publishing through CI/CD pipelines.
Improve app store listings through keyword research, competitor comparisons, and revised titles and descriptions. Plan A/B tests, review visual messaging, and organize launch preparations for apps on Apple App Store and Google Play Store.
Inspect Google Cloud Filestore usage and free space, then propose capacity increases or decreases based on configured thresholds and storage tier limits. Apply resizing after confirmation to address low space or reduce excess capacity.