openclaw-secret-scanning-maintainer

Triage, redact, and resolve GitHub Secret Scanning alerts across issues, PRs, and discussions.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/seasonmac/Full-Scene-Agents --skill openclaw-secret-scanning-maintainer-seasonmac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-secret-scanning-maintainer
Source: https://github.com/seasonmac/Full-Scene-Agents/tree/main/openclaw/.agents/skills/openclaw-secret-scanning-maintainer
Command: npx skills add https://github.com/seasonmac/Full-Scene-Agents --skill openclaw-secret-scanning-maintainer-seasonmac

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.

Core Features & Use Cases

  • Maintainer-only workflow coordinating triage, redaction, cleanup, and resolution of secret leakage across issues, PRs, and discussions.
  • Automated workflow steps: fetch alerts, analyze content, redact secrets, purge unsafe content, notify authors, and close alerts.
  • Real-world use: when a repository detects exposed credentials in comments or descriptions, run this skill to isolate the leak and guide remediation.

Quick Start

Run the secret-scanning maintainer workflow to identify, redact, purge, notify, and resolve secret leakage across GitHub issues, PRs, and discussions using the provided script.

Frequently Asked Questions about openclaw-secret-scanning-maintainer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to handle GitHub secret scanning alerts found in issue comments and discussions?

The best way to handle GitHub secret scanning alerts is to use an automated workflow that triages, redacts, purges unsafe content, notifies authors, and resolves the leaks across issues, PRs, and discussions end-to-end.

How do I redact exposed credentials detected in GitHub pull request comments?

You can redact exposed credentials in GitHub pull request comments by running a specialized secret-scanning script that isolates the leak, replaces the sensitive data, and securely purges the original content from the repository.

Can I automatically notify GitHub users after redacting their leaked secrets in issue bodies?

Yes, you can automatically notify GitHub users after redacting their leaked secrets by executing a workflow that sends templated notifications to authors once the unsafe content is purged and the alert is ready to be closed.

Does this secret scanning maintainer workflow require administrative repository access to resolve alerts?

Yes, this secret scanning workflow is a maintainer-only process designed to securely triage and resolve alerts, requiring appropriate GitHub repository permissions to execute GraphQL and REST calls for content redaction and alert closure.

How are GitHub GraphQL and REST API calls used during secret leak remediation?

GitHub GraphQL and REST API calls are used to securely fetch alerts, analyze exposed content, redact secrets, and purge unsafe text across issues and discussions, with restricted output to prevent further sensitive data exposure.