Is Delete Page safe and trustworthy?

tashan scores Delete Page on public evidence — it is currently active. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Delete Page?

Drop the skill folder into ~/.claude/skills/ (user scope) or .claude/skills/ (project scope).

Who maintains Delete Page?

2 GitHub contributors, source: clawpage/clawpage-skill.

‹ The Index

Delete Page

skill

Author’s activation text, quoted as published

Permanently delete a clawpage page by its pageId via DELETE /api/pages/<pageId. Trigger when the user explicitly asks to delete / remove / take down / destroy / 删除 / 下线 a specific page they own and a pageId (or a clearly identifiable single page) is in scope. Deletion is irreversible — there is no soft-delete or trash. NEVER fabricate a pageId. Do NOT use for removing a local page project only (just rm -rf the directory), do NOT use for unpublishing temporarily (use update-page to set a short TTL or pagecode instead), do NOT use for sub-resources like short links / KV records / blobs (use manage-links / manage-data / manage-blobs respectively).

Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format

Install (Claude Code):

cp -r delete-page ~/.claude/skills/

Adoption: 1 repos
Upkeep: 68.0
Freshness: 70.0
Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
Health: active
Contributors: 2
License: MIT-0

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

Its own instructions

Its SKILL.md says when to use it, covers setup and states a limitation.

Read from the capability’s own SKILL.md. This is not a grade and does not compare to the instruction-depth verdict on an MCP server — a skill has no tools to document, so that rubric does not apply to it.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Pro adds the history to tashan doctor, so a run over your own config says which of yours gained an advisory, started running an install script, or lost its last maintainer — and what to move to.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

source ↗ · skill:clawpage/delete-page

Everything on this page is public evidence and free. What it cannot know is whether you run this — npx tashan-cli doctor reads your own config and names what is wrong in it, also free. tashan Pro tells you the day any of it changes.

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-14 · scorer s5 · how · something wrong here?