BF google-hotels-search
Search live Google Hotels stays by location, dates and occupancy, returned in one unified schema alongside every other booking platform. Use when a user wants to find Google Hotels listings. Powered by the StayingAPI REST API / MCP server.
Search live Google Hotels stays by location, dates and occupancy, returned in one unified schema alongside every other booking platform.
As a process F 44/100 · Will not run — References files that are not bundled: references/auth-setup.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The text references files that are not there: add them or drop the references.
- 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-requests-env-secretSKILL.md:1Skill asks the runtime to inject credential env vars into its sandbox: STAYINGAPI_KEY — verify each one is needed for the stated purposerequired_environment_variables: STAYINGAPI_KEY
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 239 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
missing-refreference to a missing file: references/auth-setup.md - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "repository" - note
frontmatter-keyunknown frontmatter key "required_environment_variables"
Process rating: all ten parameters 44/100
- 0Tools and files. 1 referenced file(s) missing: references/auth-setup.md
- 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. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Consistency. The Hermes dialect needs category and tags
- 100Steps. 18 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 1407 tokens
- low 11 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
- +4No input/output examples
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 239: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 18 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.