DELETE IT

v1.0.3

Gmail integration. Manage communication data, records, and workflows. Use when the user wants to interact with Gmail data.

⭐ 0· 330·0 current·0 all-time

byMembrane Dev@membranedev

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for membranedev/membranedev-gmail.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "DELETE IT" (membranedev/membranedev-gmail) from ClawHub.
Skill page: https://clawhub.ai/membranedev/membranedev-gmail
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install membranedev-gmail

ClawHub CLI

Package manager switcher

npx clawhub@latest install membranedev-gmail

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Suspicious

high confidence

Purpose & Capability

The name/description claim Gmail integration and managing communication data, but there are no instructions, code files, required env vars, or config paths to perform Gmail access. A legitimate Gmail skill would need OAuth credentials, API endpoints, or at least detailed runtime steps.

Instruction Scope

SKILL.md is a one-line placeholder: 'Dummy skill. Delete it pls'. It provides no runtime instructions, no API call examples, and no data handling guidance. That lack of actionable instruction is incoherent with the described purpose and leaves the agent with no safe, auditable behavior to follow.

✓

Install Mechanism

There is no install spec and no code files, so nothing will be written to disk or installed by the skill itself. From an install mechanism perspective this is low risk, but also explains why there's nothing implementing the claimed Gmail functionality.

Credentials

No environment variables, credentials, or config paths are requested — but a real Gmail integration would require OAuth client credentials, tokens, or at least a declared primary credential. The absence of any declared secrets is disproportionate to the claimed capability.

✓

Persistence & Privilege

The skill does not request 'always: true' and uses default invocation settings. It does not declare system-wide configuration changes or persistent privileges.

Scan Findings in Context

[no_code_files_no_findings] unexpected: The regex-based scanner found nothing because the skill is instruction-only and contains no code. Given the declared Gmail integration, we'd expect code or at least OAuth/env declarations — their absence makes the empty scan result unexpected.

What to consider before installing

Do not install this skill as-is. The description promises Gmail integration but the SKILL.md is a placeholder and there is no implementation, no provenance (homepage/source), and no declared credentials or OAuth flows. Ask the publisher for: (1) a clear SKILL.md with exact runtime steps and required OAuth scopes, (2) source code or a trusted homepage, and (3) explanation of what credentials the skill needs and why. If you don't get concrete answers and verifiable code, treat the skill as untrusted and remove it.

Like a lobster shell, security has layers — review code before you run it.

latestvk979758ccg7dghnpd08v4zv1zx827qtx

330downloads

0stars

4versions

Updated 1mo ago

v1.0.3

MIT-0

Dummy skill. Delete it pls

Comments

Loading comments...