Loading...
Loading...
Found 919 Skills
Create a PR title and draft description after substantive code changes are finished. Trigger when wrapping up a moderate-or-larger change (runtime code, tests, build config, docs with behavior impact) and you need the PR-ready summary block with change summary plus PR draft text.
Cross-cutting project status dashboard. Shows active epics with progress ratios, actionable next steps, blocked items, in-progress tasks, GitHub issues, and session context. Produces rich terminal output with clickable links. Triggers on: 'project status', 'swain status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'am I blocked', 'what needs review', 'show me priorities'.
Use when you need to refactor Java code to adopt modern Java features (Java 8+) — including migrating anonymous classes to lambdas, replacing Iterator loops with Stream API, adopting Optional for null safety, switching from legacy Date/Calendar to java.time, using collection factory methods, applying text blocks, var inference, or leveraging Java 25 features like flexible constructor bodies and module import declarations. Part of the skills-for-java project
When the user wants to create, optimize, or audit a HowTo section block—an in-page block of ordered steps with optional Schema.org HowTo JSON-LD. Also use when the user mentions "HowTo section," "how-to section," "steps section," "quick start," "walkthrough," "tutorial block," "3 steps," "N steps," "simple steps," "tutorial steps," "step-by-step block," "HowTo schema," "HowTo JSON-LD," "instruction steps," "numbered steps SEO," "horizontal tabs for steps," or "procedure section." This skill is for a section inside a page, not a full page template—use article-page-generator, docs-page-generator, or tools-page-generator for page-level layout. For FAQ Q&A blocks, use faq-page-generator. For structured data details beyond HowTo, use schema-markup. For article body copy only, use article-content.
Rust async internals skill for understanding and debugging async Rust. Use when understanding the Future trait and poll model, Pin and Unpin, tokio task scheduling, debugging async stack traces with tokio-console, tracking waker leaks, using select! and join!, or avoiding blocking in async contexts. Activates on queries about Rust async internals, Future poll, Pin, Unpin, tokio-console, waker, async stack traces, select!, join!, or blocking in async.
Solve CAPTCHAs in automated browser sessions using third-party solving services. Use this skill whenever you need to: bypass a CAPTCHA while automating a website, integrate CAPTCHA solving into a Playwright or Puppeteer script, solve reCAPTCHA v2 or v3, hCaptcha, Cloudflare Turnstile, or image-based CAPTCHAs, automate a login or form submission that's blocked by a CAPTCHA, test a page that has CAPTCHA challenges, or write a script that needs to pass a CAPTCHA programmatically. Also triggers for: "recaptcha", "hcaptcha", "turnstile", "captcha solving", "bypass captcha", "solve captcha", "pass captcha challenge", "automate past captcha", "get past robot check", "bot verification". Always use this skill for any CAPTCHA-related automation — even simple cases benefit from correct token injection patterns.
Behavior Guidelines for Information Visualization Presentation. Automatically activated when the model's response contains structured information such as comparisons, steps, configurations, architectures, etc., ensuring priority use of visual formats like tables, code blocks, lists, tree structures, instead of pure text accumulation. Trigger words: "Use a table", "Draw a diagram", "Make a list", "Structure it", "Don't just use text", "Visualize", "Compare". Even without trigger words, the rules of this Skill should take effect as long as the response contains structured information suitable for visualization. It also applies to scenarios such as "Too much text to read", "Can it be more intuitive?", "Organize into a table".
Automated, project-wide code coverage and CRAP (Change Risk Anti-Patterns) score analysis for .NET projects with existing unit tests. Auto-detects solution structure, runs coverage collection via `dotnet test` (supports both Microsoft.Testing.Extensions.CodeCoverage and Coverlet), generates reports via ReportGenerator, calculates CRAP scores per method, and surfaces risk hotspots — complex code with low test coverage that is dangerous to modify. Use when the user wants project-wide coverage analysis with risk prioritization, coverage gap identification, CRAP score computation across an entire solution, or to diagnose why coverage is stuck or plateaued and identify what methods are blocking improvement. DO NOT USE FOR: targeted single-method CRAP analysis (use crap-score skill), writing tests, running tests without coverage collection, applying test filters, producing TRX reports, or troubleshooting test execution (use run-tests for all of these).
Help a PhD student intentionally choose which cognitive mode to enter right now (deep production, wide reading, or collaborative engagement) and plan their day around these modes to minimize context-switching costs. Use this skill whenever the user is at the start of a day or work block and unsure what to focus on, feels scattered across too many activities, asks "what should I do right now", wants to plan their day, or feels frustrated by constant context-switching. Trigger on phrases like "plan my day", "what should I work on now", "I feel scattered", "context switching", "deep work", "can't focus", "I have X hours", or whenever the user is trying to decide between substantively different kinds of work (writing vs reading vs meetings).
Modular grid layout with card-like blocks, clear hierarchy, soft spacing, and subtle visual contrast for organized, scannable interfaces.
Use when writing, fixing, or editing TypeScript error handling, catch blocks, thrown values, null failures, swallowed errors, retries, fallbacks, or Result-style APIs.
Buffett-style single-stock moat diagnostic — "Would Buffett buy this stock?" Five dimensions: business & moat / financial health / management & capital allocation / valuation & margin of safety / long-term visibility. Data from Longbridge CLI first, MCP fallback, WebSearch only for gaps. Runs cross-statement reconciliation (勾稽校验) BEFORE scoring; data-source appendix closes with a one-line reconciliation summary. Output: star-rated radar card, dimension detail, Buffett-voice narrative, mandatory holding-period education block. Triggers: "巴菲特", "护城河", "巴菲特会买吗", "价值投资", "好生意", "宽护城河", "定价权", "诊股", "巴菲特诊股", "巴菲特视角", "长期持有", "護城河", "巴菲特會買嗎", "價值投資", "寬護城河", "定價權", "診股", "巴菲特診股", "巴菲特視角", "長期持有", "Buffett", "Warren Buffett", "moat", "economic moat", "wide moat", "pricing power", "value investing", "owner earnings", "would Buffett buy", "Berkshire-style", "quality compounder".