2.9K skills · sorted by relevance
Run smoke tests, or basic operational checks, for Mastra projects locally or in staging and production. Verify Studio screens, agents, tools, workflows, traces, and memory, then report results, blockers, and skipped checks.
Manage Lark knowledge spaces, their members, and the hierarchy of document entries. Create spaces and entries, browse their structure, and move or copy entries to organize where team documents and shortcuts are located.
Manage NodeGroup resources in a KubeSphere environment, including creation, updates, and deletion. Bind or unbind nodes, namespaces, and workspaces, verify changes, and investigate synchronization problems or deployment settings using the bundled API script.
Run Apify Actors, programs that collect web data, through the Composio integration. Retrieve structured results, create reusable tasks with preset inputs, and inspect execution logs for both quick collection jobs and longer runs.
Investigate errors, crashes, and unexpected behavior by reproducing failures, tracing execution, and comparing logs. Tests one explanation at a time, then provides a verified fix, supporting evidence, and tests or safeguards to prevent recurrence.
Read and summarize AI research papers from Hugging Face or arXiv links and identifiers. Retrieve paper content alongside structured details about authors, related models, datasets, Spaces, and implementation links to support further investigation.
Create and manage isolated GSD workspaces with repository copies and separate planning folders. Use one command to create an environment, review active workspace status, or remove a workspace and clean up its worktrees.
Choose Stripe APIs and payment interfaces for one-time payments, subscriptions, marketplaces, and financial accounts. Helps plan, modify, or review integrations, including connected account setup, payment method storage, and migration from deprecated APIs.
Create SVG illustrations centered on one physical object, with white faces, teal sides, dark outlines, and hard shadows. Use this consistent, people-free style for onboarding steps, empty states, feature cards, and product imagery.
Guide the integration of collaboratively edited Markdown fields into an application feature. It explains service selection, permissions inherited from parent records, content storage in Loro sessions, and how to initialize and retire each editing surface.
Use when measuring or improving agent quality and performance — set up evaluators, online monitoring, CI/CD quality gates, observability, or cost optimization. Triggers on: "evaluate my agent", "add evaluator", "measure quality", "quality gate", "run evals", "agent too slow", "why is it slow", "reduce latency", "set up observability", "CloudWatch dashboard", "how much does my agent cost", "cost optimization", "logs not showing up", "logs missing", "spans not found", "eval failing", "eval error", "dev traces", "local traces", "agentcore dev traces", "traces to CloudWatch". Not for debugging errors or crashes — use agents-debug. Slow but correct routes here; broken routes to debug.
The English summary is being prepared. Showing the original description.
Connects AI agents to remote Windows desktop applications on Amazon WorkSpaces Applications (AppStream 2.0) through the managed Agent Access MCP server, and guides reliable desktop automation. Covers connecting an agent to the MCP endpoint (SigV4, streaming URL, and Active Directory SAML/Domain Join), BLOCKING vs POLLING connect modes, the computer-use tools (screenshot, click, type, key, scroll), screenshot-budget and action-batching discipline, MCP tool forwarding (forwarded___ tools), session lifecycle and expire-on-delete, and troubleshooting connection errors. Use when building or debugging an agent that drives a remote Windows desktop or GUI application via WorkSpaces Applications / AppStream — including "dcv session not ready", "client_disconnected", 400 signing-region, POLLING/connection_status, SAML assertion, or forwarded tool questions. Not for Amazon WorkSpaces Personal/Core virtual desktops or general AppStream fleet administration unrelated to agent access.
The English summary is being prepared. Showing the original description.
Expert knowledge for Playwright Workspaces development including troubleshooting, best practices, decision making, limits & quotas, security, and configuration. Use when managing Playwright Testing workspaces, tokens/RBAC, quotas, monitoring/metrics, or run/AADSTS7000112 issues, and other Playwright Workspaces related development tasks. Not for Azure App Testing (use azure-app-testing), Azure DevOps (use azure-devops), Azure Pipelines (use azure-pipelines), Azure Test Plans (use azure-test-plans).
The English summary is being prepared. Showing the original description.
Collect, normalize, and structure execution traces from instrumented programs (strace, ltrace) into JSON format for downstream analysis. Use when working with system call traces, library call traces, or execution logs that need to be analyzed for debugging, test case reproduction, or verification. Supports parsing strace/ltrace output, filtering noise, extracting debug information, and preparing traces for bug analysis or reproduction workflows.
The English summary is being prepared. Showing the original description.
Append structured execution traces across operational, cognitive, and contextual surfaces with minimal overhead. Load when inspecting agent runs, logging tool calls and observations, enabling post-run debugging, or pairing with structured-planning step IDs. Also triggers on "trace this run", "log execution", "agent observability", "run log", or when fault-localize needs evidence. Default-on during multi-step plans. Traces live at .agent-loom/traces/ — git-ignored by default.
The English summary is being prepared. Showing the original description.
Map the impact of a proposed change using real dependencies and project documentation. Identify affected code, data, interfaces, tests, and release steps, then compare the implemented changes with the plan to expose gaps and unverified risks.
Build complex interactive artifacts for claude.ai with React, Tailwind CSS, and shadcn/ui. Start from a configured project, develop interfaces with state management or navigation, and bundle the result into one shareable HTML file.
Build accessible interfaces with shadcn/ui components and Tailwind CSS styling. Create forms, tables, and layouts that adapt to screen size, then coordinate colors, spacing, and dark mode across the application.
Investigate slow Paperclip runs, page requests, and CI suites using Honeycomb traces, which show timed operations. Find relevant traces, separate overlapping work, identify dominant delays, and configure optional tracing or add missing measurements.
Design minimalist web interfaces with warm monochrome colors, clear typographic hierarchy, generous spacing, and flat card grids. Use muted pastel accents and subtle motion to create an editorial layout for product interfaces.
Manage Clockify time tracking from Claude Code with natural language requests. Create, retrieve, or delete time entries, start timers, check running entries, and view workspaces and members for reporting, activity reviews, and invoice preparation.
Fetch execution traces, records of an agent’s actions, from LangSmith Studio to debug LangChain and LangGraph agents. Inspect errors, tool calls, memory operations, execution times, and token usage, or export records for further review.
Audit URL word separators and generate hyphenated slugs, the readable parts of page addresses. Plan changes from underscores or spaces, including permanent redirects, internal link updates, and sitemap changes.
Find and compare restaurants, hotels, parks, shops, and local services in a specified area. Check details such as opening hours and photos, then present relevant options with a map when the required location data is available.