skills.rest
karaabd23-crypto
karaabd23-cryptoCOMMUNITY
Explore all skills by this author →
GitHub

openclaw-secret-scanning-maintainer

Automate triage, redaction, cleanup, and resolution of GitHub Secret Scanning alerts.

1|Updated Apr 23, 2026
Search Tags:#workflow#security#github#alerts#redaction#maintainer#secret-scanning
One-click install
npx skills add https://github.com/karaabd23-crypto/openclaw --skill openclaw-secret-scanning-maintainer-karaabd23-crypto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openclaw-secret-scanning-maintainer
Source: https://github.com/karaabd23-crypto/openclaw/tree/main/.agents/skills/openclaw-secret-scanning-maintainer
Command: npx skills add https://github.com/karaabd23-crypto/openclaw --skill openclaw-secret-scanning-maintainer-karaabd23-crypto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Maintainer-only workflow to triage, redact, clean up, and resolve secret leakage detected by GitHub Secret Scanning in OpenClaw repositories.

Core Features & Use Cases

  • Triage open secret-scanning alerts and fetch relevant locations (comments, bodies, and discussions).
  • Redact leaked secrets in approved locations and delete or recreate affected comments as needed.
  • Notify affected authors with an English-language security notice and provide guidance to rotate credentials.

Quick Start

Run the secret-scanning maintainer workflow to process new alerts, redact exposed secrets, delete or recreate affected content, and notify authors.

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 clean up leaked secrets detected in GitHub PR and issue discussions?▼

The best way to clean up leaked secrets in PR and issue discussions is a maintainer workflow that redacts exposed credentials in bodies, purges affected content, and sends English-language security notices guiding authors to rotate credentials.

Can I use automated redaction scripts to resolve GitHub secret scanning alerts in issue comments?▼

Yes, automated redaction scripts can resolve GitHub secret scanning alerts by processing issue comments. The workflow uses a dedicated script to fetch alerts, redact secrets, delete or recreate comments, and mark alerts as resolved. This handles issue comments, PR bodies, and discussions.

Why does my secret scanning alert workflow require repository admin permissions?▼

Secret scanning alert workflows require repository admin permissions to ensure only authorized maintainers can execute sensitive security operations like triage, redaction, purge, and resolution of exposed credentials. This restricts access to prevent unauthorized changes.

What steps are involved in resolving GitHub secret scanning alerts across issue bodies and discussions?▼

Resolving GitHub secret scanning alerts involves fetching open alerts across issue bodies and discussions, redacting leaked secrets, purging affected content, notifying authors with security notices, and summarizing the workflow operations. This ensures complete cleanup.

Related Skills

Explore More Software Engineering Skills→
Agent-Pattern-LabsAgent-Pattern-Labs
4

openclaw-secret-scanning-maintainer

Triage, redact, and resolve GitHub Secret Scanning alerts via Node.js scripts.

Official
Advanced
JaviMontanoJaviMontano

apex-secrets-sanitization

Detect and mask exposed credentials across code, configs, docs, and pipelines.

Community
Advanced
constzzconstzz

golang-continuous-integration

Automate Golang CI/CD pipeline setup with GitHub Actions.

Community
Advanced
ArianHobson333ArianHobson333
7

osint

Automate open-source intelligence collection from code repositories with secret scanning.

Community
Advanced