BB team-calendar
Team calendar: event, type, date and time with time zone, attendees, organizer, location and source module. Use for shared scheduling.
The skill promises shared calendar management with events, types, dates, times with timezone support, attendees, organizers, locations, and module sources. Marketed as a team scheduling synchronization tool.
Testing shows a B grade with 79/100 quality score. No critical issues found, security at 100. However, the process score of 69 suggests implementation gaps—likely in timezone handling or sync logic. Runs on Claude and Hermes, but no model benchmarks make real-world reliability uncertain.
Deployable if you need basic calendar integration and can verify behavior on your data. For mission-critical scheduling, test thoroughly first.
Team calendar: event, type, date and time with time zone, attendees, organizer, location and source module.
As a process B 69/100 · Nearly there — weak spots: result and completion, inputs and preconditions, progress reporting
The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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 · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 134 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "risk" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "source_type" - note
frontmatter-keyunknown frontmatter key "date_added" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "source_repo"
Process rating: all ten parameters 69/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
- 60Failures and branches. 2 branches
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 37 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3188 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 13 top-level sections: this looks like several domains in one skill
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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 134: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 37 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.