SKILLEMALL.ai

BC luma

Luma Event Manager for Clawdbot — Discover events by topic or location, RSVP, view guest lists, and sync to Google Calendar. No API key required (web scraping), no Luma Plus subscription needed. Repo: github.com/mariovallereyes/luma-skill

modbender/skill-library-mcp Agent Skills author: modbender MIT 13 files body ≈ 566 tokens Open the sourcegithub.com analyzed 2 d ago

Luma Event Manager for Clawdbot — Discover events by topic or location, RSVP, view guest lists, and sync to Google Calendar.

As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationGitHubPersonal productivitytype 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
C
56/100
Has gaps
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

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 · 5

✓ No critical or high findings

Medium and low: 5
  • low Secrets in code secret-high-entropy-token package-lock.json:63
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…NxY+fzEC…TMw+Dfs3…h4g==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:122
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…9co+7Zrb…CSH/zJvXw56gmHw==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:163
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…Eg5+wW0/QaZM…swK/w2MWU+Gw==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:207
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…uff+RtWa…OPA==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:219
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…CUH+OiuIgU++RB0+94Nl…dMw==",
    detector

Files scanned: 13. 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 56/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
  • 40Consistency. Frontmatter name (luma) differs from the folder (luma-event-manager)
  • 50Failures and branches. 0 branches, has a failure section
  • 100Tools and files. No external tools needed
  • 100Steps. 30 steps
  • 100Execution cost. Instruction body is 566 tokens
  • 100Running it twice. No mutating operations
  • 100Progress reporting. Reports progress
  • low The response is described with custom markup (4 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
  • +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 238: enough signal without eating the budget
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 30 items
  • +4Has examples (4 code blocks)

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