CD notion
Production-ready Notion API client for SaaS workflows. Create/read/update pages, query data sources, append blocks.
The same skill from clawhub has been run on models: Active A see the result → This is a copy: its text may differ, so the grade is not carried over.
Production-ready Notion API client for SaaS workflows.
As a process D 47/100 · Unfinished process — weak spots: steps, when it triggers, failures and branches
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
-
medium Broad scope
meta-requests-env-secretSKILL.md:1Skill asks the runtime to inject credential env vars into its sandbox: NOTION_API_KEY — verify each one is needed for the stated purposerequired_environment_variables: NOTION_API_KEY
Files scanned: 4. 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 "web" - note
frontmatter-keyunknown frontmatter key "env" - note
frontmatter-keyunknown frontmatter key "primary-credential"
Process rating: all ten parameters 47/100
- 0Steps. Prose only: no discrete steps
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 6 mutating operations with no state check
- 40Consistency. Frontmatter name (notion) differs from the folder (notion-manager)
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 227 tokens
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 115: 120–800 characters recommended
- +3No numbered steps or checklist
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 5 headings
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.