10,192 skills found ¡ Page 339 of 340
daluoter / openspec-proposeMalicious File Analysis System
Hanzala-plyance / openspec-ff-changeShared Backstage feature specifications and agent constitutions powered by OpenSpec.
vigneshsinna / openai-skills--soraUse when the user asks to generate, remix, poll, list, download, or delete Sora videos via OpenAI\u2019s video API using the bundled CLI (`scripts/sora.py`), including requests like \u201cgenerate AI video,\u201d \u201cSora,\u201d \u201cvideo remix,\u201d \u201cdownload video/thumbnail/spritesheet,\âĻ
dabit3 / lightningFull stack framework for building cross-platform mobile AI apps
Noizefield / apc-newComplete APC plugin development from idea to shipped product â full workflow orchestration. Trigger with /apc-new <Name>.
Noizefield / apc-hubOpen the APC Hub live dashboard (read-only command center). Trigger with /apc-hub.
Noizefield / apc-shipPHASE 5 â Packaging. Create cross-platform installers and distribution packages for a validated APC plugin. Trigger with /apc-ship <Name>.
Noizefield / apc-debugAutonomous debugging and fault isolation for an APC plugin â crash analysis, known-issues lookup, fix loop. Trigger with /apc-debug <Name>.
Zeruel87 / boot-gateBoot-gate the game before committing: launch, verify menu, check for exceptions
OutlineDriven / mesonUse when setting up a Meson project, meson setup/compile/test, wrap dependencies, cross-file cross-compiling, meson.build, or migrating from CMake/Autotools to Meson.
OutlineDriven / bazelUse when writing Bazel BUILD files with cc_library or cc_binary rules, Bzlmod dependencies, toolchain registration, remote execution, sandbox debugging, or bazel query and cquery graphs.
OutlineDriven / ebpfUse when writing eBPF programs with libbpf, bpftrace, or Rust with aya-ebpf and aya-log, attaching kprobes, tracepoints, or XDP hooks, declaring maps, sharing data with a Tokio loader, triaging verifier or Aya load errors, or porting with CO-RE. Not for full kernel bypass: use dpdk.
OutlineDriven / cmakeUse when writing CMakeLists.txt, out-of-source builds, target_link_libraries, target properties, find_package/FetchContent, toolchain files, CPack, CMake presets, or cmake configure errors.
OutlineDriven / fuzzingUse when planning an end-to-end fuzzing program for a project: engine and target selection, corpus management, and CI or nightly wiring. Not for harness design: use fuzz-harness-writing. Not for engine operation or triage: use libfuzzer. Not for sanitizer flag reference: use sanitizers.
OutlineDriven / hip-rocmUse when writing HIP kernels with hipcc, porting CUDA code through HIPIFY, profiling with rocprofv3, debugging with rocgdb, or optimizing for MI300X. Not for NVIDIA-side kernels: use cuda.
OutlineDriven / makeUse when writing or debugging Makefiles, understanding pattern rules and automatic dependency generation, managing CFLAGS/LDFLAGS, or diagnosing incremental build, phony targets, or recursive make.
OutlineDriven / cudaUse when writing CUDA kernels, managing the thread, block, and grid hierarchy, tiling shared memory, using streams, setting nvcc flags, or using Thrust. Not for kernel debugging: use cuda-debugging.
OutlineDriven / tasteUse when asking "overkill?", "elegant?", "audit", or "taste-test this", or setting a taste register. Not for tasks that require source or remote-system changes.
OutlineDriven / ninjaUse when diagnosing Ninja build failures, tuning parallelism, interpreting verbose output, or working with build.ninja files as a CMake-generated low-level build executor.
OutlineDriven / deslopUse when the user says deslop, debloat, tidy, simplify, clean a diff, cleanup codebase, or deslop branch diff, or remove dead code or config. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven / commitUse when asked to commit changes, create a typed branch, format history for a changelog, or rewrite messages of HEAD or an unpushed range. Not for pushing or a PR: use commit-push-pr.
OutlineDriven / principlesUse when a request names a working principle (subtract before you add, idempotent operations, never block on the human) or asks which principle applies. Not for running a repair: use strike-the-root.
OutlineDriven / workUse when implementing from a plan, spec, clear build request, or settled ticket, orchestrated or standalone. Don''t use for open-ended debugging (figure-it-out), exploration, or read-only research.
OutlineDriven / sagaUse when a user runs saga or asks to autonomously build a sizable feature. Not for executing a given plan: use subagent-driven.
OutlineDriven / reviewUse when asked to review a pull request, examine code changes, find bugs, or audit a branch, in standard or depth mode. Not for an iterative review-and-fix loop: use audit-project.
OutlineDriven / unslopUse when prose is drafted or edited, reviewed for AI tells, or the user asks to remove AI patterns, humanize, or add voice. Offers dedash and detool modes. Not for code debris: use deslop.
OutlineDriven / to-specUse when settled conversation decisions need synthesis into an agent-ready implementation spec, stopping before publication. Not for turning plans into tickets: use to-tickets.
OutlineDriven / vulnerability-triage-brocardsUse when a vulnerability report, CVE, bug-bounty submission, or automated finding needs triage before deep verification. Don''t use for tasks that require source or remote-system changes.
OutlineDriven / resolveUse when addressing review feedback in analyze or reception mode, or handling GitHub PR feedback in autonomous, interactive, or summary mode for a named PR target. Classifies, applies, replies, or summarizes comments.
OutlineDriven / tddUse when developing a fix or feature test-first, plan a TDD build, or work red-to-green in slices. Not for hardening: use tests-adversarial. Not for deleting weak tests: use tests-purge-unneeded.
