DC ai-content-repurposer
(no description)
Not recommendedlow grade D
As a process C 64/100 · Has gaps — weak spots: when it triggers, failures and branches, running it twice
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:26High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…9dM/mwVgvbZJaSNaRk+bshk…Kbz+IoId…W0Q==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:87High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…NxY+fzEC…TMw+Dfs3…h4g==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:104High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…SDq+2kAA…MOe/+5cdoEdg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:176High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…9co+7Zrb…CSH/zJvXw56gmHw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:231High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Eg5+wW0/QaZM…swK/w2MWU+Gw==",
detector
Files scanned: 13. 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 64/100
- 0When it triggers. No condition that starts the skill
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 39 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2207 tokens
- low 13 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
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +4Structure: 32 headings
- +3Step-by-step instructions: 39 items
- +3Output format is stated explicitly
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
The skill mostly matches its content-repurposing purpose, but batch mode can write outside the requested output folder and the docs do not clearly explain that user content is sent to OpenAI.
LLM: suspicious (high) · VirusTotal: · 29 May 2026