BD MGC Blackbox (Zero‑Exposure Edition)
Local encrypted credential and script management for AI agents. Zero‑exposure execution layer for storing tokens, passwords, configs, and scripts without plaintext leakage.
Local encrypted credential and script management for AI agents.
As a process D 40/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Implicit keys need to be on a single line at line 1, column 1: ```yaml ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "id" - note
frontmatter-keyunknown frontmatter key "mcp_tools" - note
frontmatter-keyunknown frontmatter key "install" - note
frontmatter-keyunknown frontmatter key "runtime" - note
frontmatter-keyunknown frontmatter key "port" - note
frontmatter-keyunknown frontmatter key "keywords"
Process rating: all ten parameters 40/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (MGC Blackbox (Zero‑Exposure Edition)) differs from the folder (mgc-meta-skill)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web, python, node) that frontmatter does not declare
- 70Execution cost. Instruction body is 4459 tokens
- 85Steps. 54 steps, 1 vague phrases
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 172: enough signal without eating the budget
- +4Structure: 36 headings
- +3Step-by-step instructions: 54 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 52.
External checks
ClawHub: suspicious
This skill is a real local secret-and-script manager, but its documentation overstates the plaintext boundary while giving agents secret retrieval and script execution paths.
LLM: suspicious (high) · 13 Aug 2026