openclaw-secret-scanning-maintainer

Triage and redact GitHub secret scanning alerts in issues, pull requests, and discussions.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/wangqianCAI/OBI --skill openclaw-secret-scanning-maintainer-wangqiancai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-secret-scanning-maintainer
Source: https://github.com/wangqianCAI/OBI/tree/main/.agents/skills/openclaw-secret-scanning-maintainer
Command: npx skills add https://github.com/wangqianCAI/OBI --skill openclaw-secret-scanning-maintainer-wangqiancai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates the sensitive and repetitive process of triaging GitHub secret scanning alerts, ensuring that leaked credentials are redacted or removed while maintaining repository security and compliance.

Core Features & Use Cases

  • Automated Redaction: Safely identifies and replaces exposed secrets in issue bodies and comments without manual intervention.
  • History Purging: Handles the deletion and recreation of comments to effectively clear edit history containing plaintext secrets.
  • Use Case: When a developer accidentally commits a Discord bot token or API key in a PR comment, this skill allows a maintainer to instantly redact the secret, notify the author, and resolve the security alert in one workflow.

Quick Start

Use the openclaw-secret-scanning-maintainer skill to list all open alerts and process the first one by fetching its content and redacting the leaked secrets.

Frequently Asked Questions about openclaw-secret-scanning-maintainer

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

FAQPage Schema
How do I automate GitHub secret scanning alert triage for leaked credentials?

Automating GitHub secret scanning alert triage involves fetching alert metadata, identifying secret patterns, and performing secure API operations to redact or purge exposed credentials in issues, pull requests, and discussions.

How can I redact exposed API keys in GitHub pull request comments?

To redact exposed API keys in GitHub pull request comments, the skill identifies the leaked secrets and replaces the sensitive information directly in the comment body without manual intervention.

Does this secret redaction process completely remove the edit history of plaintext secrets in GitHub issues?

Yes, this secret redaction process completely removes the edit history of plaintext secrets by deleting and recreating the affected comments to effectively clear any historical record of the leaked information.

Can I use this skill to process secret scanning alerts across GitHub issues, pull requests, and discussions?

Yes, you can use this skill to process secret scanning alerts across GitHub issues, pull requests, and discussions by fetching alert metadata and utilizing secure API operations to purge the sensitive content.

How are sensitive secrets handled in logs during automated GitHub security alert resolution?

During automated GitHub security alert resolution, sensitive secrets are protected by enforcing strict non-disclosure rules in logs and utilizing temporary files for safe content processing.

What is the best way for a maintainer to resolve a secret leak alert and notify the author in one workflow?

The best way for a maintainer to resolve a secret leak alert and notify the author in one workflow is to automate the redaction of the secret, alert the contributor, and close the security flag simultaneously.