Please remove skill from search index: mixx85/spotify-claw (deleted)

[mixx85]

Hi,

I'm the author of the skill mixx85/spotify-claw (account: @mixx85).

The skill has been deleted via CLI, but it still appears in ClawHub search results. Earlier versions (1.1–1.3) were published accidentally and contained personal data.

Could you please:

1. Fully remove mixx85/spotify-claw from the search index
2. Confirm all version history / stored ZIP files are deleted from the database

Thank you.

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve.

Workflow note: Future ClawSweeper reviews update this same comment in place.

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

Summary
Keep open. This is a live ClawHub privacy/deletion request for a specific skill, and current production still returns the reported slug in search, detail, file, and version endpoints while current main documents the owner delete path as soft-delete rather than artifact purge.

Reproducibility: yes. On 2026-05-18, production search returned spotify-claw, the detail endpoint returned owner mixx85, the file endpoint returned HTTP 200, and the versions endpoint returned eight versions including 1.1.0, 1.2.0, and 1.3.0.

Next step
This needs maintainer/operator access and privacy/security judgment to verify and purge live production data; it is not a safe automated source-only fix PR.

Security
Needs attention: This remains security-sensitive because public production endpoints expose a deleted skill whose reporter says earlier versions contained personal data.

Review details

Best possible solution:

A maintainer/operator should verify ownership, purge or delist the reported slug across production data, search/digest, embedding, version, storage, backup, and cache surfaces, then confirm the result without exposing private contents.

Do we have a high-confidence way to reproduce the issue?

Yes. On 2026-05-18, production search returned spotify-claw, the detail endpoint returned owner mixx85, the file endpoint returned HTTP 200, and the versions endpoint returned eight versions including 1.1.0, 1.2.0, and 1.3.0.

Is this the best way to solve the issue?

Yes. Keeping this open for maintainer/operator handling is the right path because the remaining work is live production purge verification and privacy policy handling, not a safe source-only cleanup.

Label justifications:

• P1: A user reports accidentally published personal data, and live production endpoints still expose the reported deleted skill and version metadata.
• impact:security: The request concerns sensitive personal data and deletion/purge verification across public API, database, search, and storage surfaces.

Security concerns:

• [high] Complete production privacy purge verification
  An operator should verify and complete removal across live rows, search/digest and embedding tables, version records, storage blobs, backups, and caches without exposing private artifact contents.
  Confidence: 0.97
• [high] Do not treat CLI delete as artifact purge — convex/httpApiV1/skillsV1.ts:1492
  The public DELETE path calls setSkillSoftDeletedInternal with deleted: true, which hides the skill but does not prove historical version records or stored files are purged.
  Confidence: 0.94
• [medium] Stored skill files need explicit purge confirmation — convex/skills.ts:1213
  The visible hard-delete step deletes version documents, but the inspected backend paths did not show a skill-file storage delete call for each files[].storageId.
  Confidence: 0.87

Acceptance criteria:

• Operator query confirms no active or stale rows for mixx85/spotify-claw remain in skills, skillSearchDigest, skillVersions, skillEmbeddings, embeddingSkillMap, aliases, or related reference tables.
• Operator storage check confirms every files[].storageId belonging to the reported skill versions is deleted or irretrievable.
• Public checks for search, detail, versions, and file endpoints no longer expose the reported slug or its version metadata.

What I checked:

• Live issue state: GitHub still shows this issue open with P1, maintainer-review, product-decision, security-review, current-main-repro, and impact:security labels; the body says versions 1.1-1.3 accidentally contained personal data.
• Production search still returns the deleted slug: The live search endpoint returned spotify-claw with owner handle mixx85, so the observable search-index complaint still reproduces on 2026-05-18.
• Production detail and file endpoints still expose the skill: The live detail endpoint returned owner mixx85, latest version 2.0.1, and public metadata; the SKILL.md file endpoint returned HTTP 200.
• Production version metadata still includes reported versions: The live versions endpoint returned eight versions, including 1.1.0, 1.2.0, and 1.3.0, matching the range the reporter said accidentally contained personal data.
• CLI delete is documented as soft-delete: The CLI delete command description is Soft-delete one of your skills, and user-facing docs say the command calls DELETE /api/v1/skills/{slug} and reserves the slug for 30 days. (packages/clawhub/src/cli.ts:323, 1a00013c21b1)
• CLI delete calls public DELETE endpoint: cmdDeleteSkill sends DELETE /api/v1/skills/{slug} with the user's token and does not invoke an admin hard-delete or storage-purge path. (packages/clawhub/src/cli/commands/delete.ts:71, 1a00013c21b1)

Likely related people:

• steipete: Current blame for the CLI delete command, v1 DELETE handler, setSkillSoftDeletedInternal, and hardDeleteSkillStep points to the current release commit by Peter Steinberger, and recent GitHub history shows adjacent ClawScan/moderation backend work. (role: current-line owner and recent backend contributor; confidence: high; commits: 1a00013c21b1, 35aa372b24a3, 651e54ed7c0d; files: packages/clawhub/src/cli.ts, packages/clawhub/src/cli/commands/delete.ts, convex/httpApiV1/skillsV1.ts)
• Patrick-Erichsen: Recent path history includes Patrick on skill restore and security audit work touching convex/skills.ts, which is adjacent to soft-delete, undelete, moderation, and operator cleanup behavior. (role: recent adjacent security and restore contributor; confidence: medium; commits: 72d4e7a3262e, 893f341bdb02; files: convex/skills.ts)
• vyctorbrzezowski: A recent search relevance commit touched convex/search.ts, convex/skills.ts, and search tests, making this a useful routing signal for stale public search visibility. (role: recent search contributor; confidence: medium; commits: 9ab92e58470e; files: convex/search.ts, convex/skills.ts, convex/search.test.ts)

Remaining risk / open question:

• Production may still contain sensitive personal data in public metadata, version rows, storage blobs, backups, caches, or derived search/embedding tables until an operator verifies and purges it.
• The public owner delete path is soft-delete semantics, so treating a CLI delete as artifact purge would not satisfy the reporter's version-history and stored-file deletion request.
• A source-only PR cannot confirm whether this specific production slug and its historical blobs have been removed.

Codex review notes: model gpt-5.5, reasoning high; reviewed against 1a00013c21b1.

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve.

Keep open. This is an issue, and the repository policy for this ClawHub pass does not auto-close issues; independently, the request is still a live production deletion/privacy matter. Current main shows owner CLI/API deletion is a soft-delete path, while repo-only review cannot verify that the production rows, search digest rows, embedding lookup rows, version records, or stored file blobs for the reported slug have actually been purged.

Required change / next step:

This is a production privacy/deletion request that needs maintainer/operator access to verify and purge live Convex data and storage before any source-only hardening work is considered.

Review details

Best possible solution:

A maintainer/operator should verify the live production deployment for the reported slug, purge any remaining skill, search digest, version, embedding, lookup, alias/reference rows and associated storage blobs, then confirm the result to the reporter. If that production check confirms source gaps, follow with a focused hardening PR that keeps skillSearchDigest in sync on soft delete and makes hard delete remove lookup/digest rows and stored skill files with targeted tests.

Acceptance criteria:

• Production operator query confirms no active or stale rows for the reported slug remain in skills, skillSearchDigest, skillVersions, skillEmbeddings, embeddingSkillMap, aliases, or related reference tables.
• Production storage check confirms every files[].storageId belonging to the reported skill versions is deleted or irretrievable.
• If a hardening PR follows, run bun run test, bun run format:check, and bun run lint.

What I checked:

• Issue request: The provided issue body says the author deleted mixx85/spotify-claw via CLI, still saw it in ClawHub search, and asks for search-index removal plus confirmation that version history and stored ZIP files containing personal data are gone.
• Repository cleanup policy: The provided review policy for openclaw/clawhub says to keep issues open and only propose auto-close for pull requests that are certainly implemented on current main.
• CLI delete is soft delete: The CLI delete command is described as Soft-delete a skill (owner, moderator, or admin), matching the reporter's CLI path but not a hard purge. (packages/clawhub/src/cli.ts:301, 7bef2a0b65d4)
• CLI delete calls public DELETE endpoint: cmdDeleteSkill sends DELETE /api/v1/skills/{slug} with the API token; it does not call the admin hard-delete mutation. (packages/clawhub/src/cli/commands/delete.ts:64, 7bef2a0b65d4)
• HTTP DELETE maps to soft-delete mutation: The v1 DELETE handler authenticates the API token and calls internal.skills.setSkillSoftDeletedInternal with deleted: true. (convex/httpApiV1/skillsV1.ts:1218, 7bef2a0b65d4)
• Soft delete does not purge versions or files: setSkillSoftDeletedInternal patches the skill's soft-delete/moderation fields, adjusts counts, marks embeddings deleted, and writes an audit log; the inspected body does not delete skillVersions rows, skillSearchDigest rows, embeddingSkillMap rows, or Convex storage blobs. (convex/skills.ts:6990, 7bef2a0b65d4)

Likely related people:

• Patrick Erichsen: Current blame points Patrick at the CLI delete command, v1 DELETE handler, setSkillSoftDeletedInternal, hardDeleteSkillStep, digest helper/tests, and recent adjacent convex/skills.ts work. (role: current-main maintainer and recent merger for the delete/search/admin cleanup surface; confidence: high; commits: ecf09b868a98, a7d1701f5a3d; files: packages/clawhub/src/cli.ts, packages/clawhub/src/cli/commands/delete.ts, convex/httpApiV1/skillsV1.ts)
• Peter Steinberger: Path history on the same CLI/backend/docs surface includes earlier release-era commits by Peter before the current main rewrite/import, so he is useful secondary routing context though current line ownership is mostly Patrick. (role: earlier release-history owner for the ClawHub CLI/backend baseline; confidence: medium; commits: 8752e4bb7e92, 8216c73c9bd4; files: packages/clawhub/src/cli/commands/delete.ts, convex/skills.ts, convex/httpApiV1/skillsV1.ts)

Remaining risk / open question:

• Repo-only review cannot verify whether production Convex still contains rows or blobs for mixx85/spotify-claw.
• Closing this now could leave a privacy/deletion request unresolved for a specific reported slug.
• The current owner CLI/API delete path is intentionally a soft delete and may not satisfy the requested purge of version history or stored files.
• Search visibility may still depend on stale skillSearchDigest rows because soft delete does not update that digest in the inspected mutation.

Codex review notes: model gpt-5.5, reasoning high; reviewed against 7bef2a0b65d4.