Loading...
Loading...
Found 9,214 Skills
Cointegration testing for pairs trading using Engle-Granger, Johansen, and rolling stability analysis
Determine whether an app is ready to submit, then drive the App Store release flow with asc, including first-time submission fixes for availability, in-app purchases, subscriptions, Game Center, and App Privacy.
A method for iteratively improving text instructions for agents (skills / slash commands / task prompts / CLAUDE.md sections / code generation prompts) by having unbiased executors run them, then evaluating from both perspectives (executor self-report + instruction-side metrics). Repeat until improvement plateaus. Use immediately after creating or significantly revising a prompt or skill, or when you suspect the reason an agent isn't behaving as expected is due to ambiguity in the instructions.
Port phone numbers from other carriers into Sinch with the Porting API. Automates port-in order creation, portability checks, order tracking, on-demand activation, and webhook notifications. Use when porting numbers, checking portability, creating port-in orders, tracking port status, activating ported numbers, uploading LOA documents, or configuring porting defaults.
Generates production-grade Appium mobile automation scripts for Android and iOS in Java, Python, or JavaScript. Supports real device and emulator testing locally and on TestMu AI cloud with 100+ real devices. Use when the user asks to automate mobile apps, test on Android/iOS, write Appium tests, or mentions "Appium", "mobile testing", "real device", "app automation". Triggers on: "Appium", "mobile test", "Android test", "iOS test", "real device", "app automation", "UiAutomator", "XCUITest driver", "TestMu", "LambdaTest".
Use ShadTextarea for multi-line text input; placeholder. ShadTextareaFormField for forms with validation. Use when adding multi-line text fields or bio/description inputs in a Flutter shadcn_ui app.
Extracts the behavioral requirements, user experience (UX) flows, micro-interactions, and conditional visibility rules of a frontend component from its source code. Produces an experience.md file focused on "how it feels, behaves, and when it renders".
Kuikly Reactive Update and Directive System Development Assistant (Kuikly DSL). Guides on how to implement UI reactive updates using observable, observableList, observableSet, and the correct usage of directives such as vfor, vforIndex, vforLazy, vif, velseif, velse, vbind. Use this when you need to handle the following scenarios in Kuikly: (1) Declare reactive fields and bind them to UI attributes (2) List rendering (vfor/vforIndex/vforLazy) (3) Conditional rendering (vif/velseif/velse) (4) Value binding rendering (vbind) (5) Efficient list updates (diffUpdate) (6) Troubleshooting issues like reactive data not taking effect or UI not updating (7) CRUD operations on observableList/observableSet (8) Reactive update strategies for complex objects
Scans code for security vulnerabilities — injection flaws, authentication gaps, XSS vectors, mass assignment, CSRF, insecure deserialization, sensitive data exposure, broken access control, and misconfigurations. Generates severity-scored findings with copy-pasteable fix prompts. Trigger phrases: "security scan", "security audit", "vulnerability check", "find security issues".
Drive a PR to mergeable state — check CodeRabbit and reviewer comments, address valid ones, reply and resolve invalid ones, fix CI failures (even pre-existing ones from main), push fixes, then loop every 4.5 minutes until two consecutive clean checks. Use after opening a PR when you want it babysitted to green.
Wire a semantic layer into a nao agent so that metric queries are routed through a single source of truth. Supports dbt MetricFlow (dbt Cloud with Semantic Layer), Snowflake (views or semantic views via MCP), an in-house nao YAML semantic layer, or other tools (via MCP discovery). Installs the right MCP server, updates RULES.md to route metric queries through the semantic layer, and (for the nao YAML option) generates starter metric files. Use after a first round of tests has shown the agent struggling with metric reliability. Do not use for raw rule writing (write-context-rules) or first-time setup (setup-context).
Run a security and reliability health check on a Portaly Vibe payment integration before deployment. Trigger when the user mentions Portaly health check, payment security audit, pre-deploy check, sentry scan, callback verification audit, integration safety check, or wants to verify their Portaly payment integration is safe to go live.