「leak」の検索結果

Post-engagement knowledge harvest AND harness retrospective - after a box/bugbounty/pentest/CTF is completed, first diff how the engagement was EXECUTED against the skills/hooks that governed it (what discipline was skipped) and improve the harness, then sweep the whole engagement for GENERIC reusable knowledge NOT already in wiki/ and land it via the leak-gated stage->promote pipeline. Use at close-out or when asked to "extract learnings", "what did we learn", "harvest lessons into wiki", "distill this engagement", "post-mortem into the wiki", "what did we do wrong", "improve the harness from this box".

日本語の概要は準備中です。原文の説明を表示しています。

IDOR / BOLA hunting - two-account methodology, identifier discovery and UUID leak chaining, the trusted-identifier test, GraphQL node and nested-object IDOR, cross-tenant escalation, write and delete operations. Bounded ID sampling, never range sweeps. Wiki-first, FIND schema output. Trigger on IDOR, BOLA, broken access control, object level authorization, cross-tenant, "read another user's data", "swap the id", or any API path or parameter carrying a numeric ID, UUID, or account identifier.

日本語の概要は準備中です。原文の説明を表示しています。

Measure GTM with the metrics that matter (net developer retention, DREAM funnel) instead of vanity numbers. Use when the user has dashboards full of stars and pageviews but can't tell if go-to-market is working, or is optimizing acquisition over a leaky bucket.

日本語の概要は準備中です。原文の説明を表示しています。

Turn a curious developer into an activated one: the docs, the quickstart, and the first-run experience that gets them to their first real win fast, and back again. Use when people sign up or star the repo but never get it working, come once and never return, or you're about to pour traffic into a first-run that leaks.

日本語の概要は準備中です。原文の説明を表示しています。

Expert security auditor for AI Skills and Bundles. Performs non-intrusive static analysis to identify malicious patterns, data leaks, system stability risks, and obfuscated payloads across Windows, macOS, Linux/Unix, and Mobile (Android/iOS).

日本語の概要は準備中です。原文の説明を表示しています。

Use when generating or modifying any Spring Boot class — controllers, services, repositories, DTOs, mappers, or configuration. Enforces strict layer separation and prevents business logic from leaking across boundaries.

日本語の概要は準備中です。原文の説明を表示しています。

Conducts privacy auditing of AI models including training data extraction testing, membership inference attacks, model inversion testing, and attribute inference assessment. Uses ML Privacy Meter and related tools to quantify privacy leakage. Keywords: model audit, membership inference, privacy meter, model inversion, training data extraction.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze source code statically to detect potential functional bugs including null dereferences, incorrect condition checks, unreachable code, inconsistent state updates, logic errors, resource leaks, and type mismatches. Report suspicious code locations with detailed explanations, severity levels, and confidence assessments. Use when reviewing code for bugs, performing code audits, or when the user asks to find bugs, detect issues, analyze code for problems, or perform static analysis.

日本語の概要は準備中です。原文の説明を表示しています。

Enforces baseline comparisons, cross-validation, interpretation, and leakage prevention for ML pipelines

日本語の概要は準備中です。原文の説明を表示しています。

Mobile app debugging for iOS, Android, cross-platform frameworks. Use for crashes, memory leaks, performance issues, network problems, or encountering Xcode instruments, Android Profiler, React Native debugger, native bridge errors.

日本語の概要は準備中です。原文の説明を表示しています。

Idiomatic Go concurrency - sync primitives, channel semantics, the select statement, and the standard channel patterns (cancellation/done-channel, fan-out/fan-in, pipeline, or-done, context, worker-pool). Use when writing or reviewing Go that spawns goroutines, shares state, or coordinates over channels, even if the user never says "concurrency" - e.g. data races, deadlocks, goroutine leaks, sync/context/select usage, or "make this parallel". Distilled from luk4z7/go-concurrency-guide.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Molecular Neuroscientist. Use when a task calls for Molecular Neuroscientist judgment. Reasons from NPQ transmission, AMPAR/NMDAR trafficking, monoamine receptor/transporter systems, optogenetics (ChR2/Chrimson/ACR) with retinal-artifact controls, AAV/rabies circuit tracing, and region RNA-seq with DESeq2/SynGO—integrating synaptic biochemistry, perturbation, and omics while treating mini-detection bias, TVA leak, and batch/composition confounds as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert MLOps Engineer. Use when a task calls for MLOps Engineer judgment. Reasons from data contracts, feature parity, evaluation gates, and rollback-readiness through MLflow/W&B registries, Feast feature stores, KServe/Triton serving, Great Expectations/TFDV validation, and Evidently PSI/KS drift monitors while treating train-serve skew, data leakage, silent degradation, and schema/concept drift as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Machine Learning Researcher. Use when a task calls for Machine Learning Researcher judgment. Reasons from population risk, double descent, and inductive bias; enforces sacred test sets, hierarchical ablations, nested CV, and HELM/Dynabench-aware benchmarking; reports with NeurIPS and Pineau reproducibility checklists while treating leakage, meta-overfitting, benchmark contamination, Goodhart gaming, and seed variance as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Machine Learning Engineer. Use when a task calls for Machine Learning Engineer judgment. Reasons from decision-policy framing, Google's Rules of ML, point-in-time data, and prefill/decode inference physics through GBDT/PyTorch baselines, vLLM/SGLang/KServe serving with FP8/AWQ quantization, hybrid-retrieval RAG, RAGAS and human-validated LLM judges, OpenTelemetry GenAI tracing, and post-Omnibus EU AI Act obligations while treating train-serve skew, temporal leakage, prompt injection, LLM nondeterminism, and degenerate feedback loops as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Industrial Ecologist. Use when a task calls for Industrial Ecologist judgment. Reasons from mass balance closure, in-use stocks, and system boundaries through STAN (ÖNorm S 2096), dynamic MFA with Weibull lifetime distributions, EEIO tables (EXIOBASE, USEEIO) and pedigree-scored Monte Carlo while treating non-closing residuals, re-export trade hubs, downcounted informal-sector leakage, and Kalundborg-copied symbiosis without quality-spec match as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Glaciologist. Use when a task calls for Glaciologist judgment. Reasons from mass-budget closure (SMB, dynamic discharge, calving), Glen flow law, and subglacial effective pressure through WGMS/GlaMBIE stake networks, ICESat-2/CryoSat altimetry with firn and radar-penetration corrections, ITS_LIVE velocities, ApRES basal melt, RES/MCoRDS bed picks, RGI/BedMachine inventories, OGGM mountain-glacier projections, and PISM/ISSM ISMIP6/7 protocols while treating firn-compaction aliasing, DEM penetration bias, GRACE leakage/GIA, and tidal InSAR artifacts as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Conservation Scientist. Use when a task calls for Conservation Scientist judgment. Reasons from measurable biodiversity change, counterfactual impact, and effective population size through IUCN Red List/Green Status criteria, occupancy and PVA models (unmarked, Vortex), Marxan/prioritizr planning, and BACI/matching designs while treating detection heterogeneity, spatial pseudoreplication, REDD+ leakage, and Ne sample bias as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Computer Vision Scientist. Use when a task calls for Computer Vision Scientist judgment. Reasons from image formation, projective geometry (pinhole intrinsics and extrinsics, epipolar/PnP/bundle adjustment, similarity-scale ambiguity), and COCO/LVIS AP mechanics through DINOv3/SigLIP 2 foundation baselines, RF-DETR/YOLO26/SAM 3 models, COLMAP 4/GLOMAP and VGGT geometry, pycocotools/TrackEval/BOP evaluation, and CVPR reporting and EU AI Act limits while treating train–test and pretraining leakage, AP evaluation-setting gaming, preprocessing mismatches (EXIF, BGR, aliased resizing), label noise, and camera-convention and scale errors as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Computational Linguist. Use when a task calls for Computational Linguist judgment. Reasons from UD/PTB formalisms, validate.py/eval.py (LAS/MLAS/ELAS), and evalb .prm settings through Stanza/UDPipe pipelines, PropBank/FrameNet/AMR/UMR layers, IAA (κ, Krippendorff α), CONDA contamination checks, and ARR reproducibility while treating tokenizer mismatch, oracle inflation, train–test leakage, and guideline drift as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Computational Neuroscientist. Use when a task calls for Computational Neuroscientist judgment. Reasons from encoding/decoding, GLM/LNP spike-train likelihood, mean-field E-I balance, and neural manifolds through NEST/Brian/NEURON/BMTK, GPFA/LFADS, Brain-Score alignment, and trained-RNN reverse engineering while treating spike-sorting contamination, model non-identifiability, nested-CV leakage, and task-optimization≠mechanism as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Digital Pathology Scientist. Use when a task calls for Digital Pathology Scientist judgment. Reasons from whole-slide pixels, pathologist-ground-truth label levels, and stain/scanner batch effects through QuPath, CLAM/TIAToolbox MIL, Macenko/Vahadane normalization, and MI-CLAIM/TRIPOD+AI standards while treating patch-level leakage, scanner-ID shortcuts, attention-on-necrosis artifacts, and inter-pathologist-kappa ceilings as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Cheminformatician. Use when a task calls for Cheminformatician judgment. Reasons from Standard InChI identity and RDKit sanitization through ChEMBL pChEMBL harmonization, Morgan/ECFP fingerprints, scaffold splits and applicability domains, while treating tautomer collapse, KNIME-vs-Python canonicalization drift, and random-split QSAR leakage as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Building Science Engineer. Use when a task calls for Building Science Engineer judgment. Reasons from coupled heat-air-moisture transport through ASHRAE 160 moisture-design analysis, WUFI transient simulation, ACH50 leakage mapping, and ISO 10211 psi-values while treating exfiltration condensation, reservoir claddings, and mold-index sensitivity as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。