chore(deps): update supabase/agent-skills digest to 8331f91

[renovate]

This PR contains the following updates:

Package	Update	Change
supabase/agent-skills	digest	1207767 → 8331f91

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[toolhive-release-app]

🛡️ Skill Security Scan Results

❌ supabase

• Status: Failed
• Findings: 9
• Blocking: 1

Blocking issues:

• [LLM_UNAUTHORIZED_TOOL_USE] (HIGH) The references/skill-feedback.md file instructs the agent to create a GitHub Issue on the supabase/agent-skills repository using conversation content as the issue body. While step 1 asks permission once, the workflow then proceeds to automatically draft and submit the issue. This constitutes unauthorized tool use where the agent takes an external write action (creating a public GitHub issue potentially containing conversation details) on behalf of the user. The issue body is populated from conversation content, which could inadvertently expose sensitive project details, credentials, or proprietary code discussed during the session. (references/skill-feedback.md)

Allowlisted (not blocking):

• MANIFEST_MISSING_LICENSE (Allowed: supabase/agent-skills is licensed MIT at the repository root; upstream does not embed an SPDX license identifier in per-skill SKILL.md frontmatter.)

✅ supabase-postgres-best-practices

• Status: Passed
• Findings: 2

---

Summary: Scanned 2 skill(s), found 1 blocking issue(s).

⚠️ Action Required: Review the blocking findings. Add a justified entry to the skill's security.allowed_issues[] in its spec.yaml if the finding is a false positive.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.