SKILLEMALL.ai
GitHub ↗ RU Sign in

CC geo-report

Generate a professional, client-facing GEO report combining all audit results into a single deliverable with scores, findings, and prioritized actions

sickn33/agentic-awesome-skills Hermes author: sickn33 MIT 1 file body ≈ 4 552 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Generate a professional, client-facing GEO report combining all audit results into a single deliverable with scores, findings, and prioritized actions

As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

AnalyzerData and analyticstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code Hermes Agent
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
95
Quality 40%
79
Run on models
none yet
Process rating
C
57/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
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: geo-report (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.
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: Read Grep Glob Bash WebFetch Write

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

Against the Agent Skills spec

  • warning description-long-hermes description is 150 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • 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"

Process rating: all ten parameters 57/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 6 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 70Execution cost. Instruction body is 4552 tokens
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 60 steps
  • 100Consistency. Name and required fields are in place

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
  • +4Description does not say when NOT to use the skill (false activations)
  • +2Single-language instructions
  • +3Description length 150: enough signal without eating the budget
  • +4Structure: 31 headings
  • +3Step-by-step instructions: 60 items
  • +3Output format is stated explicitly
  • +4Has examples (15 code blocks)
  • +1License stated

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