CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reverse-engineer-anything

Investiga sistemas distribuidos e artefatos por engenharia reversa autorizada. Trigger em: "analisar binário", "decompilar APK", "inspecionar ASAR", "analisar app Electron sem código-fonte", "inspecionar firmware", "browser sem código-fonte", "reverse engineer this binary", "comparar versões compiladas", "rea-agents", "usar REA", "REA MCP", "engenharia reversa de binário", "engenharia reversa de aplicativo distribuído".

Quality

83%

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

81%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 dense, well-structured skill body with a clear routing table, an executable CLI fallback, and an investigation workflow that has genuine validation checkpoints and a per-question evidence ledger. The main gaps are unresolved referenced paths (governance policies and LICENSE-REA missing from the bundle) and version-pinned provenance details that add time-sensitive tokens.

Suggestions

Add the missing LICENSE-REA file and the referenced policies/ files to the bundle (or restate the governance rules inline) so every path cited in the body resolves.

Move the version-pinned provenance details (v36, full commit hash, consultation date) into a dedicated provenance/deprecated note or shorten them, keeping time-sensitive details out of the main instruction flow.

Provide one fully parameterized example of a common REA tool call (e.g., open_binary or inspect_android_package with its argument shape) so the most frequent path is copy-paste ready without consulting reference files.

DimensionReasoningScore

Conciseness

The body is lean and telegraphic, assumes Claude's competence, and contains no explanations of known concepts; every section carries operational rather than background content. Not 5 because 'Fontes Externas' pins time-sensitive version/date details (v36, full commit hash, 'consultado em 2026-10-10') outside any deprecated/old-patterns section, and a few governance sentences stack multiple caveats that could be tightened; not 3 because there is no padding or unnecessary explanation.

4 / 5

Actionability

The routing table gives a concrete first REA tool per target type ('open_binary no caminho fornecido', 'inspect_android_package com APK explícito', 'list_browser_targets no endpoint loopback'), and the ASAR fallback includes a copy-paste-ready CLI block (npx analyze-javascript-application + jq + inspect-analysis-view) plus specific parameters like detail: "summary" and provider_id: "ida". Not 5 because most REA tool invocations are named without full parameters (deferred to live session schemas), so only some common cases are fully executable as written; not 3 because the guidance is genuinely executable rather than pseudocode.

4 / 5

Workflow Clarity

The 'Fluxo de investigação' is a clear five-step sequence with explicit validation checkpoints: a per-question ledger (Evidence ID/location, hypothesis, support/contradiction, coverage, unknowns), marking each question answered/partially answered/pending, exporting Evidence before closing with close_binary, and validating any reconstruction against the real app before claiming equivalence. Error-recovery guidance is also present (tool absence is not a negative finding; misaligned-but-absent registry suggests reconnect/restart), matching anchor 5 rather than anchor 4's 'minor validation gaps'.

5 / 5

Progressive Disclosure

The body is an overview that routes each target type to one of five real, one-level-deep reference files via a table, with explicit navigation guidance ('Leia só o guia relevante em references/'); the reference files link only back to the parent SKILL.md and to siblings, with no nested local references. Not 5 because the body also cites GLOBAL.md, five policies/*.md files, and LICENSE-REA, none of which exist in the bundle — unresolved paths that break navigation; not 3 because the core structure and signaling are otherwise good.

4 / 5

Total

17

/

20

Passed

Description

82%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 strong description with an explicit, bilingual trigger list and a clearly staked-out niche. The main weakness is that the capability statement itself is one broad action, leaving the concrete operations to be inferred from the trigger phrases rather than stated as capabilities.

DimensionReasoningScore

Specificity

The capability statement 'Investiga sistemas distribuidos e artefatos por engenharia reversa autorizada' names the domain but expresses only one broad action; concrete operations (decompilar, inspecionar, comparar versões) appear only as trigger phrases rather than stated capabilities. This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) — below 4 because no list of several specific capability actions is given, above 2 because the domain is named and the triggers convey concrete operations.

3 / 5

Completeness

It explicitly answers both 'what' ('Investiga sistemas distribuidos e artefatos por engenharia reversa autorizada') and 'when' with a dedicated explicit trigger list ('Trigger em: ...' followed by concrete phrases), in third-person voice. This clearly matches anchor 5 — both what and when with concrete trigger phrases — rather than anchor 4, where the 'when' would be less explicit.

5 / 5

Trigger Term Quality

Thirteen natural trigger phrases across Portuguese and English ('analisar binário', 'decompilar APK', 'inspecionar ASAR', 'inspecionar firmware', 'reverse engineer this binary', 'comparar versões compiladas') give good keyword coverage a user would naturally say. Not 5 because file extensions (.apk, .asar, .bin, .ipa) and common synonyms such as 'disassemble' or 'decompile this APK' are missing; not 3 because coverage goes well beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — authorized reverse engineering of distributed binaries, APKs, ASAR/Electron apps, and firmware without source — with triggers ('decompilar APK', 'inspecionar ASAR', 'rea-agents', 'REA MCP') that are highly specific and unlikely to fire for other skills. Minimal conflict risk, matching anchor 5 rather than anchor 4's 'minor overlap risk'.

5 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 1 possibly missing (LICENSE-REA)

Warning

Total

13

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/87-reverse-engineer-anything/SKILL.md

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.