Security audit
Security checks for vulnerabilities and agentic risk
This is a straightforward Notion CLI skill that reads and creates Notion pages using a user-provided Notion API key, with some documentation gaps around secret handling and live workspace writes.
Install only if you intend to connect an agent or CLI to your Notion workspace. Use a least-privilege Notion integration, avoid pasting the API key into shared logs or terminals, and test create-page against a non-production database before allowing agent-driven writes.
The README explicitly instructs users or agents to create Notion pages through the API but does not warn that this operation mutates data in the connected workspace. In an agent-execution context, missing disclosure about write side effects can lead to unintended creation of records, clutter, or modification of production knowledge bases when a user expects read-only behavior.
The skill documents commands that can create and read Notion content but does not warn users that running the tool may modify live workspace data. This increases the chance of unintended destructive or privacy-impacting actions because an agent or user may treat the commands as harmless documentation rather than operations against a real external service.
The installation section instructs users to export a Notion API key but provides no privacy or secret-handling guidance. This can lead to credential leakage through shell history, screenshots, logs, shared terminals, or misuse by agents that do not treat the value as sensitive.
The file’s user-facing description and command/help text are written in Chinese, and there is no indication that another language is supported or that Chinese is an intentional opt-in. This can violate language/locale policy when a skill imposes a specific language on users without choice or documented justification.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
click.echo("✗ 错误：需要 NOTION_API_KEY")
return
url = 'https://api.notion.com/v1/pages'
data = {
"parent": {"database_id": parent},
"properties": {
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
click.echo("✗ 错误：需要 NOTION_API_KEY")
return
url = 'https://api.notion.com/v1/pages'
data = {
"parent": {"database_id": parent},
"properties": {
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
click.echo("✗ 错误：需要 NOTION_API_KEY")
return
url = 'https://api.notion.com/v1/pages'
data = {
"parent": {"database_id": parent},
"properties": {
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
click.echo("✗ 错误：需要 NOTION_API_KEY")
return
url = 'https://api.notion.com/v1/pages'
data = {
"parent": {"database_id": parent},
"properties": {
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
}
try:
response = requests.post(url, headers=ctx.obj['headers'], json=data)
response.raise_for_status()
result = response.json()
The natural-language instructions and headings indicate the skill is presented in Chinese, but there is no opt-in, alternative language option, or justification for a locale-specific constraint. Under the stated policy, forcing a specific language without user choice can be a policy violation.
The skill documentation is written in Chinese and does not indicate any language choice, opt-in, or region-specific justification. Per the policy, forcing a specific language or locale without user opt-in can be a natural-language policy violation.