CtrlK
BlogDocsLog inGet started
Tessl Logo

ios-ettrace-performance

Capture and interpret iOS Simulator ETTrace profiles. Use when profiling launch or runtime latency, comparing traces, or finding CPU-heavy stacks.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 strong, executable profiling workflow with explicit validation gates and feedback loops, delegating heavy logic to bundled scripts. Tightening inlined bash or extracting a reference doc would lift progressive disclosure and conciseness.

DimensionReasoningScore

Conciseness

The body is operational and assumes Claude's competence (no explanation of ETTrace/dSYM concepts), with only minor prose that could be trimmed; it is efficient rather than padded.

4 / 5

Actionability

Copy-paste-ready bash with specific flags (--simulator, --launch, --dsyms), xcodebuild/archive invocations, and concrete coverage of launch traces, runtime traces, dSYM collection, and framework building.

5 / 5

Workflow Clarity

A 7-step core workflow plus explicit validation checkpoints (symbolication gate, dwarfdump UUID checks, capture-marker and non-empty summary error-exits) and a feedback loop (analyzer rejects JSON shape -> recapture).

5 / 5

Progressive Disclosure

Clear section structure with processing logic delegated to two real bundle scripts (collect_ios_dsyms.sh, analyze_flamegraph_json.py) one level deep, though the body itself inlines substantial bash that could warrant a reference doc.

4 / 5

Total

18

/

20

Passed

Description

73%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 concise, well-targeted description that covers what and when with concrete triggers and a distinct niche. It could list more specific capture/interpret actions and add a few more natural synonyms to push higher.

Suggestions

Expand the 'what' with one or two more concrete actions (e.g., 'symbolicate flamegraphs', 'report hotspots') to lift specificity.

Add common synonyms/file hints (e.g., 'ETTrace flamegraph', 'output_<thread>.json') to broaden natural trigger terms.

DimensionReasoningScore

Specificity

"Capture and interpret iOS Simulator ETTrace profiles" names the domain and two concrete actions, matching the anchor for 1-2 concrete actions without being comprehensive.

3 / 5

Completeness

It explicitly answers both what ("Capture and interpret iOS Simulator ETTrace profiles") and when ("Use when profiling..."), but the 'what' is terse and the 'when' could be slightly more specific.

4 / 5

Trigger Term Quality

"profiling launch or runtime latency, comparing traces, or finding CPU-heavy stacks" gives good natural keyword coverage a user would actually say, with a few synonyms missing.

4 / 5

Distinctiveness Conflict Risk

"iOS Simulator ETTrace profiles" carves a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.