Loading...
Loading...
Found 737 Skills
Use this skill when the user says phrases like "get transcript", "transcribe video", "extract script", "help me extract it", "what does this video say", "what did this blogger say", or directly provides a video link requesting content extraction. Even if the user only sends a video link without stating their request, proactively trigger this skill if the context involves benchmark analysis or content extraction. Call video2text.py to obtain the raw transcript, use AI to correct common speech recognition errors, identify the author, and archive it to the benchmark blogger directory. Do NOT trigger for: analyzing viral content patterns (use li-analyzer), recording own topic ideas (use li-recorder), writing own scripts (use li-writer). Use when the user wants to "get transcript", "transcribe video", "extract script", or gives a video link for content extraction. Runs speech-to-text, AI proofreads, and archives to benchmark blogger directory.
Library reference for @expo/ui SwiftUI components on iOS — covers Host boundaries, modifier composition, iOS 26 Liquid Glass and Human Interface Guidelines composition rules, layout/input/navigation/display catalogues, and ObservableState patterns. Use this skill whenever writing or reviewing React Native code that imports from @expo/ui/swift-ui or @expo/ui/swift-ui/modifiers — including new Expo apps adopting native SwiftUI views, migrations from React Native primitives to expo-ui, and code targeting iOS 26 features (Liquid Glass, GlassEffectContainer, sheet detents). Trigger even if the user does not explicitly mention "expo-ui" but is writing iOS-targeted Expo UI code that should bridge to SwiftUI.
Expert-level development skill for building, debugging, reviewing, and migrating Freshworks Platform 3.0 marketplace applications. REQUIRES Node.js 24.x + FDK 10.x installed BEFORE use—checks prerequisites and refuses to proceed without them. Does NOT install or manage FDK/Node—use fw-setup skill. Before fdk validate, follow this SKILL.md Manifest + toolchain gate (fw-setup if CLI wrong, /fdk-migrate on 2.x or legacy engines, then validate—never downgrade to FDK 9/Node 18 as a shortcut except LAST RESORT after six validate iterations). New apps default to FDK 10.0.1 and Node.js 24.x; FDK 9.x/Node 18.x allowed when explicitly requested with deprecation notice. Use for: (1) Creating Platform 3.0 apps (frontend, serverless, hybrid, OAuth), (2) Debugging validation errors, (3) Migrating Platform 2.x apps to 3.0, (4) Reviewing manifest.json, requests.json, oauth_config.json, (5) Implementing Crayons UI, (6) Integrating external APIs or OAuth providers, (7) Any Freshworks Platform 3.0 app development, FDK CLI, or marketplace submission task.
Guides the agent through migrating an existing Capacitor app project from CocoaPods to Swift Package Manager (SPM) for iOS dependency management. Covers prerequisite checks, inventorying installed Capacitor plugins, backing up customized iOS project files (Info.plist, AppDelegate.swift, Assets.xcassets, Base.lproj, App.entitlements, GoogleService-Info.plist, .xcconfig files, signing configuration), deleting the existing `ios/` folder, re-scaffolding with `npx cap add ios --packagemanager SPM`, restoring preserved files, re-syncing plugins, and verifying the build. Performs all migration steps manually — does not use the interactive `npx cap spm-migration-assistant` command. Do not use for Capacitor plugin projects, app projects already on SPM, app projects without an existing `ios/` folder, or non-Capacitor mobile frameworks.
Triage and orchestrate code reviews. Analyzes PR intent, identifies touched surfaces, assesses risk, and routes to specialist skills. Does NOT perform detailed review - delegates to specialists. Supports full pipeline with "Review PR <number>" command.
Read-only Storage Analysis Assistant for macOS / Windows (auto-detects system). Scans the entire disk usage to identify space hogs, categorizes each item into three levels: 🟢 Auto-cleanable / 🟡 Manual judgment required / 🔴 Clean with caution, and provides actionable disposal plans. Generates an interactive HTML report with beautiful formatting, collapsible sections, and one-click copy commands. Also supports starting a local service to delete files directly via the web (move to trash / delete immediately). The entire scanning process is read-only. Must be used in the following scenarios: When users mention "storage analysis", "disk full", "C drive/hard disk full", "insufficient space", "clean up space", "disk cleanup", "space occupied", "what's taking up space", "help me check storage", "check computer storage/space", "storage space", "computer space insufficient", "memory full/insufficient" (in Chinese colloquial, "memory" often refers to storage), "storage analysis", "disk cleanup", "clear cache", "disk cleanup"; or when users complain about insufficient computer space, want to know what's taking up hard disk space, or need cleanup suggestions. Note: If users explicitly refer to RAM (e.g., "which process is using memory", "high memory usage", want to see Activity Monitor), that's RAM, not storage, and does not belong to this skill.
Rules and worked examples for writing prose that does not read like AI-generated slop. Consult before writing or editing any prose.
Search Twitter for trending promotional posts related to coding/AI agent tools, generate reply drafts with the pikiclaw GitHub card, and push the results to Feishu Doc along with bot notifications. Does NOT auto-post to Twitter.
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (_rich_success, _rich_warning, _rich_error, _rich_info, _rich_echo), DiagnosticCollector, STATUS_SYMBOLS, CommandLogger, or any user-facing terminal output — even if the user doesn't mention "logging" or "UX" explicitly.
Write technical reports — experiment reports, system design documents, code documentation, and internal research memos. Use when documenting technical work that doesn't fit paper format.
Use when babysitting a PR/MR until CI is green and every valid reviewer feedback is addressed — supports GitHub PR (gh) and GitLab MR (glab), triages comments into Valid / Discuss / Out-of-scope, addresses valid items with small commits and inline thread replies, escalates invisible findings (SonarQube/Snyk dashboards) and 3-round bot deadlocks, reports ready-to-merge (never auto-merges). Triggers — '監看 PR', 'babysit PR/MR', 'PR 顧到 merge', 'address review feedback', 'wait until CI green', '把 PR 顧到綠'. NOT for writing PR descriptions, NOT for diff code review (use pr-review), NOT for actually merging the PR (user does that).
Audit a live page for accessibility issues and locate each violation precisely — optionally pass a URL (e.g. `accesslint:scan https://example.com/dashboard`), otherwise ask for one. Ensures a debuggable Chrome, runs the @accesslint/core engine via CDP, and returns a worklist of live-DOM WCAG violations grounded to each violation's DOM selector and source file:line. Locates; doesn't edit — output drives fixes by Claude. Use it for "is this page accessible", or to verify a UI change. For diffing against uncommitted changes or a branch, use the `diff` skill.