Loading...
Loading...
Found 1,476 Skills
Use this skill for ANY task involving jj or jujutsu version control. ALWAYS trigger when the user mentions jj, jujutsu, revsets, change IDs, bookmarks, or oplog. Also trigger when the user wants to squash, split, or reorder commits in a stack, write a revset query, absorb fixup changes, undo or restore a previous operation, resolve conflicts after rebasing, recover from force-pushes, rewrite protected/immutable commits, view change evolution (evolog), or try parallel approaches. Trigger even if "jj" is not explicitly said — "changes" instead of "commits", "stack" instead of "branch", "absorb", "squash into the right commit", "undo my last operation", "conflict after rebase", or "compare approaches in parallel" are strong jj signals. This skill contains critical non-obvious rules (like always using -m flags) that prevent broken workflows.
Expert knowledge for Azure Resource Graph development including troubleshooting, best practices, decision making, limits & quotas, configuration, and integrations & coding patterns. Use when querying via CLI/PowerShell/REST, using GET/LIST vs Query, handling paging/quotas, or deploying shared queries, and other Azure Resource Graph related development tasks. Not for Azure Monitor (use azure-monitor), Azure Policy (use azure-policy), Azure Resource Manager (use azure-resource-manager), Azure Cost Management (use azure-cost-management).
This skill should be used when the user asks about Hyperliquid whale positions, Hyperliquid liquidations, Hyperliquid open interest, Hyperliquid trader analytics, Hyperliquid taker data, smart money on Hyperliquid, or any Hyperliquid-specific query. Use when user says: 'Hyperliquid whales', 'HL whale positions', 'HL liquidations', 'HL open interest', 'HL trader', 'smart money', 'Hyperliquid大户', 'HL鲸鱼', 'HL持仓', 'HL清算', 'HL持仓量', 'HL交易员'. For general crypto prices/news, use market.
SAML SSO assertion attack playbook. Use when testing signature validation, assertion wrapping, audience restrictions, ACS handling, XML trust boundaries, and enterprise SSO flaws.
Extract Alamy stock photos in full resolution without watermarks or restrictions
Deterministic pixel art upscaling using EPX/Scale2x, hq2x/hq4x, and xBR algorithms that add valid sub-pixels through pattern recognition. Activate on 'pixel art scaling', 'EPX', 'Scale2x', 'hq2x', 'hq4x', 'xBR', 'retro game upscaling'. NOT for AI/ML upscaling, photo enlargement, or simple nearest-neighbor.
Implements keyboard, directional, and scene-level focus behavior across SwiftUI and UIKit. Use when managing @FocusState, defaultFocus, focused values, focusable interactions, focus sections, tvOS geometric focus model and Siri Remote navigation, watchOS Digital Crown focus, visionOS gaze/hover and RealityKit InputTargetComponent, macOS key view loop and Full Keyboard Access, focus restoration after presentation changes, custom focus routing with UIFocusGuide, or debugging focus with UIFocusDebugger.
Decision Coaching for Vue Component/Composable Refactoring — Users paste a piece of code or point to an SFC, and the skill first performs a diagnosis ("Fat Trunk" / "UI & IO Entanglement" / "Reactivity & Business Logic Entanglement"), then selects one from three recipes, and provides a specific sequence of extraction steps (which variable to move first, what errors the compiler will throw, how to fix them one by one, when rollback is possible). The entire process ensures behavioral equivalence through compiler green lights + step-by-step rollback, without relying on test safeguards. Trigger scenarios: Users say "This Vue component is too fat / I want to extract the logic / Split this SFC / This composable is too messy / Extract a composable / Split into humble / Pure functionalize", or point to an obviously overlong .vue / composable file and request "Refactor / Optimize / Split". Only handles Vue (Vue 2 Options, Vue 2/3 `<script setup>`, composable, pinia store). Does not handle: Adding new features (follow feature process), fixing bugs (follow issue process), cross-module architecture restructuring, backend code.
Indie Hackers platform help — the largest founder community for bootstrapped and indie businesses (~1-2M monthly visits, 165K+ entrepreneurs). Covers community engagement strategy (post types, formatting, timing), product pages (revenue milestones, transparent metrics), groups, interviews, podcast, Partner Up co-founder matching, advertising, and IH+ premium. DR75 nofollow backlinks. Use when your Indie Hackers posts aren't getting traction, product page isn't attracting interest, want more visibility among bootstrapped founders, or unsure if IH is worth the time for your launch. Do NOT use for multi-directory launch coordination (use /sales-launch-directory). Do NOT use for other launch platforms (use the platform-specific skill).
Totango platform help — SuccessBLOCs, SuccessPlays, Health Scores, Customer 360, Touchpoints, Customer Data Hub, Unison AI, Catalyst, email campaigns, REST API. Use when implementation is taking too long and you need a setup plan, SuccessPlays aren't triggering or running on the wrong accounts, health scores don't match actual churn risk, integrations keep breaking or disconnecting from Salesforce or HubSpot, reports and dashboards feel rigid and you can't build custom views, Totango API returns errors or you need to query accounts, or you're migrating to Totango from Gainsight or ChurnZero. Do NOT use for general customer success strategy (use /sales-customer-success) or NPS/CSAT survey methodology (use /sales-customer-feedback).
Use this skill whenever a user wants to deploy, host, run, or set up any project on a Linux VPS (Virtual Private Server). Triggers include: setting up a Node.js/Python/other app on a server, checking server compatibility with a project, making an app accessible online, fixing port issues, keeping an app running with PM2 or systemd, setting up tunnels (ngrok, localtunnel, pinggy), cloning private GitHub repos to a server, configuring environment variables, managing logs, enabling auto-restart on reboot, dealing with AWS/GCP firewalls, or any combination of these. Always use this skill when the user is working on a remote Linux server and wants to deploy or run any kind of application — even if they don't use the word "VPS" explicitly.
Adapt an ML paper's writing, structure, positioning, and paragraph-level narrative to a target conference such as NeurIPS, ICML, ICLR, CVPR, ACL, EMNLP, or similar venues. Use this skill whenever the user wants to submit, rewrite, polish, restructure, or tailor a paper for a specific conference; asks what good accepted/oral papers at a venue look like; wants reviewer-friendly writing; or wants section-by-section or paragraph-by-paragraph paper guidance. This is a writing and presentation skill, not an experiment-design skill.