DC quietmail
(no description)
Not recommendedlow grade D
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
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 · 6
✓ No critical or high findings
Medium and low: 6
-
low Secrets in code
secret-password-literalapp/models.py:15Hard-coded password / key literal (may be an example)api_key = Column(String(128), unique=True, nullable=False, index=True) # qmail_xxx
-
low Exfiltration
read-dotenvREADME.md:43Reads a .env filecp .env.example .env
-
low Dangerous commands
cmd-background-processREADME.md:156Starts a background / autostarted processsudo systemctl enable quiet-mail-api
-
low Secrets in code
secret-password-literaltest_send_email_direct.py:18Hard-coded password / key literal (may be an example) (test fixture / example file)password="TG4I…V8m",
fixture -
low Secrets in code
secret-high-entropy-tokentest_testbot_smtp.py:18High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)password="LxTW…R0o",
fixturequoted -
low Secrets in code
secret-password-literaltest_testbot_smtp.py:18Hard-coded password / key literal (may be an example) (test fixture / example file)password="LxTW…R0o",
fixture
Files scanned: 26. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 18 mutating operations with no state check
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 100Steps. 26 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2155 tokens
- low 16 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)
- +3Description length 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- -218 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 30 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (16 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
This is a disclosed email API skill, but it needs review because it ships live-looking SMTP credentials, weak secret storage defaults, and no enforced anti-abuse limits for account creation or sending.
LLM: suspicious (high) · VirusTotal: suspicious · 10 Sept 2026