CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

jsmax

High-impact JavaScript analysis and exploitation engine. Use when you have a list of JS URLs and need to extract secrets, endpoints, JWTs, MD5 hashes, and critical data to prove high-impact vulnerabilities (PII dump, cloud takeover).

Quality

84%

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

78%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 well-structured, actionable skill body with a clear sequenced workflow, verified bundle references, and strong progressive disclosure. The weakest areas are mild persona padding, a few vague verification steps, and a loosely defined failure-retry loop.

Suggestions

Trim motivational persona lines ('You are a top 1% bug hunter', 'The "Money" Phase', the 'Core Mandate' section) to save tokens without losing operational value.

Make failure recovery an explicit loop: instruct re-running the fetch on FAILURE URLs (the script already retries internally) before falling back to analyzing the URL string itself.

Tighten vague verification steps like 'If you find an MD5 hash, check for common values' by referencing a concrete method (e.g., a wordlist lookup command as given in references/exploitation.md).

DimensionReasoningScore

Conciseness

The operational content is dense and efficient — pattern prefixes (AKIA, ghp_, glpat_), an exact fetch command, and the output protocol format — with only minor padding that could be trimmed ('You are a top 1% bug hunter', 'The "Money" Phase', and the closing 'Core Mandate' section of motivational lines). It does not reach anchor 5 because those persona-fluff lines are not pure operational content.

4 / 5

Actionability

Mostly executable guidance: the copy-paste-ready 'python scripts/fetch_js.py <url_list_file> ./jsmax_downloads 10 <offset>' with its documented protocol outputs, specific detection patterns, and a structured reporting template. Minor gaps keep it below anchor 5 — e.g., 'If you find an MD5 hash, check for common values' is vague and offset iteration is described but not exemplified.

4 / 5

Workflow Clarity

A clear 5-phase sequence with explicit validation checkpoints for the batch operation ('verify that PROGRESS|END matches the expected offset', FAILURE status handling, completeness summary in results), so the batch-operation cap at 3 does not apply. Below anchor 5 because failure recovery says to 'note it for a manual retry later' rather than defining an explicit validate→fix→retry loop.

4 / 5

Progressive Disclosure

Clean structure: the SKILL.md body is a workflow overview with the scanning catalog, escalation patterns are split into references/exploitation.md (verified to exist with real, non-nested content), and tooling lives in scripts/fetch_js.py (whose output protocol matches the body's documented format exactly). References are one level deep and well-signaled at point of use, matching the anchor 5 example.

5 / 5

Total

17

/

20

Passed

Description

83%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 explicit what/when structure, concrete capability lists, and domain-appropriate trigger terms. The main deductions are the second-person voice and a few missing natural synonyms like '.js files'.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('extract secrets, endpoints, JWTs, MD5 hashes, and critical data to prove high-impact vulnerabilities (PII dump, cloud takeover)'), which approaches anchor 5, but the second-person phrasing 'Use when you have a list of JS URLs and need to...' incurs the rubric's third-person voice penalty of 1. It is above anchor 3 because coverage of the domain's actions is comprehensive, not just 1-2 items.

4 / 5

Completeness

It clearly answers both what ('extract secrets, endpoints, JWTs, MD5 hashes, and critical data to prove high-impact vulnerabilities') and when ('Use when you have a list of JS URLs and need to...') with concrete trigger phrases, matching the anchor 5 example structure. Not anchor 4 because the 'when' clause is fully explicit rather than merely improvable.

5 / 5

Trigger Term Quality

Good natural keyword coverage including 'JavaScript', 'JS URLs', 'secrets', 'JWTs', 'MD5 hashes', 'PII dump', and 'cloud takeover' — terms a bug-hunting user would actually say. It falls short of anchor 5 because common variations like '.js files', 'JavaScript files', or 'API keys' are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (secret hunting in JS files for bug bounty) with a distinct trigger ('a list of JS URLs'), but 'High-impact JavaScript analysis' could minorly overlap with generic JS code-review or security-audit skills. Not anchor 5 due to that residual overlap risk; clearly above anchor 3's 'could still overlap with similar skills'.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Awarexone/Agentic-Bug-Hunter

Path

skills/jsmax/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.