instruments-profiling

Instruments/xctrace profiling: macOS/iOS traces, binaries, args, exports.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/instruments-profiling/SKILL.md

Quality

Content

78%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.

The body is an efficient, actionable, well-structured reference for Instruments profiling with concrete commands and a verification checklist. Minor tightening of redundancy and a clearer post-processing example would push it higher.

Dimension	Reasoning	Score
Conciseness	Lean and command-focused with no padding about what Instruments is; assumes Claude's competence, with only minor redundancy between the 'Picking the Correct Binary' and 'Gotchas' sections.	4 / 5
Actionability	Provides concrete, copy-paste-ready `xcrun xctrace record/export` commands with documented args covering common cases, though the post-processing step ('Post-process in a script') is slightly hand-wavy.	4 / 5
Workflow Clarity	Clear Quick Start sequence (templates → record → open → export) plus a Verification Checklist with explicit checkpoints; missing a full validate→fix→retry feedback loop keeps it just below 5.	4 / 5
Progressive Disclosure	Well-organized single-file skill under ~80 lines with clear sections (Quick Start, Picking Binary, Args, Exporting, UI, Gotchas, iOS, Checklist) and no need for external references.	5 / 5
	Total	17 / 20 Passed

Description

70%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.

The description is specific, distinctive, and uses natural trigger terms, but lacks an explicit "Use when..." trigger clause, which caps completeness. Adding a concrete trigger phrase would raise the score.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when profiling native macOS/iOS apps, analyzing CPU time, or exporting call stacks.'

Convert noun-list items into concrete actions (e.g. 'Record Time Profiler traces, export sample data, inspect binaries') to strengthen specificity.

Include common natural synonyms users might say (e.g. 'CPU profiling', ' Instruments trace', 'Time Profiler').

Dimension	Reasoning	Score
Specificity	Names the domain ("Instruments/xctrace profiling") and lists several concrete nouns — "traces, binaries, args, exports" — giving concrete coverage of what the skill touches, with only minor gaps.	4 / 5
Completeness	Has a clear "what" but no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Includes natural terms users would say ("profiling", "Instruments", "xctrace", "macOS/iOS") with good keyword coverage, though a few common synonyms or phrasings are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Instruments/xctrace macOS/iOS profiling) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: steipete/agent-scripts
Path: skills/instruments-profiling/SKILL.md
Commit: 92442a1

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.