Otonom deney dongusu. Kod degisikligi yap, olc, karsilastir, kabul et veya geri al. Metrik bazli karar verme ile performans, boyut veya kalite optimizasyonu. Tek basina veya agent ile kullan.
npx skills add https://github.com/vibeeval/vibecosystem --skill experiment-engine
> Not / Overlap: Bu skill experiment-loop ile ayni otonom deney dongusu kavramini kapsar (bu dosya TR, experiment-loop EN). Yeni isler icin experiment-loop tercih edilir; v4.0 da birlestirilecek.
Bir hedef belirle, sistematik olarak deneyler yap, sadece iyilestirenleri tut.
HEDEF BELIRLE
└─ "API response time'i %20 dusur"
└─ "Bundle size'i 500KB'nin altina getir"
└─ "Test coverage'i %90'a cikar"
BASELINE OLC
└─ Mevcut metrigi kaydet (ornek: 340ms, 720KB, %78)
DENEY DONGUSU (N kez tekrarla):
┌─────────────────────────────────────┐
│ 1. MODIFY - Tek degisiklik yap │
│ 2. VERIFY - Metrigi olc │
│ 3. COMPARE - Baseline ile kiyasla │
│ 4. DECIDE - Kabul / Reddet │
│ ├─ Iyilesti → COMMIT + yeni │
│ │ baseline │
│ └─ Kotulesti → ROLLBACK │
└─────────────────────────────────────┘
RAPOR OLUSTUR
└─ N deney, X kabul, Y red, final metrik
# Hedef: API response time < 200ms
# Baseline: 340ms
# Deney 1: Database query'ye index ekle
git stash # mevcut durumu kaydet
# ... index ekle ...
curl -w "%{time_total}" http://localhost:3000/api/users # 280ms
# 340ms -> 280ms = IYILESTI → COMMIT
# Deney 2: Response'u cache'le
# ... Redis cache ekle ...
curl -w "%{time_total}" http://localhost:3000/api/users # 45ms
# 280ms -> 45ms = IYILESTI → COMMIT
# Deney 3: JSON serializer degistir
# ... fast-json-stringify ekle ...
curl -w "%{time_total}" http://localhost:3000/api/users # 42ms
# 45ms -> 42ms = MINIMAL IYILESME → REDDET (karmasiklik artmaya degmez)
# Sonuc: 340ms -> 45ms (%87 iyilesme), 2/3 deney kabul edildi
# Hedef: < 500KB
# Baseline olc
BASELINE=$(npx next build 2>&1 | grep "First Load JS" | awk '{print $4}')
# Deney dongusu
experiments=(
"lodash yerine lodash-es"
"moment yerine dayjs"
"tree-shaking acik mi kontrol"
"dynamic import lazy component'ler"
"image optimize (next/image)"
)
for exp in "${experiments[@]}"; do
echo "=== Deney: $exp ==="
# degisiklik yap...
NEW=$(npx next build 2>&1 | grep "First Load JS" | awk '{print $4}')
if [ "$NEW" -lt "$BASELINE" ]; then
echo "KABUL: $BASELINE -> $NEW"
BASELINE=$NEW
git add -A && git stash # kaydet
else
echo "RED: $NEW >= $BASELINE"
git checkout . # geri al
fi
done
# Hedef: %90 coverage
# Baseline
BASELINE=$(npx jest --coverage --silent 2>&1 | grep "All files" | awk '{print $4}')
# Her dosya icin test yaz, coverage'i olc
for file in $(find src -name "*.ts" -not -name "*.test.*"); do
echo "=== Test: $file ==="
# test yaz...
NEW=$(npx jest --coverage --silent 2>&1 | grep "All files" | awk '{print $4}')
if (( $(echo "$NEW > $BASELINE" | bc -l) )); then
echo "KABUL: %$BASELINE -> %$NEW"
BASELINE=$NEW
fi
done
YANLIS: Ayni anda 3 sey degistirip "daha hizli oldu" demek
→ Hangi degisiklik etkili oldugunu bilemezsin
DOGRU: Her seferinde TEK degisiklik yap
→ Neyin ise yaradigini kesin bilirsin
# Yontem 1: git stash (basit)
git stash # deney oncesi
# ... deney ...
git stash pop # basarisizsa geri al
# Yontem 2: git worktree (izole)
git worktree add /tmp/experiment-1 -b exp/perf-test
cd /tmp/experiment-1
# ... deney ...
# basarisizsa worktree'yi sil
# Yontem 3: checkpoint (karmasik deneyler)
git add -A && git commit -m "checkpoint: pre-experiment"
# ... deney ...
# basarisizsa: git reset --hard HEAD~1
interface ExperimentResult {
id: string
description: string
baseline: number
result: number
improvement: number // yuzde
accepted: boolean
duration: number // saniye
timestamp: string
}
// Deney raporu
interface ExperimentReport {
goal: string
metric: string
baselineValue: number
finalValue: number
totalExperiments: number
accepted: number
rejected: number
totalImprovement: number // yuzde
experiments: ExperimentResult[]
}
# Deney Raporu: [Hedef]
## Ozet
- Hedef: [metrik] < [esik]
- Baseline: [baslangic degeri]
- Final: [son deger]
- Iyilesme: [yuzde]
- Deneyler: [kabul]/[toplam]
## Deneyler
| # | Aciklama | Onceki | Sonraki | Degisim | Karar |
|---|----------|-------:|--------:|--------:|-------|
| 1 | Index ekle | 340ms | 280ms | -18% | KABUL |
| 2 | Redis cache | 280ms | 45ms | -84% | KABUL |
| 3 | JSON serializer | 45ms | 42ms | -7% | RED |
## Ogrenim
- En etkili: Redis cache (-84%)
- Degmez: JSON serializer degisimi (karmasiklik > kazanim)
# experiment-loop.sh
# Kullanim: ./experiment-loop.sh "response_time" "200" "ms" 10
METRIC=$1 # olculecek metrik
TARGET=$2 # hedef deger
UNIT=$3 # birim
MAX_ROUNDS=$4 # max deney sayisi
ROUND=0
BASELINE=$(measure_$METRIC)
while [ $ROUND -lt $MAX_ROUNDS ]; do
ROUND=$((ROUND + 1))
# Claude'a optimize ettir
claude -p "Optimize $METRIC. Current: ${BASELINE}${UNIT}. Target: <${TARGET}${UNIT}. Make ONE small change." --no-input
# Olc
NEW=$(measure_$METRIC)
if [ "$NEW" -lt "$BASELINE" ]; then
echo "Round $ROUND: KABUL ($BASELINE -> $NEW)"
BASELINE=$NEW
git add -A && git commit -m "experiment: $METRIC improved to ${NEW}${UNIT}"
else
echo "Round $ROUND: RED ($NEW >= $BASELINE)"
git checkout .
fi
# Hedefe ulastik mi?
if [ "$BASELINE" -le "$TARGET" ]; then
echo "HEDEF ULASILDI: ${BASELINE}${UNIT} <= ${TARGET}${UNIT}"
break
fi
done
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take vibeeval/experiment-engine from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference npx.
Without those the skill loads but fails at the first command.