frida

Dynamic instrumentation via Frida - attach to or spawn a process, load a JS hook script, capture send() events into a lifecycle-managed run directory. Supports local, USB-attached, and remote frida-server targets.

Quality

78%

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 ./.claude/skills/frida/SKILL.md

Quality

Content

82%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 highly actionable and well-structured with executable commands and a clear error-recovery table, with only minor room to tighten prose and make the workflow sequence more explicit.

Dimension	Reasoning	Score
Conciseness	Dense and skill-specific with no padding of concepts Claude already knows; a few sections (evidence caveat, some template rows) could be tightened slightly.	4 / 5
Actionability	Fully executable, copy-paste-ready install commands, full invocation syntax with flags, five concrete example commands covering local/spawn/USB/remote/custom-hook, and a runnable Python API block.	5 / 5
Workflow Clarity	A clear install→invoke→read-output sequence is present and the 'Failure modes (read metadata.json first)' table provides an error→cause→fix feedback loop, but it is not framed as an explicit numbered workflow with validation checkpoints.	4 / 5
Progressive Disclosure	Well-organized sections with a single clearly signaled one-level-deep reference (docs/frida.md) and no bundle files to misplace; the body is self-contained though somewhat long, keeping it just short of a 5.	4 / 5
	Total	17 / 20 Passed

Description

75%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 Frida-domain terms, but omits any 'Use when...' trigger guidance, which caps completeness at 3.

Suggestions

Add an explicit 'Use when...' clause naming trigger scenarios (e.g., 'Use when confirming a flagged sink fires at runtime, tracing API calls, or bypassing SSL pinning on a pinned mobile app').

Include one or two natural-phrase synonyms alongside the technical terms (e.g., 'runtime hooking', 'process tracing') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'attach to or spawn a process, load a JS hook script, capture send() events into a lifecycle-managed run directory' — plus local/USB/remote target modes, giving comprehensive coverage.	5 / 5
Completeness	The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Domain-natural terms ('Dynamic instrumentation', 'Frida', 'hook script', 'attach/spawn', 'frida-server') match what a user needing this skill would say, but no synonyms or natural-phrase variants are included.	4 / 5
Distinctiveness Conflict Risk	'Dynamic instrumentation via Frida' names a clear niche with distinct triggers (frida-server, JS hook script) and minimal overlap with other skills.	5 / 5
	Total	17 / 20 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: gadievron/raptor
Path: .claude/skills/frida/SKILL.md
Commit: a5deef3

Reviewed: 2 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.