Loading...
Loading...
Found 4,073 Skills
Systematic pre-publication manuscript audit producing a structured refactoring report with section-level diagnostics, citation hygiene analysis, and submission-readiness assessment. Use this skill whenever the user uploads a manuscript, paper, thesis chapter, journal submission, or conference paper and asks for review, feedback, editing, refactoring, pre-submission check, proofreading, or quality audit. Also trigger when the user says "review my paper", "check before submission", "is this ready to submit", "pre-pub checklist", "manuscript review", "refactor my paper", or asks about citation consistency, argument coherence, or formatting compliance. Covers partial requests like "check my references" or "does the abstract work" — the full diagnostic surfaces issues across all facets even when only one was asked about.
DDEV local development environment for Craft CMS projects. Covers config.yaml settings (project type, PHP/Node versions, database, docroot), shorthand commands (ddev composer, ddev craft, ddev npm), add-ons (Redis, Mailpit), custom commands (.ddev/commands/), Vite dev server exposure (web_extra_exposed_ports, web_extra_daemons), database import/export, Xdebug toggling, and troubleshooting. Triggers on: ddev start, ddev craft, ddev composer, ddev ssh, ddev import-db, ddev xdebug, .ddev/config.yaml, web_extra_exposed_ports, web_extra_daemons, ddev add-on, ddev poweroff, ddev describe. Use when running DDEV commands, configuring local environments, or troubleshooting container issues.
Compares a single test case's behavior across two branches, analyzing pass/fail status, duration, flakiness, and failure details. Useful for investigating test regressions introduced by a feature branch.
Apply when defining or changing the contract of a VTEX IO app through manifest.json, builder declarations, dependencies, peerDependencies, billingOptions, and app identity. Covers how the app declares capabilities and integration boundaries. Use for scaffolding apps, splitting responsibilities across apps, or fixing contract-level link and publish issues.
📡 Pulse — Twice-daily tech briefing for group distribution. Designed to be triggered by cronjob at morning and evening, or manually. Use this skill only when the user says "pulse" or "/pulse".
Reference data for test filter syntax across all platform and framework combinations: VSTest --filter expressions, MTP filters for MSTest/NUnit/xUnit v3/TUnit, and VSTest-to-MTP filter translation. DO NOT USE directly — loaded by run-tests, mtp-hot-reload, and migrate-vstest-to-mtp when they need filter syntax.
C++ library for reducing tail latency in RAM reads by hedging across multiple DRAM channels with uncorrelated refresh schedules
Orchestrate the complete advisor workflow for assembling and delivering a comprehensive financial plan, from data gathering through recommendations and ongoing monitoring. Use when the user asks about building a financial plan for a client, structuring a planning engagement, coordinating retirement and education and estate goals into one plan, running scenario analysis across a full financial picture, prioritizing competing recommendations, preparing for a plan presentation meeting, or deciding when a plan needs updating. Also trigger when users mention 'comprehensive financial plan', 'discovery meeting', 'cash flow analysis', 'retirement modeling', 'education funding gap', 'plan delivery', 'savings rate', 'plan update trigger', or 'is my client on track'.
Deep Research Skill for Horizontal-Vertical Analysis. Proposed by digital life Khazix, it integrates core ideas from Saussure's diachronic-synchronic analysis, longitudinal-cross-sectional research design in social sciences, business school case study methods, and competitive strategy analysis. It is used when users want to systematically research a product, company, concept, technology, or person. The core is dual-axis analysis: the vertical axis tracks the complete life cycle from birth to the present (presented as a narrative story), while the horizontal axis conducts a systematic horizontal comparison with competitors/peers at the current time point. Finally, unique insights are generated by intersecting the two axes, and a beautifully formatted PDF research report is produced as the final output. Trigger words include but are not limited to: horizontal-vertical analysis, research for me, help me analyze, in-depth research, conduct a research, investigate, competitor analysis, help me understand how this thing is, what's this product/company/concept about, help me figure it out, help me understand it, do a deep research for me. Even if the user only says "help me understand XX" or "what's the background of XX", it should be triggered as long as the context implies a need for systematic in-depth research (rather than a simple conceptual explanation). It also applies to scenarios where the user sends a product name, company name, or technical term and says "help me research this". Do not use it for simple noun explanations (when the user only asks "what is XX"), do not use it for official account writing (use khazix-writer for that), and do not use it for pure title abstract generation (use wechat-title for that).
Manage time-bounded company announcements in Glean. Use when creating, updating, or deleting announcements that surface across the Glean UI.
Manage crisis communication across prevention, response, and recovery phases using SCCT theory and crisis statement frameworks. Use this skill when the user faces a PR crisis, needs to draft a crisis response, plan crisis preparedness, or manage negative public attention — even if they say 'we're getting bad press', 'how do we respond to this scandal', 'draft a public statement', or 'prepare for potential backlash'.
Apply systems thinking — causal loop diagrams, stock-and-flow models, system archetypes, and leverage-point analysis — to organizational, economic, or social problems where feedback loops, delays, or emergent behavior drive recurring failure across multiple interacting actors. Use this skill when the user describes a multi-actor situation that resists linear fixes: policy interventions that backfire, org-level fixes that break other teams, market symptoms that return after being solved, or time-lagged second-order consequences, even if they say 'why does fixing X make Y worse' or 'identify the leverage points in this system'. Do NOT use for single-cause software bugs, flaky tests, or regressions — those are debugging problems, not systems-thinking problems, even when phrased as 'this keeps coming back'.