Loading...
Loading...
Found 9,272 Skills
April Dunford's 10-step positioning methodology for B2B tech products. Use when customers don't understand the product, sales cycles are long because reps must "explain it," prospects compare you to wrong competitors, or you face price pressure despite a good product. Covers competitive alternatives, unique attributes, value themes, target market characteristics, market category (Head to Head / Big Fish Small Pond / New Game), and trend layering.
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.
Use this skill when the user wants to do something on X with xurl, especially when they talk in task language like send a tweet, create an X post, reply to a post, send a DM, search posts, upload media, check mentions, or switch between X app accounts. Also use it for xurl sign-in and app setup problems such as OAuth, redirect URI, who-am-I checks, or managing multiple xurl apps. Prioritize user goals over technical wording: trigger even if the user never says CLI, command line, terminal, or script. Do not use it for general X API development in Python, Node.js, raw curl, mobile apps, or generic OAuth theory.
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow execution, poor readability. Triggers when: user asks about test quality, shares test files for review, or expresses frustration: "tests keep breaking whenever I change anything", "our tests take forever", "I can't understand what this test is doing", "tests pass but bugs still reach production", "we have too many mocks". Do NOT trigger for: writing new tests from scratch (use the regular test-writing workflow) or testing framework/syntax questions — this skill reviews an existing suite for structural quality problems, not individual test authoring.
Develop Xiaohongshu note ideas and drafts from rough thoughts, lived experience, or existing source material. Use this when the user has a scattered idea, a half-formed opinion, a working draft, or a professional insight and wants help shaping it into a Xiaohongshu note with stronger structure, trust, readability, and platform spread potential. This skill is especially for professional, experience-dense, memo-style notes that should feel like a real operator sharing judgments, not a generic content writer producing polished fluff.
Extract useful frames from local video files based on task intent, such as persona research, shot breakdown, product visibility, UI walkthroughs, visual-style review, or CTA/compliance checks. Use this when the goal is not generic video analysis, but selecting the right still frames and contact sheets for a specific downstream need.
Prepare for investor calls by pulling upcoming meetings from Google Calendar, deeply researching each investor and their firm (website scraping, portfolio analysis, thesis extraction), checking for competitor conflicts, and outputting an honest prep sheet with compatibility assessments. Use when asked to prep for investor meetings, fundraising calls, VC meetings, or demo day.
Comprehensive paid media auditor who systematically evaluates Google Ads, Microsoft Ads, and Meta accounts across 200+ checkpoints spanning account structure, tracking, bidding, creative, audiences, and competitive positioning. Produces actionable audit reports with prioritized recommendations and projected impact.
Use this skill when the user asks to "check data usage", "list TCO policies", "view quotas", "reduce Coralogix costs", "optimize observability spend", "lower our logging bill", "data budget exceeded", "TCO policy", "retention tier", "archive storage", "ingestion costs", "frequent search vs archive", "why is our bill so high", "spending too much on logs", "data retention settings", "quota rules", "cost analysis", "usage breakdown", "optimize log volume", "control data ingestion", "archive cold data", "billing units", "plan consumption", "daily plan", "overage", "PAYG", "usage anomaly", "usage trend", "cx_data_usage_units", or wants to investigate, analyze, or reduce Coralogix data costs.
Turn an article or script into a click-driven 16:9 web presentation that "looks like a video", with optional voiceover audio synthesis. Workflow: Original Article → **One-time Output** Script + Outline Development Plan → User **One-time Alignment** on 5 Items (Script / Outline / Theme / Assets / Development Mode) → Web Development (Chapter-by-Chapter / Sequential / Parallel) → Optional Audio Synthesis (Default: MiniMax CLI mmx-cli). **Outline only plans rhythm and information density, not animations** — Animations are designed on the fly during chapter development following the PRINCIPLES + ANTI-AI rules. Each click advances one beat of the script, each step occupies the full screen, and the progress bar is hidden by default only appearing on hover. Application Scenarios: Use web pages to make videos (dynamic PPT but not like PPT), turn scripts/articles into interactive explanations, create screen recording tutorials for Bilibili / YouTube / Video Channels, make cinematic product/talk demos. This Skill embodies design methodology + collaboration process — it is not bound to any specific styles/fonts/colors — so it can be reused for any theme and aesthetic.
Run a retrospective after generating a CLI. Identifies systemic improvements to the Printing Press — templates, Go binary, skill instructions, catalog — so the next CLI comes out better. Creates a GitHub issue with actionable findings when there are Printing Press fixes to make. Use after any /printing-press run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings".
Core technical-indicator signal engine for stocks listed in HK / US / A-share / Singapore via Longbridge Securities. Computes and interprets MACD, KDJ, RSI, Bollinger Bands, EMA, ADX, and OBV from OHLCV data; combines multi-dimensional votes (trend / mean-reversion / volume-price) to produce a composite buy / sell / neutral signal. Triggers: "技术指标", "MACD", "KDJ", "RSI", "布林带", "布林线", "EMA", "ADX", "OBV", "金叉", "死叉", "超买", "超卖", "技术分析", "趋势指标", "量价", "技術指標", "布林帶", "技術分析", "超買", "超賣", "technical indicator", "MACD signal", "KDJ overbought", "RSI oversold", "Bollinger Bands", "moving average", "golden cross", "death cross", "technical analysis".