but-performance-tests

Use when creating, changing, running, or debugging shell-based `but` CLI performance scenarios under `crates/but/tests/performance`, including Hyperfine runs, fixture setup, setup-to-test state, and output inspection.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, well-structured instruction skill that leverages a canonical README for detail and provides a clear sequenced workflow with guardrails. It could be improved by inlining a short representative example command and an explicit validate-fix-retry loop.

Suggestions

Inline one or two short representative shell commands (e.g., a sample Hyperfine invocation or the README validation command) so the skill is actionable without first opening the README.

Add an explicit feedback loop after the validation/benchmark step (e.g., 'If validation fails, fix the scenario and re-run validation before proceeding').

Replace mild hedges like 'as applicable' with a concrete condition to tighten the already-lean guidance further.

Dimension	Reasoning	Score
Conciseness	The body is lean and instruction-only, deferring detail to the canonical README and avoiding explanation of concepts Claude already knows; the few hedges present ('as applicable', 'genuinely required') encode real constraints rather than padding.	5 / 5
Actionability	Names concrete files (lib.sh, run.sh, setup.sh, test.sh) and specific operations, but provides no inline copy-paste commands, relying entirely on the referenced README for executable detail.	4 / 5
Workflow Clarity	A clear 8-step sequenced workflow includes validation (step 8) and keeping validation outside the timed operation (step 5), but lacks an explicit error-recovery feedback loop (validate -> fix -> retry).	4 / 5
Progressive Disclosure	SKILL.md acts as a concise overview with a single well-signaled one-level-deep reference to the performance README, and content is appropriately split into Workflow and Guardrails sections under 50 lines.	5 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, well-triggered description that clearly conveys both capability and use conditions for a narrow performance-testing niche. Its only gap is missing common synonyms like 'benchmark' that users might naturally say.

Dimension	Reasoning	Score
Specificity	Lists the full scenario lifecycle (creating, changing, running, debugging) plus concrete sub-tasks (Hyperfine runs, fixture setup, setup-to-test state, output inspection), giving comprehensive action coverage rather than just a few with minor gaps.	5 / 5
Completeness	Explicitly answers both 'what' (the scenario operations and included sub-tasks) and 'when' via a concrete 'Use when creating, changing, running, or debugging...' trigger tied to a specific path.	5 / 5
Trigger Term Quality	Includes natural terms like 'creating', 'running', 'debugging', 'performance scenarios', and 'Hyperfine runs', but omits common synonyms a user might say such as 'benchmark' or 'perf tests', so it falls short of comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	Tightly scoped to shell-based `but` CLI performance scenarios under a specific directory with Hyperfine, giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: gitbutlerapp/gitbutler
Path: .agents/skills/but-performance-tests/SKILL.md
Commit: e64149e

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.