SKILLEMALL.ai
GitHub ↗ RU Sign in

BD notion-api-toolkit-free

(no description)

ClawHub Agent Skills author: 天轰穿 v1.0.0 MIT-0 2 files body ≈ 1 829 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

一个面向个人开发者与知识工作者的轻量化Notion集成Skill,通过托管OAuth与REST API的组合,帮助你快速接入Notion工作空间。本免费版聚焦查询与基础读写,适合个人与小型团队试用。 本Skill封装了Notion…

As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationNotionSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
83/100
safety, quality, tests
Safety 60%
100
Quality 40%
57
Run on models
none yet
Process rating
D
48/100
Unfinished process
Result and completion w 14
0
When it triggers w 12
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. 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 · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Map keys must be unique at line 43, column 1: suggested_price: "9.9 CNY/per_use" tools: ["read", "write", "exec"] ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "slug"
  • note frontmatter-key unknown frontmatter key "displayName"
  • note frontmatter-key unknown frontmatter key "summary"
  • note frontmatter-key unknown frontmatter key "edition"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "pricing_tier"
  • note frontmatter-key unknown frontmatter key "pricing_model"
  • note frontmatter-key unknown frontmatter key "suggested_price"

Process rating: all ten parameters 48/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 3 mutating operations with no state check
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 42 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1829 tokens
  • low 14 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
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +4Structure: 40 headings
  • +3Step-by-step instructions: 42 items
  • +4Has examples (11 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.

External checks

ClawHub: suspicious
This Notion skill is mostly coherent, but it asks for powerful CLI-based read/write access while using overly broad triggers and unrelated local network diagnostics.
LLM: suspicious (medium) · VirusTotal: · 23 Jul 2026