DD article
Write a publication-ready article in one of three angles - a trending long-form piece, a watched-repo thesis, or a project-through-a-lens essay. Optional Replicate hero image with --visual.
Write a publication-ready article in one of three angles - a trending long-form piece, a watched-repo thesis, or a project-through-a-lens essay.
As a process D 39/100 · Unfinished process — References files that are not bundled: url, ../images/explainer-${today}.<ext>, ../images/repo-article-${today}.<ext>
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
net-credential-useSKILL.md:462Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)3. **Generate** with fallback enabled from the start (Nano Banana Pro can rate-limit; Seedream 5.0 lite is the fallback). The Replicate call is auth'd, so route it through `./secretcurl` with the `{REquoted -
low Exfiltration
net-credential-useSKILL.md:547Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)There is no network sandbox — `curl` works. For a flaky public GET, fall back to **WebFetch** on the same URL. For an auth'd API, call `./secretcurl` with a `{ENV_NAME}` placeholder (the key is injectquoted
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
body-longSKILL.md body ≈ 8098 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: url - warning
missing-refreference to a missing file: ../images/explainer-${today}.<ext> - warning
missing-refreference to a missing file: ../images/repo-article-${today}.<ext> - warning
missing-refreference to a missing file: ../images/project-lens-${today}.<ext> - warning
missing-refreference to a missing file: ../images/${IMG_BASENAME}.<ext>
Process rating: all ten parameters 39/100
- 0Tools and files. 5 referenced file(s) missing: url, ../images/explainer-${today}.<ext>, ../images/repo-article-${today}.<ext>
- 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. 23 mutating operations with no state check
- 40Execution cost. Instruction body is 8098 tokens: crowds the task out of the window
- 85Steps. 133 steps, 2 vague phrases
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (18 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 189: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 133 items
- +4Has examples (16 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 45.