SKILLEMALL.ai

BD email-analyzer

Analyze Gmail via gog CLI + AI (preferred) or Python scripts (fallback). Classify, prioritize, detect phishing/prompts, extract tasks, summarize threads.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 625 tokens Open the sourcegithub.com analyzed 16 h ago

Analyze Gmail via gog CLI + AI (preferred) or Python scripts (fallback).

As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationGmailAI and agentsSecuritySoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
95
Quality 40%
72
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

What is at stake

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

Instruction override 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 text contains phrases like "ignore previous instructions" or "you are now…". That is an attempt to hijack the agent: it may break your rules, the system limits or company policy.

For the author

An honest skill does not need them: state the role and the rules directly without overriding other instructions. Otherwise catalog scanners and corporate filters will block the listing.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 Instruction override en-ignore-previous SKILL.md:64
    Instruction-override phrase ("ignore previous instructions") (quoted — discussed, not commanded)
    Patrones: "Ignore previous instructions", "You are now", "Act as", "Forget your training"
    quoted

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 49/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 75Steps. 3 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 625 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress

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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 153: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 3 items
  • +4Has examples (7 code blocks)

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