Loading...
Loading...
Found 7,703 Skills
Log information for future reference. Use when user says "fyi", "remember this", "note that", "for your info".
Conduct a systematic literature review on an academic topic. Use when the user asks for a literature review, survey, or systematic overview of a research area.
Pay people in SOL or USDC, buy and sell tokens, check prices, manage Solana wallets, stake SOL, earn yield through lending, and track portfolio performance — all from the command line. No API keys, no private key env vars. Use when the user wants to send crypto, trade, check balances, earn yield, or see how their holdings are doing.
Extract text from source documents (PDF, DOCX, PPTX, HTML, Markdown) for spreadsheet workflows. Use to understand source material before populating workbooks.
Use this skill when asked to create a GitHub issue. It handles different issue types (bug, feature, etc.) using repository templates and ensures proper labeling.
Analyze and optimize Xano workspace performance. Use when the user wants to find slow endpoints, trace execution bottlenecks, deep-dive request stacks, or understand why their Xano API is slow. Also use when the user mentions "performance," "slow endpoint," "bottleneck," "stack trace," or "optimization."
Upload IPA/PKG builds to App Store Connect and manage the full build distribution workflow. Use this skill when: (1) Uploading a build: "asc builds upload --app-id ... --file MyApp.ipa ..." (2) Checking or listing build upload records: "asc builds uploads list/get/delete" (3) Linking a build to an App Store version before submission: "asc versions set-build" (4) Adding or removing a beta group from a build for TestFlight distribution (5) Setting TestFlight "What's New" notes: "asc builds update-beta-notes" (6) User says "upload my build", "distribute to TestFlight", "set what's new", "link build to version"
Saves, retrieves, and searches structured context (reasoning, decisions, trade-offs) behind AI-generated code, linked to git commits. Use when the developer says "save this session with GitWhy", asks about past context or decisions, or wants to push context to a PR. Also use after significant implementation work, debugging sessions, or architecture decisions.
End-of-day review: check for loose ends, review pinned items, and preview tomorrow's calendar.
Use this skill when the user asks to "investigate incident", "triage this alert", "what's firing", "who got paged", "incident response", "check incident status", "SLO breaching", "error budget burned", "check service level", "SLI status", "who was notified", "check notification delivery", "verify alert routing", "MTTR", "incident severity", "error budget", "burn rate", "acknowledge incident", "resolve incident", "production incident", "what alerts are active", "incident timeline", "on-call triage", or wants to triage, manage, or respond to incidents using alerts, SLOs, and notifications.
Set remark names for MoWen UID (remark -> uid), remove remark names, and retrieve MoWen UID using remark names. A single MoWen UID can have multiple remark names. In some natural language scenarios, such as "Get the latest MoWen notes from 'Lao Chi'" or "Check the profile of 'Er Ye' on MoWen", if 'Lao Chi' or 'Er Ye' are identified as names, you can first try using the `remark` command to retrieve the corresponding UID before proceeding with subsequent operations. Triggered when setting, removing, or retrieving remark names.
Mowen Notes. Triggered when viewing someone's homepage note list, my note list, or searching for notes.