BC obsidian-cloudflare-pages
Publish selected Obsidian markdown from a vault to a static site and deploy to Cloudflare Pages.
As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, consistency
ProcedureObsidianCloudflareInfrastructuretype and topics are labelled automatically from the skill text
The same skill appears in 1 more place: ClawHub
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Exfiltration
read-dotenvREADME.md:120Reads a .env filecp skills/obsidian-cloudflare-pages/.env.example skills/obsidian-cloudflare-pages/.env
-
low Exfiltration
read-dotenvSKILL.md:83Reads a .env filecp skills/obsidian-cloudflare-pages/.env.example skills/obsidian-cloudflare-pages/.env
-
low Exfiltration
read-dotenvSKILL.md:121Reads a .env filecp .env.example .env
Files scanned: 5. 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") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 23 mutating operations with no state check
- 40Consistency. Frontmatter name (obsidian-cloudflare-pages) differs from the folder (obsidian-cloudflare-pages-skill)
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 46 steps, 1 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 996 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 96: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 12 headings
- +3Step-by-step instructions: 46 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.
External checks
ClawHub: suspicious
This skill does what it says, but its publishing CLI can delete files in configurable local paths and run unpinned setup/deploy commands, so it should be reviewed before use.
LLM: suspicious (high) · VirusTotal: · 29 May 2026