AGENT SKILL

worker-benchmarks

Run comprehensive worker system benchmarks and performance analysis

License 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

01 前言 Front Matter

name
worker-benchmarks
author
agentic-flow
version
1.0.0
invocable
true
description
Run comprehensive worker system benchmarks and performance analysis
capabilities
[ "performance_testing", "metrics_collection", "optimization_recommendations" ]

03 SKILL.md 正文

Worker Benchmarks Skill

Run comprehensive performance benchmarks for the agentic-flow worker system.

Quick Start

# Run full benchmark suite
npx agentic-flow workers benchmark

# Run specific benchmark
npx agentic-flow workers benchmark --type trigger-detection
npx agentic-flow workers benchmark --type registry
npx agentic-flow workers benchmark --type agent-selection
npx agentic-flow workers benchmark --type concurrent

Benchmark Types

1. Trigger Detection (trigger-detection)

Tests keyword detection speed across 12 worker triggers.

  • Target: p95 < 5ms
  • Iterations: 1000
  • Metrics: latency, throughput, histogram

2. Worker Registry (registry)

Tests CRUD operations on worker entries.

  • Target: p95 < 10ms
  • Iterations: 500 creates, gets, updates
  • Metrics: per-operation latency breakdown

3. Agent Selection (agent-selection)

Tests performance-based agent selection.

  • Target: p95 < 1ms
  • Iterations: 1000
  • Metrics: selection confidence, agent scores

4. Model Cache (cache)

Tests model caching performance.

  • Target: p95 < 0.5ms
  • Metrics: hit rate, cache size, eviction stats

5. Concurrent Workers (concurrent)

Tests parallel worker creation and updates.

  • Target: < 1000ms for 10 workers
  • Metrics: per-worker latency, memory usage

6. Memory Key Generation (memory-keys)

Tests memory pattern key generation.

  • Target: p95 < 0.1ms
  • Iterations: 5000
  • Metrics: unique patterns, throughput

Output Format

═══════════════════════════════════════════════════════════
📈 BENCHMARK RESULTS
═══════════════════════════════════════════════════════════

✅ Trigger Detection
   Operation: detect
   Count: 1,000
   Avg: 0.045ms | p95: 0.120ms (target: 5ms)
   Throughput: 22,222 ops/s
   Memory Δ: 0.12MB

✅ Worker Registry
   Operation: crud
   Count: 1,500
   Avg: 1.234ms | p95: 3.456ms (target: 10ms)
   Throughput: 810 ops/s
   Memory Δ: 2.34MB

───────────────────────────────────────────────────────────
📊 SUMMARY
───────────────────────────────────────────────────────────
Total Tests: 6
Passed: 6 | Failed: 0
Avg Latency: 0.567ms
Total Duration: 2345ms
Peak Memory: 8.90MB
═══════════════════════════════════════════════════════════

Integration with Settings

Benchmark thresholds are configured in .claude/settings.json:

{
  "performance": {
    "benchmarkThresholds": {
      "triggerDetection": { "p95Ms": 5 },
      "workerRegistry": { "p95Ms": 10 },
      "agentSelection": { "p95Ms": 1 },
      "memoryKeyGeneration": { "p95Ms": 0.1 },
      "concurrentWorkers": { "totalMs": 1000 }
    }
  }
}

Programmatic Usage

import { workerBenchmarks, runBenchmarks } from 'agentic-flow/workers/worker-benchmarks';

// Run full suite
const suite = await runBenchmarks();
console.log(suite.summary);

// Run individual benchmarks
const triggerResult = await workerBenchmarks.benchmarkTriggerDetection(1000);
const registryResult = await workerBenchmarks.benchmarkRegistryOperations(500);

Performance Optimization Tips

  1. Model Cache: Enable with CLAUDE_FLOW_MODEL_CACHE_MB=512
  2. Parallel Workers: Enable with CLAUDE_FLOW_WORKER_PARALLEL=true
  3. Warning Suppression: Enable with CLAUDE_FLOW_SUPPRESS_WARNINGS=true
  4. SQLite WAL Mode: Automatic for better concurrent performance

04 同仓库更多 Skills

YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

vercel-sandbox

Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

slack

Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

electron

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

dogfood

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.

★ 1