686 skills · sorted by relevance
Prepare a Python environment for Mixpanel analysis by installing required libraries and checking credentials and connectivity. Use it for first-time setup, missing dependencies, or guidance on service account and OAuth sign-in options.
Build TypeScript summary panels that combine data already fetched by other panels. Accept partial updates, wait for required fields before rendering, and update displayed metrics without additional network requests, using reusable base classes and a coordinator.
Manage servers remotely through the aaPanel/BT Panel API. Its Python tools deploy site updates, transfer and edit files, run shell commands, and execute MySQL queries, with deployment previews and backup options.
Build dashboard panels in plain TypeScript with automatic retries, saved panel settings, and clear error states. Keep panel-specific helper functions in the same file to make each component easier to understand and maintain.
Build dashboard panels in plain TypeScript using a shared Panel class. Examples cover form submission, input validation, error messages, browser storage, and immediate display updates, with a finance tracker demonstrating how the pieces fit together.
Add a complete dashboard panel in plain TypeScript, from server routes and data services to the visible component and registration. The workflow checks existing routing patterns and includes request failure handling, caching, and saved panel state.
Analyze Mixpanel data with Python to explore usage trends, conversion steps, returning users, and differences between user groups. Also manage business context documents that explain an organization's structure and goals to AI assistants.
Create a multi-panel research figure from a clear claim and fixed data references, or start from an existing figure. Plan the layout, coordinate panel creation, inspect the composite, and revise affected panels through independent review.
Panel health assessment, firm exit management, coverage gap analysis, and panel refresh brief for in-house legal ops teams. Produce an annual Panel Health Report synthesising scorecard data, billing compliance, and step-out patterns into per-firm recommendations — Retain, Watch, Improvement Plan, or Exit Review. Produce a firm exit pack: formal exit notice with active matter transition plan, plus an internal exit record. Identify practice area, geographic, or tier gaps and produce a structured Coverage Gap Report with remediation options. Produce a Panel Refresh Brief as a scoped input to the RFP process. Trigger on: 'review our panel', 'annual panel review', 'is our panel working', 'which firms should we exit', 'write the exit notice', 'coverage gap', 'we don't have anyone for restructuring', 'refresh the panel', 'panel rationalisation', 'too many firms', 'step-out problem', 'do we have the right firms'.
The English summary is being prepared. Showing the original description.
Panel structure design, firm selection criteria, right-sourcing analysis, and coverage gap assessment for in-house legal teams. Build panel frameworks from scratch or formalise existing informal arrangements. Define weighted selection criteria for firm evaluation. Run right-sourcing analysis (ABC tiering) to identify work sent to expensive providers that doesn't require that level of resource. Assess existing panels for practice area, geographic, and capability gaps. Trigger on: 'design our panel', 'how many firms do we need', 'panel structure', 'firm selection criteria', 'which firms should we use', 'right-sourcing', 'are we sending work to the right firms', 'panel gaps', 'too many firms', 'consolidate our panel', 'we need a firm for', 'preferred provider', 'panel tiers', 'do we need BigLaw for this', 'convergence', 'D&I panel targets', 'how do we choose firms'.
The English summary is being prepared. Showing the original description.
Build dashboard panels in plain TypeScript with saved sizes and expanded or collapsed states. The pattern includes data fetching retries with increasing delays, loading indicators, error messages, and a shared base class for consistent panel behavior.
Keep the ComfyUI sidebar panel node-pack (comfyui-agent-panel) in step with the orchestrator after comfyui-mcp updates. Use this whenever the orchestrator was just updated (install_comfyui (action:"self_update"), npm i -g comfyui-mcp, a new version in the ENVIRONMENT line), when a panel/bridge command fails in a way that smells like version drift ("panel is too old", a graph_/ui_ command the panel doesn't implement, a feature that works in the docs but not in the sidebar), or when the user asks to update/pin/unpin the panel. It checks the installed panel version against what THIS orchestrator build needs, RESPECTS an explicit version pin (warn-only, never move a pinned user), offers a clear way to unset the pin, runs the sync through the verified install_comfyui(action:'panel') path, and reports the version RE-READ from disk. Never claim a sync that did not happen.
The English summary is being prepared. Showing the original description.
Assemble multiple plots into ONE publication-ready multi-panel journal figure (e.g. Figure 1 with panels A, B, C). Use whenever the user asks to combine, compose, or lay out several plots as a single composite figure — newly plotted from data or from already-rendered panels the user supplies (PNG/PDF). Ask the user to pick one of two approaches: (1) redraw every panel into one unified figure using independent, tightly packed `subfigures` (each sized to its own labels, so axes need NOT align), consistent style, correctly placed panel letters, and per-panel legends/colorbars; (2) composite already-rendered PNG/PDF panels onto a mosaic canvas and add panel letters (image compositing, not plotting). Both export vector PDF + high-DPI PNG. For a SINGLE plot from a data table, use the sibling `omics-plotting` skill instead.
The English summary is being prepared. Showing the original description.
Present hosted widget documents on a connected Mac panel. Use the agent’s widget tool to prepare the document, then control whether the panel is visible and which supported document or local app destination it displays.
Build dashboard panels in plain TypeScript with automatic retries for failed requests, error messages, and retry buttons. Save expanded or collapsed state and panel dimensions in localStorage, the browser’s local storage.
Create dashboard panels in plain TypeScript using the browser’s page-building API. Follow a shared base class to add titles, counts, loading indicators, error messages, manual retry buttons, and periodically refreshed content.
Build dashboard panels in plain TypeScript with data fetching and loading states. The pattern uses cached data, fallback values, and a circuit breaker, which temporarily pauses requests after repeated failures, to handle API problems.
Build dashboard panels in vanilla TypeScript with shared loading and error displays, saved panel state, and request handling. Examples show retries with increasing delays and CircuitBreaker integration to pause repeated failures and reuse cached results.
Build dashboard panels that manage both display and data fetching. A shared TypeScript base provides loading states, retry controls, caching, automatic refresh, and a circuit breaker that temporarily pauses requests after repeated failures.
Build dashboard panels in vanilla TypeScript with resizing, saved layout state, loading indicators, and retry controls. Examples also show how to wrap existing data-fetching functions with caching and temporary request pauses after repeated failures.
Build dashboard panels with patterns for handling failed API requests. TypeScript examples cover retries, cached data, temporary pauses after repeated failures, loading and error displays, and saving panel size and expansion state in the browser.
Build dashboard panels and sidebars in plain TypeScript. Provides patterns for panels that fetch data on a timer and sidebars updated by external callers, including retries, saved display settings, and styles inserted only once.
Build dashboard panels in plain TypeScript, with regularly refreshed content, loading indicators, item counts, and error messages. Provides a shared panel class and examples for stocks, news, and weather, including retry handling and small trend charts.
Build a new dashboard or admin panel by following existing project patterns. This skill coordinates server endpoints, service logic, interface components, registration, and styling, then checks that the pieces connect consistently.