SKILLEMALL.ai
GitHub ↗ RU Sign in

BB competitor-analysis

Research competitors with Browserbase discovery, enrichment lanes, screenshots, matrices, and HTML reports.

sickn33/agentic-awesome-skills Hermes author: sickn33 MIT 17 files body ≈ 7 759 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Research competitors with Browserbase discovery, enrichment lanes, screenshots, matrices, and HTML reports.

As a process B 66/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice

AnalyzerGitHubCloudflareMarketingResearchtype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code Hermes Agent
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
95
Quality 40%
68
Run on models
none yet
Process rating
B
66/100
Nearly there
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: competitor-analysis (sickn33/agentic-awesome-skills)

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 1

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Bash Agent AskUserQuestion

Files scanned: 16. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 107 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning body-long SKILL.md body ≈ 7759 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "risk"
  • note frontmatter-key unknown frontmatter key "source"
  • note frontmatter-key unknown frontmatter key "source_repo"
  • note frontmatter-key unknown frontmatter key "source_type"
  • note frontmatter-key unknown frontmatter key "date_added"
  • note frontmatter-key unknown frontmatter key "license_source"
  • note frontmatter-key unknown frontmatter key "tools"

Process rating: all ten parameters 66/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 9 mutating operations with no state check
  • 70Execution cost. Instruction body is 7759 tokens
  • 85Steps. 98 steps, 2 vague phrases
  • 100Tools and files. Tools declared in frontmatter
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 4 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 12 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (3 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +3Description length 107: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -31 of 7 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +4Description says when NOT to use the skill
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 98 items
  • +4Has examples (14 code blocks)
  • +4Reference files are cited in the instructions (5 of 5)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.