CtrlK
BlogDocsLog inGet started
Tessl Logo

instruments-profiling

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

73

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The content is a lean, highly actionable reference: executable xctrace commands, a clear sequencing with validation checkpoints, and well-organized sections. It is a strong example of a concise single-file skill with no unnecessary explanation.

DimensionReasoningScore

Conciseness

The body is lean and operational — bullets and copy-paste commands with no padding explaining what Instruments is or how profilers work — so every token earns its place and assumes Claude's competence.

3 / 3

Actionability

Provides fully executable commands with concrete flags (e.g., the full 'xctrace record --template "Time Profiler" ... --launch --' and the export --xpath example) that are copy-paste ready and specific.

3 / 3

Workflow Clarity

The record→pick-binary→export flow is clearly sequenced and reinforced by a Verification Checklist and confirm-the-process-path checkpoints, matching the anchor for clear sequence with explicit validation steps.

3 / 3

Progressive Disclosure

No bundle files exist and the ~80-line body is organized into well-signaled sections (Quick Start, Picking the Correct Binary, Exporting, UI Workflow, Gotchas, Verification Checklist), which per the scoring notes scores 3 for skills with no external references.

3 / 3

Total

12

/

12

Passed

Description

82%

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, well-keyworded, and clearly distinctive, but it lacks an explicit 'Use when...' trigger clause, capping completeness at 2. Adding a one-line trigger guidance (e.g., 'Use when profiling macOS/iOS native apps or analyzing call stacks') would lift completeness to 3.

Suggestions

Append an explicit trigger clause such as 'Use when the user wants to profile or analyze performance of macOS/iOS native apps' to satisfy the 'when' requirement and raise completeness to 3.

Lead capability areas with verbs (e.g., 'Record, attach, and export Time Profiler traces') to make the actions more concrete than a noun enumeration.

Add common user phrasings like 'CPU profiling', 'hot paths', or 'call stacks' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the tool ('Instruments/xctrace profiling') and enumerates multiple concrete capability areas ('macOS/iOS traces, binaries, args, exports'), matching the anchor for listing several specific concrete actions rather than vague language.

3 / 3

Completeness

Clearly answers 'what' but provides no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 2 with 'when' only implied.

2 / 3

Trigger Term Quality

Includes natural terms a user would say for this domain — 'profiling', 'Instruments', 'xctrace', 'macOS/iOS traces' — giving good coverage rather than only some relevant keywords.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (Apple Instruments/xctrace profiling) with distinct, domain-specific triggers unlikely to conflict with other skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
steipete/agent-scripts
Reviewed

Table of Contents

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.