Please unhide griffmurder/taskbullet — 1.0.2 LLM scan is clean, owner cannot restore

[GriffMurder]

What happened

Published skill taskbullet as @griffmurder.

• Owner: Wesley / griffmurder
• Skill page: https://clawhub.ai/griffmurder/skills/taskbullet
• Profile (shows 0 public skills): https://clawhub.ai/griffmurder

1.0.0 / 1.0.1 were hidden by LLM review (2FA/captcha/secret-scoping). I republished 1.0.2 with no secret relay, owner-authorized workspace only.

clawhub skill verify taskbullet --version 1.0.2 now reports:

• security.status: clean
• verdict: benign
• confidence: high
• summary: disclosed TaskBullet integration for user-approved human handoff, with limits on spending, secrets, and account ownership

clawhub inspect also shows verdict: clean and legacyReason: scanner.llm.clean. Latest tag is 1.0.2.

Blocker

Owner restore is forbidden:

clawhub unhide taskbullet and clawhub undelete taskbullet both return:

Forbidden: This skill was hidden by moderation and cannot be restored by the owner. Please contact a moderator.

Public profile still shows No published skills yet.

Ask

Please have a moderator unhide griffmurder/taskbullet so 1.0.2 can appear on the publisher profile and install surfaces.

No malware findings. This is a false-positive hold left over from the first two versions.

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed September 11, 2026, 8:43 PM ET / September 12, 2026, 00:43 UTC.

Summary
Keep open for staff moderation. The reported clean scan supports reviewing the hold, but neither current source nor the discussion establishes that this skill has been restored.

Reproducibility: not applicable. as a code-bug reproduction: this requests a staff action, and the reported owner denial matches an explicit source and test contract.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Add expected vs actual behavior.

Maintainer decision needed

Question	Recommendation
Does griffmurder/taskbullet qualify for staff restoration after reviewing version 1.0.2 and the original hold?	Review for targeted restoration: Inspect the original hold and current artifact, then restore through the existing staff path if no independent restriction remains.

Why: Repository source establishes who may restore a listing, but cannot establish whether this production hold remains justified.

Next step
Route to staff moderation to inspect the hold and decide restoration; no bounded source defect is established for an automated repair.

Security
Needs attention: Lifting this hold requires a staff assessment of the artifact and existing restrictions.

Review details

Best possible solution:

Resolve the listing through audited staff moderation, preserving version scanner results and verifying public visibility after any approved restoration.

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

Not applicable as a code-bug reproduction: this requests a staff action, and the reported owner denial matches an explicit source and test contract.

Is this the best way to solve the issue?

Yes, case-specific staff review is the appropriate path; allowing clean scans alone to bypass restore authorization would weaken the existing moderation boundary.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• The production hide provenance, account standing, and complete version 1.0.2 security evidence were not independently inspected; the false-positive explanation remains unverified.

Codex review notes: model internal, reasoning medium; reviewed against 8c2de6c506bb.

Label changes

Label changes:

• add P2: This is a targeted publisher moderation request without evidence of a broader registry outage.
• add impact:security: The requested action lifts a moderation restriction on public distribution.
• add issue-rating: 🌊 off-meta tidepool: Current issue advisory state selects this label.
• add clawsweeper:no-new-fix-pr: Current issue advisory state selects this label.
• add clawsweeper:needs-security-review: Current issue advisory state selects this label.

Label justifications:

• P2: This is a targeted publisher moderation request without evidence of a broader registry outage.
• impact:security: The requested action lifts a moderation restriction on public distribution.

Evidence reviewed

Security concerns:

• [medium] Verify the hold before authorizing restoration
  A reported clean version scan does not establish that independent listing or account restrictions are resolved; confirm those restrictions before restoring public availability.
  Confidence: 0.95

What I checked:

• Outstanding restoration request: The live issue matches the supplied report: version 1.0.2 reportedly scans clean, both owner restore commands return Forbidden, and the public profile remains empty. The sole comment is a bot review-start notice, not confirmation of restoration.
• Current restore authorization: Owner restoration requires owner-initiated hide provenance; missing or non-owner provenance produces the exact reported error. A clean moderation reason alone does not confer restoration authority. (convex/skills.ts:13764, 8c2de6c506bb)
• Staff restoration preserves scanner evidence: Authorized restoration reconstructs moderation fields from the current version, clears soft deletion, updates public counts and embeddings, and records an audit entry. This existing capability does not prove it was applied to taskbullet. (convex/skills.ts:13810, 8c2de6c506bb)
• Authorization regression coverage: Tests explicitly reject owner restoration when hide provenance is missing and permit moderator restoration with an audit record. These tests were inspected, not executed. (convex/skills.undeleteGate.test.ts:567, 8c2de6c506bb)
• Security contract: The specification separates version-scoped scanner verdicts from staff decisions about availability and forbids replacing scanner verdicts with manual trust overrides. (specs/security-moderation.md:570, 8c2de6c506bb)
• Latest-release boundary: The v0.23.3 source also contains the owner-initiated-hide check and the reported Forbidden message. No release evidence establishes restoration of this particular production record. (convex/skills.ts:13890, 87ca030c30f3)

Likely related people:

• unknown: The claimed source-line change could not be verified from bounded local history. (role: source history unknown; confidence: low)

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.