malskill

In the author's own words, from each skill's SKILL.md — showing the first 30 of 336 files.

• codemachine-template

  Create, validate, and structure CodeMachine AI orchestrator workflow packages. Use when the user asks to build a CodeMachine workflow, write a .workflow.js file, define agents for CodeMachine, scaffold a codemachine package, or create multi-agent pipelines with CodeMachine CLI. Also triggers for: codemachine template, codemachine workflow design, main.agents.js, sub.agents.js, modules.js, resolve…

  ai/codemachine-template/SKILL.md on GitHub (opens in a new tab)

• keras

  Keras model loading and structure-inspection workflow for `.keras`, SavedModel, and HDF5 artifacts. Use when you need to inspect layers, summaries, configs, weights, or quick inference behavior from TensorFlow/Keras model files.

  ai/keras/SKILL.md on GitHub (opens in a new tab)

• langchain-py

  Build and maintain production-grade LangChain Python systems (LangChain 1.3.x / LangGraph 1.2.x baseline) with create_agent, middleware, tools, structured output, and multi-agent architectures (subagents, handoffs, router, skills). Activate for Python agent design, debugging, migrations from older APIs, context engineering, and Tavily-backed web search integration.

  ai/langchain-py/SKILL.md on GitHub (opens in a new tab)

• pytorch

  PyTorch model inspection and checkpoint workflow for loading tensors, `state_dict` data, modules, and parameters. Use when working with `.pt` or `.pth` artifacts, auditing model structure, extracting weights, or scripting inference-oriented inspection of deep-learning checkpoints.

  ai/pytorch/SKILL.md on GitHub (opens in a new tab)

• scikit-learn

  scikit-learn model inspection workflow for loading persisted estimators, pipelines, and tree models. Use when you need to inspect `joblib` or pickle-based model artifacts, view parameters, feature names, importances, or pipeline structure, or run lightweight predictions for analysis.

  ai/scikit-learn/SKILL.md on GitHub (opens in a new tab)

• vec2text

  vec2text: embedding-inversion library for reconstructing approximate text from sentence embeddings. Use when working with saved embedding tensors, privacy/inversion research, or AI/ML challenge workflows where you need to load a corrector model and invert strings or embeddings directly.

  ai/vec2text/SKILL.md on GitHub (opens in a new tab)

• 1337-brain

  Maintain and query an Obsidian knowledge vault. Use /1337-brain for source ingestion, linked notes, project indexes, grounded answers, deduplication, or vault audits.

  behaviours/1337-brain/SKILL.md on GitHub (opens in a new tab)

• 1337

  Structured operator behavior for coding and authorized security work: explicit reasoning, evidence, verification, and concise execution. Use when the user requests /1337 or execution-first structured analysis.

  behaviours/1337/SKILL.md on GitHub (opens in a new tab)

• agentic-offensive-orchestration

  Design and review authorized multi-agent security workflows: delegation topologies, deterministic worker contracts, agentic trust boundaries, and worker-compromise containment.

  behaviours/agentic-offensive-orchestration/SKILL.md on GitHub (opens in a new tab)

• design-before-implementation

  Resolve design uncertainty before a substantial change. Use when requirements, interfaces, alternatives, or success criteria are unclear; skip a separate design phase for an already specified local fix.

  behaviours/design-before-implementation/SKILL.md on GitHub (opens in a new tab)

• evidence-before-claims

  Evidence gate for security research, scanner triage, code review, and reporting. Use before confirming vulnerability impact, auth material, control results, cleanup, or root cause.

  behaviours/evidence-before-claims/SKILL.md on GitHub (opens in a new tab)

• hypothesis-driven

  Investigate an uncertain cause using testable hypotheses and discriminating evidence. Use for persistent bugs, flaky behavior, incident diagnosis, or conflicting research observations; skip routine edits with a known solution.

  behaviours/hypothesis-driven/SKILL.md on GitHub (opens in a new tab)

• implementation-planning

  Turn settled requirements into an executable plan. Use for work with dependencies, shared-file ownership, or a handoff; skip a separate plan for a straightforward local edit.

  behaviours/implementation-planning/SKILL.md on GitHub (opens in a new tab)

• loop-control-and-pivots

  Stop unproductive retries and repeated polling. Use when the same failure recurs, a side issue consumes the task, or unfinished jobs are checked without new evidence.

  behaviours/loop-control-and-pivots/SKILL.md on GitHub (opens in a new tab)

• memory-hygiene

  Read, update, or design persistent agent memory. Use when deciding what may be stored, retrieving prior decisions, or resolving stale, conflicting, or incorrectly scoped notes.

  behaviours/memory-hygiene/SKILL.md on GitHub (opens in a new tab)

• reading-budget-discipline

  Limit context consumption when inspecting large files, tool output, logs, or collections of artifacts. Use when a targeted search or bounded extraction can answer the question without loading everything.

  behaviours/reading-budget-discipline/SKILL.md on GitHub (opens in a new tab)

• untrusted-input-hygiene

  Handle retrieved content and artifacts without promoting them into instructions. Use for prompt-injection review, external files/pages, tool results, memory retrieval, and worker reports.

  behaviours/untrusted-input-hygiene/SKILL.md on GitHub (opens in a new tab)

• verification-before-completion

  Check evidence before reporting work complete, fixed, passing, or ready. Use at a completion boundary or when later changes may have invalidated an earlier result.

  behaviours/verification-before-completion/SKILL.md on GitHub (opens in a new tab)

• android-jni-ndk

  Kotlin/Java ↔ native (C/C++/Rust) bridging on Android: NDK setup, JNI mechanics, `System.loadLibrary`, `RegisterNatives`, `@FastNative`/`@CriticalNative`, reference hygiene, exception propagation, 16 KB page-size compliance, native crash triage. Use when building or debugging a native module, embedding a `.so` library, decoding a native ANR or SIGSEGV, or reverse-engineering an APK's native code…

  coding/android-jni-ndk/SKILL.md on GitHub (opens in a new tab)

• android-testing

  Android testing patterns for unit tests, instrumented tests, Compose UI tests, screenshot tests, and end-to-end journeys. Use when setting up JUnit4/JUnit5 + Robolectric, wiring Hilt/Koin for tests, choosing between Espresso and Compose Test APIs, adding Roborazzi/Paparazzi/Dropshots screenshot tests, or diagnosing flaky Android tests.

  coding/android-testing/SKILL.md on GitHub (opens in a new tab)

• asm-patterns

  Assembly language patterns, calling conventions, and code structure for x86-64 and ARM64. Use when writing, reviewing, or generating .asm/.s/.S files; when implementing functions that interoperate with C/system code; or when establishing correct prologues, epilogues, stack management, SIMD loops, syscall stubs, or PIC data access.

  coding/asm-patterns/SKILL.md on GitHub (opens in a new tab)

• asm-performance

  Assembly performance optimization workflow: collect compiler-emitted ASM, classify bottlenecks with TMA, audit for codegen issues (bounds checks, register spills, dependency chains, missed vectorization, memory traffic, bad instruction selection, store-forwarding stalls, frontend pressure, data layout), apply one change at a time, measure, and report. Use after profiling confirms ASM is the bottl…

  coding/asm-performance/SKILL.md on GitHub (opens in a new tab)

• asm-testing

  Assembly code testing, debugging, and bug-hunting workflow for hand-written and injected assembly: C/Go harness testing, GDB/LLDB/WinDbg/x64dbg verification, objdump structural analysis, Python helpers (Capstone/Unicorn/Keystone), Frida dynamic instrumentation, offensive ASM debugging (trampolines, callgates, syscall stubs, stack spoofing, PIC shellcode), reverse engineering own binaries, and com…

  coding/asm-testing/SKILL.md on GitHub (opens in a new tab)

• c-patterns

  C language patterns and best practices for safe, maintainable C: ownership, API contracts, error handling, integer safety, portability, and concurrency boundaries. Use when writing or reviewing C code (C11+), designing module interfaces, refactoring legacy C, or hardening low-level code paths.

  coding/c-patterns/SKILL.md on GitHub (opens in a new tab)

• c-testing

  C testing workflow for unit and integration tests: deterministic harnesses, CMake/CTest execution strategy, sanitizer-first debugging, and fuzzing escalation. Use when writing or fixing tests for C (C11+) modules, stabilizing flaky suites, or reproducing memory/UB bugs.

  coding/c-testing/SKILL.md on GitHub (opens in a new tab)

• code-guidelines

  Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations on LLM coding pitfalls (Dec 2025). Use when writing, reviewing, or refactoring code across any language to avoid hidden assumptions, overengineering, orthogonal edits, vague goals, and sycophantic approval of bad requests. Especially relevant in agent-first workflows where errors are subtle con…

  coding/code-guidelines/SKILL.md on GitHub (opens in a new tab)

• cpp-patterns

  Modern C++ patterns and best practices for readable, safe, maintainable C++ code: RAII, ownership, error handling, API design, concurrency basics, and build/tooling hygiene. Use when writing or reviewing C++ (C++20+) code.

  coding/cpp-patterns/SKILL.md on GitHub (opens in a new tab)

• cpp-testing

  C++ testing workflow for unit and integration tests: GoogleTest/GoogleMock, CMake/CTest integration, diagnosing flaky tests, and running sanitizers and coverage for correctness signal. Use when writing or fixing C++ tests and test infrastructure.

  coding/cpp-testing/SKILL.md on GitHub (opens in a new tab)

• golang-patterns

  Idiomatic Go patterns, best practices, and conventions for building robust, readable, and maintainable Go code. Use when writing, reviewing, or refactoring Go (APIs, packages, errors, interfaces, concurrency, code style), choosing a dispatch or plugin mechanism, or building low-level/offensive Go with `unsafe`, `cgo`, syscall dispatch, or RE-resistant static builds.

  coding/golang-patterns/SKILL.md on GitHub (opens in a new tab)

• golang-performance

  Go performance workflow: benchmark and profile (pprof/trace), identify hotspots, reduce allocations/GC and contention, and verify improvements with repeatable measurement. Use only after you have evidence the Go code is the bottleneck.

  coding/golang-performance/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• superpowersby obra An agentic skills framework & software development methodology that works. 300k stars · 15 skills
• agent-skillsby addyosmani Production-grade engineering skills for AI coding agents. 107k stars · 25 skills
• skillsby google Agent Skills for Google products and technologies 21.3k stars · 30 skills
• garden-skillsby ConardLi ConardLi's open-source Skills collection, featuring web design, knowledge retrieval, image generation, and more. 12.9k stars · 5 skills
• ui-skillsby ibelick Skills for Design Engineers 9.8k stars · 7 skills
• Claude-Redby SnailSploit claude-red is a curated library of offensive security skills designed for the Claude skills system. Each skill is a structured SKILL.md fil… 7.5k stars · 30 skills