home/categories/lab-tools
category focus

Lab Tools

Laboratory management and utilties.

1233 اسکلزall categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
lab-tools
79

flight-recorder

Black box flight recorder for the server. Capture system state snapshots for forensic analysis after incidents. Continuous telemetry ring buffer.

bolivian-peru
bolivian-peru
research
open
lab-tools
78

workspace

Multi-repo workspace management: clone repos, create execution runs, track papers/datasets/artifacts, manage snapshots, and review audit logs. Use when the user wants to organize multi-repo work, run experiments in sandboxes, or track research resources.

Agents2AgentsAI
Agents2AgentsAI
research
open
lab-tools
78

monitoring-feature-observability

Add or adjust monitoring for a Hypeman feature using repository standards for logs, traces, and metrics. Use when a user asks for instrumentation, observability reviews, telemetry consistency changes, metric design, or production-signal improvements.

kernel
kernel
research
open
lab-tools
78

experiment-log-summarizer

summarize machine learning experiment logs in chinese when the input includes training logs, eval results, hyperparameter changes, user notes, or multiple runs and the user needs a grounded experiment summary, error analysis, best configuration recap, or a weekly update ready abstract.

chtc66
chtc66
research
open
lab-tools
76

zot-vault-review

Periodic review skill for zot vaults. Use when the user asks for weekly review, vault maintenance, linting, retrospective, meta-learning analysis, or to turn accumulated notes into clearer understanding and output drills. Include QMD refresh and search checks, and use the smoke test when local workflow wiring needs verification. Not for first-time ingest of new sources or large cross-operation wiki rewrites.

Hurricane0698
Hurricane0698
research
open
lab-tools
76

ce-standards-gap-analyzer

Analyze standards compliance by interpreting the standards's intent, verifying that implementation and RTD satisfy every decision, and producing a dated gap report with only unresolved items.

Moffran
Moffran
research
open
lab-tools
75

lvms-analyzer

Analyzes LVMS must-gather data to diagnose storage issues

openshift-eng
openshift-eng
research
open
lab-tools
75

task-observer

Monitors task execution for skill improvement opportunities. Use this skill during ANY multi-step task, agentic workflow, or substantive work session where Claude is using tools and producing deliverables. It captures patterns, user corrections, workflow insights, and methodology worth preserving as reusable skills. Also triggers during post-task feedback discussions and when the user explicitly mentions skill observations, improvements, the observation log, skill taxonomy, or asks Claude to watch for skill opportunities. Also known as "One Skill to Rule Them All" — trigger on this phrase too. IMPORTANT: this skill should be invoked at the start of every task-oriented session — if you are about to use tools to produce deliverables, invoke this skill first.

rebelytics
rebelytics
research
open
lab-tools
74

monitor-experiments

Monitors all active and recently completed experiments across Amplitude projects, triages them by importance, then runs deep analysis and reporting on the most impactful ones. Use when the user asks to "check on experiments", "experiment status", "experiment review", "what experiments are running", or wants a periodic experiment health report.

amplitude
amplitude
research
open
lab-tools
74

analyze-experiments

Designs A/B tests with proper metrics and variants, analyzes running or completed experiments, and interprets results with statistical rigor. Use when setting up experiments, checking experiment status, analyzing results, or making ship decisions.

amplitude
amplitude
research
open
lab-tools
72

blucli

Control Bluesound/NAD players: discovery, playback, volume, grouping, and TuneIn radio via blu CLI.

emanueleielo
emanueleielo
research
open
lab-tools
72

score-task

Score a completed task's quality (0-100) for tracking per-agent quality metrics.

stevehuang0115
stevehuang0115
research
open
lab-tools
72

record-learning

Quickly record a learning or discovery while working on a task.

stevehuang0115
stevehuang0115
research
open
lab-tools
72

output-eval-validate-judge

Validate LLM judges against human labels using TPR/TNR metrics and train/dev/test splits. Use after writing a judge prompt to verify it agrees with human judgment.

growthxai
growthxai
research
open
lab-tools
71

name

A test skill

Roger-luo
Roger-luo
research
open
lab-tools
70

observability

Add observability to a codebase — logging, metrics, tracing, error handling, health checks. Teaches observability by instrumenting the student's actual project. Use when someone says /observability or asks about monitoring/debugging.

fractal-nyc
fractal-nyc
research
open
lab-tools
69

reality-testing

Reality is the ultimate judge. Use when need to ground insights in experience, test if it actually works, or validate through results not theory.

nikhilvallishayee
nikhilvallishayee
research
open
lab-tools
69

state-snapshot-instrumenter

Instrument programs (Python, C/C++, Java) to capture snapshots of key program states at runtime, including variables, memory, and call stacks. Use when you need to debug complex issues, reproduce test cases, prepare traces for formal verification, or analyze program execution. Supports manual instrumentation points, automatic function/method instrumentation, and conditional triggers. Outputs structured JSON snapshots for debugging, replay, and verification workflows.

ArabelaTso
ArabelaTso
research
open
lab-tools
69

reproduction-trace-instrumenter

Instruments programs to capture execution traces specifically for reproducing reported bugs, enabling consistent replay and diagnosis of failures. Use this skill when you need to reproduce a bug, capture execution traces for debugging, instrument code to record program behavior, generate replay scripts for bug reproduction, diagnose hard-to-reproduce failures, or perform deterministic replay of program execution. Triggers when users ask to instrument code for tracing, capture execution traces, reproduce bugs, generate replay scripts, or enable deterministic debugging.

ArabelaTso
ArabelaTso
research
open
lab-tools
69

replay-oriented-instrumentation

Instruments programs to record execution information for deterministic replay debugging. Use when debugging hard-to-reproduce bugs (race conditions, timing issues, intermittent failures, heisenbugs), reproducing production failures, or analyzing complex execution sequences. Records non-deterministic events (I/O, threading, randomness, time) to enable exact replay of program executions. Supports Python, JavaScript, Java, and C/C++ with both custom instrumentation and existing replay tools.

ArabelaTso
ArabelaTso
research
open
lab-tools
69

library-advisor

Recommend relevant Isabelle/HOL or Coq standard library theories, lemmas, and tactics based on proof goals. Use when: (1) Users need library lemmas for their proof, (2) Proof goals match standard library patterns, (3) Users ask what libraries to import, (4) Specific lemmas are needed for list/set/arithmetic operations, (5) Users are stuck and need to know what library support exists, or (6) Guidance on find_theorems/Search commands is needed. Supports both Isabelle/HOL and Coq standard libraries.

ArabelaTso
ArabelaTso
research
open
lab-tools
69

code-instrumentation-generator

Automatically instruments source code to collect runtime information such as function calls, branch decisions, variable values, and execution traces while preserving original program semantics. Use when users need to: (1) Add logging or tracing to code for debugging, (2) Collect runtime execution data for analysis, (3) Monitor function calls and control flow, (4) Track variable values during execution, (5) Generate execution traces for testing or profiling. Supports Python, Java, JavaScript, and C/C++ with configurable instrumentation levels.

ArabelaTso
ArabelaTso
research
open
lab-tools
68

fix-observe

[OBSERVE:problem|step=1-of-3]=>[READ:error+screenshot]=>[DESCRIBE:symptom]

ilang-ai
ilang-ai
research
open
lab-tools
68

fix-observe

Three-step method step 1. Observe the problem carefully before jumping to conclusions.

ilang-ai
ilang-ai
research
open
Previous
Page 19 / 52
Next