hopper-debugger

Hopper debugging: macOS/iOS binaries, ObjC/Swift symbols, dyld, LLDB.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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, fully-executable operational reference: concrete mcporter/LLDB commands, a sequenced query workflow with an explicit validation checkpoint, and well-structured failure-handling feedback loops, with no padding or concept re-explanation.

Dimension	Reasoning	Score
Conciseness	The body never explains what Hopper, dyld, or ObjC are; it assumes Claude's competence, and every prose line is non-obvious operational guidance (import dialogs, concurrent-call crashes, hardened-signed attach limits, daemon restart preference) rather than filler.	3 / 3
Actionability	Every step is a concrete, copy-paste-ready shell command (e.g. 'MCPORTER_CALL_TIMEOUT=20000 timeout 30 mcporter call hopper.list_documents --output json', 'mcporter call hopper.procedure_pseudo_code procedure=... --output json'), with no pseudocode.	3 / 3
Workflow Clarity	The numbered 'Query Workflow' ends with an explicit validation checkpoint ('Validate the hypothesis with LLDB/logging/repro before editing app code'), and the 'Failure Handling' section provides feedback loops (Connection closed -> check modal -> retry; crash -> reopen -> wait for import -> re-run list_documents).	3 / 3
Progressive Disclosure	No bundle files exist and none are needed; the body is self-contained and organized into clearly navigable sections (Quick Start, Apple Frameworks, Query Workflow, Status Item bugs, Failure Handling) with no monolithic walls or nested references.	3 / 3
	Total	12 / 12 Passed

Description

72%

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 distinctive and uses strong natural trigger terms, but it lacks an explicit 'when to use' clause and lists only one generic action, leaving its capabilities under-specified. It is a solid keyword-style description that would benefit from a brief Use-when trigger and one or two concrete verbs.

Suggestions

Add an explicit trigger clause, e.g. 'Use when debugging macOS/iOS binaries, resolving ObjC/Swift symbol resolution issues, or tracing calls through dyld with Hopper and LLDB.'

Replace the single generic verb 'debugging' with concrete actions such as 'disassemble, inspect symbols, trace xrefs, and cross-reference with LLDB'.

Keep the keyword list but weave it into a short sentence so the description reads as a statement of capability rather than a tag dump.

Dimension	Reasoning	Score
Specificity	The phrase 'Hopper debugging' names the activity and the tech list ('macOS/iOS binaries, ObjC/Swift symbols, dyld, LLDB') names the domain and tools, but it does not enumerate multiple concrete actions (e.g. disassemble, inspect symbols, trace xrefs); it stops at the single generic verb 'debugging'.	2 / 3
Completeness	It states what the skill does (Hopper debugging on the listed targets) but has no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2 with 'when' only implied.	2 / 3
Trigger Term Quality	'Hopper', 'LLDB', 'ObjC/Swift symbols', 'dyld', and 'macOS/iOS binaries' are exactly the natural terms a user would say when they need this skill, giving good trigger coverage.	3 / 3
Distinctiveness Conflict Risk	'Hopper debugging' combined with dyld/LLDB/ObjC-Swift symbols carves a clear, narrow niche that would not reasonably trigger for any other skill.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: steipete/agent-scripts
Path: skills/hopper-debugger/SKILL.md
Commit: bb36883

Reviewed: about 13 hours 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.