BD rest_api_wrapper_generator
Generate production-ready REST API endpoints to expose graph database operations, queries, and data management capabilities
Generate production-ready REST API endpoints to expose graph database operations, queries, and data management capabilities
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
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 · 2
✓ No critical or high findings
Medium and low: 2
-
medium Secrets in code
secret-labelled-tokenreferences/rest-api-patterns.md:565Labelled token / key literal (vendor format unknown — verify it is not a live credential)X-API-Key: sk_l…242
-
low Secrets in code
secret-password-literalreferences/rest-api-patterns.md:565Hard-coded password / key literal (may be an example)X-API-Key: sk_l…242
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-long-hermesdescription is 123 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
Process rating: all ten parameters 48/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 (rest_api_wrapper_generator) differs from the folder (rest-api-wrapper-generator)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web, python, node) that frontmatter does not declare
- 100Steps. 60 steps
- 100Execution cost. Instruction body is 3428 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 15 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -248 emoji in the instructions: noise for the model
- -41 reference files, but SKILL.md never points to them: the model will not open them
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 123: enough signal without eating the budget
- +4Structure: 70 headings
- +3Step-by-step instructions: 60 items
- +4Has examples (43 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.