CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

web-cms-scanning

CMS-specific scans — WordPress (wpscan), Joomla, Drupal version detection.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/recon/web-recon/cms-scanning/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, command-first skill: lean token usage, executable copy-paste commands, an explicit entry condition, and clean per-CMS organization. The only weaknesses are thin Joomla/Drupal coverage and the absence of validation/next-step checkpoints for acting on scan results.

DimensionReasoningScore

Conciseness

The body is lean — a two-line entry condition followed by grouped, commented commands — with zero padding and no explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Commands are concrete and executable (wpscan with enumeration flags and API token, ready-to-run curl one-liners with standard <target> placeholders), but there are minor gaps: no guidance on interpreting output or next steps, and Joomla/Drupal coverage is a single version-check command each.

4 / 5

Workflow Clarity

The entry condition is explicit ('Once tech fingerprinting (or HTML inspection) confirms a CMS, switch from generic discovery to CMS-aware tooling') and dispatch is cleanly organized per CMS, but there are no checkpoints for validating or acting on findings (e.g., what to do with enumerated versions or vulnerable plugins).

4 / 5

Progressive Disclosure

This is a sub-50-line skill with no external references needed; the per-CMS section structure is well-organized, which per the rubric's simple-skill guidance earns a 5 with just well-organized sections (confirmed: no references/, scripts/, or assets/ bundle files exist).

5 / 5

Total

18

/

20

Passed

Description

65%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, distinct description with good natural trigger terms, but it lacks an explicit 'Use when...' clause and its action coverage is thin ('scans', 'version detection'), so completeness is capped at the 'clear what, missing when' anchor.

Suggestions

Add an explicit trigger clause, e.g., 'Use when WordPress, Joomla, or Drupal is confirmed on a target, or when the user mentions CMS scanning or wpscan.'

Broaden the action vocabulary beyond 'scans' and 'version detection' to reflect the body's coverage — e.g., 'enumerate plugins, themes, and users'.

Include a natural synonym such as 'content management system' to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('CMS-specific scans') and concrete elements — 'WordPress (wpscan)' and 'Drupal version detection' — but the action vocabulary is limited to 'scans' and 'version detection', leaving coverage gaps (plugin/theme enumeration, user enum) that keep it at '1-2 concrete actions, not comprehensive'.

3 / 5

Completeness

The 'what' is clear (CMS-specific scanning with version detection across WordPress/Joomla/Drupal), but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural keywords users would say are present — 'WordPress', 'wpscan', 'Joomla', 'Drupal', 'CMS' — giving good keyword coverage, but synonyms like 'content management system' or 'wp' are missing, so it falls short of the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche by naming specific platforms (WordPress, Joomla, Drupal) and a specific tool (wpscan), making it highly distinguishable from other skills with minimal conflict risk.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/recon/web-recon/cms-scanning/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.