Loading...
Loading...
Found 2,103 Skills
High-dividend stock screen via Longbridge — analyse high-dividend-yield strategies for A-shares / HK / US, filter for sustainable payout (reasonable payout ratio, free-cash-flow coverage), stable dividend history, and evaluate long-term total return potential. Triggers: "高分红", "股息率", "红利股", "高股息", "分红稳定", "现金分红", "股息策略", "红利策略", "高分紅", "股息率", "紅利股", "高股息", "分紅穩定", "現金分紅", "high dividend", "dividend yield", "dividend stock", "income stock", "dividend strategy", "payout ratio", "free cash flow coverage", "dividend growth", "dividend stability".
Brev managed GPU instances with Docker support. Use when running TAO training, evaluation, or inference on Brev GPU instances, managing Brev deployments, or dispatching TAO jobs through the Brev CLI. Trigger phrases include "run on Brev", "Brev GPU instance", "submit job to Brev", "Brev CLI deployment".
Audit a GitHub repository's security posture and hardening gaps across branch protection, CODEOWNERS, GitHub Actions, publish/release integrity, collaborator access, security features, and dependency review. Use when reviewing or hardening a repo, assessing GitHub configuration, checking CI/CD or Actions security, evaluating supply-chain posture, preparing maintainer-facing security todos, or when the user says "repo security posture", "audit my repo", "harden this GitHub repo", "actions security", "protect against a compromised maintainer", or points at a GitHub URL and asks what to fix.
Comprehensive technical research by combining multiple intelligence sources — Grok (X/Twitter developer discussions via Playwright), DeepWiki (AI-powered GitHub repository analysis), and WebSearch. Dispatches parallel subagents for each source and synthesizes findings into a unified report. This skill should be used when evaluating technologies, comparing libraries/frameworks, researching GitHub repos, gauging developer sentiment, or investigating technical architecture decisions. Trigger phrases include "tech research", "research this technology", "技术调研", "调研一下", "compare libraries", "evaluate framework", "investigate repo".
Discover and evaluate Laravel packages via LaraPlugins.io MCP. Use when the user wants to find plugins, check package health, or assess Laravel/PHP compatibility.
Analyze previous Jetty workflow runs and propose targeted improvements to your runbook. Use when the user wants to optimize, improve, or debug a runbook based on past execution results — including 'optimize runbook', 'improve runbook', 'why is my runbook failing', 'analyze my runs', 'runbook not working well', 'make my runbook better', 'debug runbook performance', or 'learn from past runs'. Also trigger when the user mentions trajectory analysis, run patterns, or evaluation score improvements.
HyNote AI platform help — full-stack AI note-taker that captures audio, meetings, PDFs, images, YouTube videos, and web pages into structured notes with flashcards, quizzes, mind maps, and presentation generation. Use when setting up HyNote for recording meetings or lectures and generating structured notes, troubleshooting transcription accuracy or speaker identification issues, figuring out which HyNote plan includes real-time transcription and Notion export, comparing HyNote to Otter or Granola or Coconote for AI note-taking, evaluating HyNote for multilingual transcription across web and mobile, understanding why exported notes don't include transcripts on the free plan, or deciding whether HyNote Teams is worth the per-seat cost. Do NOT use for comparing AI meeting note-takers for sales teams (use /sales-note-taker) or reviewing a sales call for coaching (use /sales-call-review).
Influence and negotiation toolkit for any interaction requiring another person's agreement, even when not framed as 'negotiation'. Covers: B2B sales, salary review, collective bargaining/unions, hard 1:1s, decision announcements, mediation, cross-cultural deals, recruitment, reaching out to a manager, CFO, customer, vendor, or colleague, responding to feedback, headcount requests, declining, pushing back on scope, justifying a delay, explaining a decision, raising a concern, getting alignment. Apply when preparing, live, or drafting any diplomatic message. Triggers: coaching prompts ('they just said X', 'what do I say', 'draft a reply'); counterparty cues (buyer, customer, champion, procurement, RFP, sponsor, HR, union, CHRO, ExCo, candidate, counter-offer, partner, peer); situation cues (pushback, refusal, ghosted, no-decision, escalation, fixed budget, MFN, raise, comp band, strike, layoff, recadrage, expectation reset, M&A, BATNA, objection, concession, anchor, mirroring).
Analyze story plot points, identify key plots and turning points. Suitable for in-depth analysis of plot structure and evaluation of plot development effectiveness
Research on Historical Isomorphism and Standard Answers. Abstract the complex dilemma the user is facing into a structural fingerprint, search for truly isomorphic successful cases, failed cases, and counterexamples in business history, management history, technology history, career history, and institutional history. Compare the constraints, decisions, and outcomes of the parties involved, and extract recurring solutions, applicable conditions, and failure boundaries. Trigger methods: /dbs-standard-answer, /标准答案 (Standard Answer), "Who faced similar problems in history?", "Has anyone encountered this situation before?", "How did they resolve it back then?", "Is there a classic solution to this problem?", "First help me find historical analogies?", "What was the standard answer in the past?". Find structurally analogous historical cases and evidence-backed standard answers. Use when the user wants to situate a current dilemma in history, compare how others addressed it, and extract recurring mechanisms with conditions and limits.
Help users navigate career changes and pivots. Use when someone is considering a new role, transitioning into product management, evaluating job offers, taking a sabbatical, or feeling stuck in their current position.
Draft professional, empathetic customer-facing responses adapted to the situation, urgency, and channel. Use when responding to customer tickets, escalations, outage notifications, bug reports, feature requests, or any customer-facing communication.