CD digest
Generate and send a digest on a configurable topic, optionally pulling RSS/Atom feeds as an input source alongside web + X signal
Generate and send a digest on a configurable topic, optionally pulling RSS/Atom feeds as an input source alongside web + X signal
As a process D 45/100 · Unfinished process — References files that are not bundled: url
GeneratorSoftware developmentAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
net-credential-useSKILL.md:62Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)**Path A — X.AI API (primary):** a direct `curl` to the Responses API. First confirm the key with `[ -n "${XAI_API_KEY:+x}" ] && echo KEY_PRESENT || echo KEY_UNSET` (a bare `$XAI_API_KEY` is a secretquoted
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: url
Process rating: all ten parameters 45/100
Will not run. References files that are not bundled: url
- 0Tools and files. 1 referenced file(s) missing: url
- 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
- 30Running it twice. 14 mutating operations with no state check
- 100Steps. 42 steps
- 100Failures and branches. 9 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3779 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (9 tags): a typed call is more reliable
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
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 129: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.