Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

perf-benchmarker

Estrelas1.758

Forks459

Atualizado4 de fevereiro de 2026 às 09:09

Use when running performance benchmarks, establishing baselines, or validating regressions with sequential runs. Enforces 60s minimum runs (30s only for binary search) and no parallel benchmarks.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

ComposioHQ

ComposioHQ/awesome-claude-plugins

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	perf-benchmarker
description	Use when running performance benchmarks, establishing baselines, or validating regressions with sequential runs. Enforces 60s minimum runs (30s only for binary search) and no parallel benchmarks.
version	1.0.0
argument-hint	<command> [duration]

perf-benchmarker

Run sequential benchmarks with strict duration rules.

Follow docs/perf-requirements.md as the canonical contract.

Required Rules

Benchmarks MUST run sequentially (never parallel).
Minimum duration: 60s per run (30s only for binary search).
Warmup: 10s minimum before measurement.
Re-run anomalies.

Output Format

command: <benchmark command>
duration: <seconds>
warmup: <seconds>
results: <metrics summary>
notes: <anomalies or reruns>

Output Contract

Benchmarks MUST emit a JSON metrics block between markers:

PERF_METRICS_START
{"scenarios":{"low":{"latency_ms":120},"high":{"latency_ms":450}}}
PERF_METRICS_END

Constraints

No short runs unless binary-search phase.
Do not change code while benchmarking.

Mais deste repositório

mesmo repositório

add-sub

ComposioHQ/awesome-claude-plugins

Subscribe to a skill event. Adds a subscription that injects context before or after a skill runs. Supports optional conditions at both insert-level (inherited by all subscriptions) and subscription-level (AND-stacked). Conditions include fileExists, gitBranch, envSet, envEquals, fileContains (with optional regex).

2026-02-111.8k

help

ComposioHQ/awesome-claude-plugins

Show skill-bus overview, status, and available commands. Quick reference for all skill-bus features.

2026-02-111.8k

list-subs

ComposioHQ/awesome-claude-plugins

List all active skill-bus subscriptions across global and project scopes, showing merge status, insert-level and subscription-level conditions, effective condition stacking, and what would fire for each skill.

2026-02-111.8k

pause-subs

ComposioHQ/awesome-claude-plugins

Temporarily disable the skill bus. Quick toggle to stop all subscriptions from firing without removing them.

2026-02-111.8k

reflecting-on-sessions

ComposioHQ/awesome-claude-plugins

Use when completing a plan, finishing a development branch, wrapping up a session, or at any natural transition between work phases — reviews skill-bus telemetry to identify subscription gaps and suggest improvements

2026-02-111.8k

remove-sub

ComposioHQ/awesome-claude-plugins

Unsubscribe from a skill event. Removes or disables subscriptions with scope-aware options.

2026-02-111.8k

name	perf-benchmarker
description	Use when running performance benchmarks, establishing baselines, or validating regressions with sequential runs. Enforces 60s minimum runs (30s only for binary search) and no parallel benchmarks.
version	1.0.0
argument-hint	<command> [duration]

perf-benchmarker

Run sequential benchmarks with strict duration rules.

Follow docs/perf-requirements.md as the canonical contract.

Required Rules

Benchmarks MUST run sequentially (never parallel).
Minimum duration: 60s per run (30s only for binary search).
Warmup: 10s minimum before measurement.
Re-run anomalies.

Output Format

command: <benchmark command>
duration: <seconds>
warmup: <seconds>
results: <metrics summary>
notes: <anomalies or reruns>

Output Contract

Benchmarks MUST emit a JSON metrics block between markers:

PERF_METRICS_START
{"scenarios":{"low":{"latency_ms":120},"high":{"latency_ms":450}}}
PERF_METRICS_END

Constraints

No short runs unless binary-search phase.
Do not change code while benchmarking.