Loading...
Loading...
Found 1,518 Skills
Single entry skill for open-websearch setup and focused live retrieval, preferring local CLI/daemon paths while remaining compatible with workspace-exposed MCP tools.
Use this skill whenever the user wants to work with survey data using the `survy` Python library. Triggers include: loading or reading survey CSV/Excel/JSON/SPSS files, handling multiselect (multi-choice) questions, computing frequency tables or crosstabs, exporting survey data to SPSS (.sav) or other formats, updating variable labels or value indices, transforming survey data between wide/compact formats, filtering respondents, replacing values, adding/dropping/sorting variables, or any task involving survy's API (read_csv, read_excel, read_json, read_polars, read_spss, crosstab, survey["Q1"], to_spss, to_csv, to_excel, to_json, etc.). Also trigger when the user says things like "analyze my survey", "process questionnaire data", "build a survey analysis script", or "help me with survy". Always read this skill before writing any survy code — it contains the correct API, patterns, and gotchas.
Use when handling Moodle CLI tasks: login, list courses/files, lecture timetable lookups, printing file contents, and course download/export operations.
Import code that has been exported by another module using static ES2015 import syntax.
Unified macro intelligence feed — reads 7 sources, classifies events, scores sentiment, generates AI insights, exposes signals via HTTP API
Wrapper for the Dify workflow DSL CLI. Create, inspect, validate, edit, and export Dify workflow files through a CLI-Anything harness.
CLI harness for Krita digital painting — manage projects, layers, filters, and export via command line. Use when automating Krita workflows, batch processing images, or operating Krita without a GUI.
cuTile Python DSL kernel implementation patterns, CtKernel runtime wrapper, suitability gate, and cuTile-specific pitfalls. Use when: (1) creating or modifying a cuTile Python DSL kernel version, (2) implementing an optimization that still fits within cuTile's exposed control surface, (3) deciding whether cuTile is still the right DSL, (4) reviewing cuTile-specific runtime patterns. Always also load /design-kernel for shared naming, versioning, and workflow.
CuTe Python DSL kernel workflow, CuteKernel runtime wrapper, suitability gate, tiling guidance, and CuTe-specific pitfalls. Use when: (1) planning or implementing a kernel in the CuTe Python DSL, (2) the optimization needs more explicit control than cuTile exposes but should remain in a Python-driven workflow, (3) defining package naming for cute-dsl kernels, (4) documenting CuTe Python DSL design choices, (5) recording language-specific knowledge for CuTe Python DSL.
Use when the user wants to initialize, switch, inspect, optimize, export, or diagnose a role bundle with /roleMe.
Guides application developers in designing correct and performant transaction patterns for CockroachDB, covering transaction lifetime, implicit vs explicit transactions, retry handling with exponential backoff, pushing invariants into SQL, selective pessimistic locking, set-based operations, connection pooling, prepared statements, keyset pagination, follower reads, and separating business logic from database logic. Use when building applications on CockroachDB, designing transaction workflows, handling retries, optimizing application-layer database interactions, or configuring connection pools.
Audit the game for security vulnerabilities: save tampering, cheat vectors, network exploits, data exposure, and input validation gaps. Produces a prioritised security report with remediation guidance. Run before any public release or multiplayer launch.